| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Location Capability | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/device-capabilities/location-capability.md | Update your Teams app [manifest.json](../../resources/schem# > > * The **Request Permissions** prompt is automatically displayed when a relevant Teams API is initiated. For more information, see [request device permissions](native-device-permissions.md). > * Device permissions are different in the browser. For more information, see [browser device permissions](browser-device-permissions.md).+> * The Location API isn't supported in the [new Teams client](../../resources/teams-updates.md). We recommend you to use HTML5 `geolocation`. ## Location APIs |
| platform | Media Capabilities | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/device-capabilities/media-capabilities.md | Update your Teams app [manifest.json](../../resources/schem# "media", ], ```+> [!NOTE] +> The Media API isn't supported in the [new Teams client](../../resources/teams-updates.md). We recommend you to use HTML5 `media`. ## Media capability APIs |
| platform | Azure Api Permissions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/includes/get-started/azure-api-permissions.md | -**Add API Permission** +**Add API permission** 1. In the left pane, under **Manage**, select **API permissions**. |
| platform | Azure Provisioning Instructions Tab | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/includes/get-started/azure-provisioning-instructions-tab.md | The <b>Provision</b> step creates resources in Azure and Microsoft 365 for your </details> <br> -# [Visual Studio Code](#tab/vscode) + # [Visual Studio Code](#tab/vscode) -Select the Teams Toolkit :::image type="icon" source="~/assets/images/teams-toolkit-v2/teams-toolkit-sidebar-icon.png"::: icon in the Visual Studio Code sidebar. + Select the Teams Toolkit :::image type="icon" source="~/assets/images/teams-toolkit-v2/teams-toolkit-sidebar-icon.png"::: icon in the Visual Studio Code sidebar. -1. Select **Provision**. + 1. Select **Provision**. - :::image type="content" source="~/assets/images/teams-toolkit-v2/provisioning-commands.png" alt-text="Screenshot shows the provisioning commands."::: + :::image type="content" source="~/assets/images/teams-toolkit-v2/provisioning-commands.png" alt-text="Screenshot shows the provisioning commands."::: -1. Select anyone of the existing subscription. + 1. Select anyone of the existing subscription. - :::image type="content" source="~/assets/images/teams-toolkit-v2/select-subscription.png" alt-text="Screenshot shows selection of existing Subscription."::: + :::image type="content" source="~/assets/images/teams-toolkit-v2/select-subscription.png" alt-text="Screenshot shows selection of existing Subscription."::: -1. Select a resource group to use for the Azure resources. + 1. Select a resource group to use for the Azure resources. - :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/select-resource.png" alt-text="Screenshot shows resources for provisioning."::: + :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/select-resource.png" alt-text="Screenshot shows resources for provisioning."::: - > [!NOTE] - > Your app is hosted using Azure resources. - > - >For more information, see [Create resource group.](/azure/azure-resource-manager/management/manage-resource-groups-portal) + > [!NOTE] + > + > * Your app is hosted using Azure resources. + > * For more information, see [Create resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal). - A dialog warns you that costs may be incurred when running resources in Azure. + A dialog warns you that costs may be incurred when running resources in Azure. -1. Select **Provision**. + 1. Select **Provision**. - :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/provision-warning.png" alt-text="Screenshot shows the provisioning of dialog."::: + :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/provision-warning.png" alt-text="Screenshot shows the provisioning of dialog."::: - :::image type="content" source="~/assets/images/teams-toolkit-v2/provision-confirm.png" alt-text="Screenshot shows the selection of subscription."::: + The provisioning process creates resources in the Azure cloud. It may take some time. You can monitor the progress by watching the dialogs in the bottom-right corner. After a few minutes, you see the following notice: - The provisioning process creates resources in the Azure cloud. It may take some time. You can monitor the progress by watching the dialogs in the bottom-right corner. After a few minutes, you see the following notice: + :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/deploy-provision-successmsgext.png" alt-text="Screenshot shows the resource successfully provisioned in the cloud."::: - :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/deploy-provision-successmsgext.png" alt-text="Screenshot shows the resource successfully provisioned in the cloud."::: + If you want, you can view the provisioned resources. For this tutorial, you don't need to view resources. - If you want, you can view the provisioned resources. For this tutorial, you don't need to view resources. + The provisioned resource appears in the **ENVIRONMENT** section. - The provisioned resource appears in the **ENVIRONMENT** section. + :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/provisioned-resources-env.png" alt-text="Screenshot shows the provisioned resource."::: - :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/provisioned-resources-env.png" alt-text="Screenshot shows the provisioned resource."::: + 1. Select **Deploy** from the **LIFECYCLE** panel after provisioning is complete. -1. Select **Deploy** from the **LIFECYCLE** panel after provisioning is complete. + :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/deploy-cloud.png" alt-text="Screenshot shows the app deploy to the cloud."::: - :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/deploy-cloud.png" alt-text="Screenshot shows the app deploy to the cloud."::: + As with provisioning, deployment takes some time. You can monitor the process by watching the dialogs in the bottom-right corner. After a few minutes, you see a completion notice. - As with provisioning, deployment takes some time. You can monitor the process by watching the dialogs in the bottom-right corner. After a few minutes, you see a completion notice. + Now, you can use the same process to deploy your Bot and Message Extension apps to Azure. -Now, you can use the same process to deploy your Bot and Message Extension apps to Azure. + # [Command Line](#tab/cli) -# [Command Line](#tab/cli) + In your terminal window: -In your terminal window: + 1. Run `teamsfx provision`. -1. Run `teamsfx provision`. + ``` bash + teamsfx provision + ``` - ``` bash - teamsfx provision - ``` + When prompted, select an Azure subscription to use Azure resources. - When prompted, select an Azure subscription to use Azure resources. + 1. Run `teamsfx deploy`. -1. Run `teamsfx deploy`. -- ``` bash - teamsfx deploy - ``` + ``` bash + teamsfx deploy + ``` |
| platform | Teams Toolkit CLI | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/Teams-Toolkit-CLI.md | Install `teamsfx-cli` from `npm` and run `teamsfx -h` to check all available com | Command | Description | |-|-|-| `teamsfx new`| Create new Teams application.| -| `teamsfx add`| Adds features to your Teams application.| -| `teamsfx account`| Manage cloud service accounts. The supported cloud services are 'Azure' and 'Microsoft 365'. | +| `teamsfx new`| Create a new Microsoft Teams application.| +| `teamsfx add`| Add a feature to your Microsoft Teams application.| +| `teamsfx account`| Manage Microsoft 365 and Azure accounts. The supported cloud services are Azure and Microsoft 365. | | `teamsfx env` | Manage environments. |-| `teamsfx provision` | Provision cloud resources in the current application.| -| `teamsfx deploy` | Deploy the current application. | -| `teamsfx package` | Build your Teams app into package for publishing.| -| `teamsfx validate` | Validate the current application.| -| `teamsfx publish` | Publish the app to Teams.| +| `teamsfx help` | Show Microsoft Teams Toolkit CLI help. | +| `teamsfx list` | List available Microsoft Teams application templates and samples. | +| `teamsfx provision` | Run the provision stage in teamsapp.yml or teamsapp.local.yml.| +| `teamsfx deploy` | Run the deploy stage in teamsapp.yml or teamsapp.local.yml. | +| `teamsfx package` | Build your Microsoft Teams app into a package for publishing.| +| `teamsfx validate` | Validate the Microsoft Teams app using manifest schema or validation rules. | +| `teamsfx publish` | Run the publish stage in teamsapp.yml.| | `teamsfx preview` | Preview the current application. |-| `teamsfx config` | Manage the configuration data. | -| `teamsfx permission`| Collaborate with other developers in same project.| +| `teamsfx m365` | Manage M365 app. | +| `teamsfx permission`| Check, grant, and list permissions for users who can access and manage Microsoft Teams application and Microsoft Entra application. | | `teamsfx update` | Update the specific application manifest file. | | `teamsfx upgrade` | Upgrade the project to work with the latest version of Teams Toolkit. | The following list provides the common scenarios for `teamsfx preview`: > [!NOTE] > The logs of the background services, such as React is saved in ~/.fx/cli-log/local-preview/. -## `teamsfx config` +## `teamsfx m365` -Configure user settings. +Manage Microsoft 365 app. -### Parameters for `teamsfx config` +### Parameters for `teamsfx m365` | Command | Description | |:- |:-|-| `teamsfx config get [option]` | Get user global settings. | -| `teamsfx config set` | Set user settings. | --### Scenarios for `teamsfx config` --* Stop sending telemetry data -- ```typescript - teamsfx config set telemetry off - ``` +| `sideloading [options]` | Sideloading an M365 App with corresponding information specified in the given manifest package. | +| `unacquire [options]` | Remove an acquired M365 App. | +| `launchinfo [options]` | Get launch information of an acquired M365 App. | ## `teamsfx permission` Check, grant, and list user permission. ## `teamsfx update` -Update the specific application manifest file. +Update the specific app manifest file. | Command | Description | |:- |:-| | `teamsfx update aad-app` | Update the Microsoft Entra App in the current application. |-| `teamsfx update teams-app` | Update the Teams App manifest to Teams Developer Portal. | +| `teamsfx update teams-app` | Update the Teams app manifest to Teams Developer Portal. | ### Parameters for `teamsfx update aad-app` Provision the cloud resources in the current application. | Command | Description | |:- |:-|-| `teamsfx provision manifest` | Provision a Teams App in Teams Developer portal with corresponding information specified in the given manifest file. | +| `teamsfx provision manifest` | Provision a Teams app in Teams Developer portal with corresponding information specified in the given app manifest file. | ### Parameters for `teamsfx provision` Provision the cloud resources in the current application. ## `teamsfx deploy` -This command is used to deploy the current application. By default it deploys entire project but its also possible to deploy partially. The options are `frontend-hosting`, `function`, `apim`, `bot`, `spfx`, `aad-manifest`, and `manifest`. +The `teamsfx deploy` command is used to deploy the current application. By default, it deploys an entire project but it's also possible to deploy partially. The available options are `frontend-hosting`, `function`, `apim`, `bot`, `spfx`, `aad-manifest`, and `manifest`. ### Parameters for `teamsfx deploy` The following list provides required permissions for `TeamsFx` projects: ## Deploy to Azure web app manually -1. Create an SSO enable tab. +1. Create an SSO enabled tab. 2. Provision your project: ```bash The following list provides required permissions for `TeamsFx` projects: 6. Modify `templates/azure/provision/frontendHosting.bicep`. -7. Provision again. Teams Toolkit updates Microsoft Entra ID, and manifest for you. +7. Provision again. Teams Toolkit updates Microsoft Entra ID and app manifest for you. 8. Find your `appPackage.dev.zip` in build, or AppPackage folder, and add to Teams. |