Updates from: 05/27/2022 01:24:35
Service Microsoft Docs article Related commit history on GitHub Change details
platform Include Saas Offer https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/prepare/include-saas-offer.md
See [create a SaaS offer](/azure/marketplace/create-new-saas-offer) for complete
We strongly recommend that you verify the end-to-end purchasing experience before publishing your SaaS offer. You can do this by creating a separate offer just for testing. For complete information, see [test offer overview](/azure/marketplace/plan-saas-offer#test-offer), [create a test offer](/azure/marketplace/create-saas-dev-test-offer), and [preview your offer](/azure/marketplace/test-publish-saas-offer). > [!IMPORTANT]
-> You can test an end-to-end transaction in Teams until your app completes store validation. For more information, see [Test preview for monetized apps](Test-preview-for-monetized-apps.md).
+> You can test an end-to-end transaction in Teams using the [Test preview for monetized apps](Test-preview-for-monetized-apps.md) feature. For live offers you must complete the app store validation process.
From a Teams standpoint, these tests must verify that the number of licenses and assignments match whatΓÇÖs in the Teams admin center when users:
platform Azure Provisioning Instructions Tab https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/includes/get-started/azure-provisioning-instructions-tab.md
+## Deploy your app to Azure
+
+Deployment consists of two steps. First, necessary cloud resources are created (also known as provisioning). Then, your app's code is copied into the created cloud resources. For this tutorial, you will deploy the tab app.
+<br>
+<br>
+<details>
+<summary>What's the difference between Provision and Deploy?</summary>
+<br>
+The <b>Provision</b> step creates resources in Azure and Microsoft 365 for your app, but no code (HTML, CSS, JavaScript, etc.) is copied to the resources. The <b>Deploy</b> step copies the code for your app to the resources you created during the provision step. It is common to deploy multiple times without provisioning new resources. Since the provision step can take some time to complete, it is separate from the deployment step.
+</details>
+<br>
+
+# [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.
+
+1. Select **Provision in the Cloud**.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/provisioning-commands.png" alt-text="Screenshot showing the provisioning commands" border="false":::
+
+1. Select a subscription to use for the Azure resources.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/select-resource.png" alt-text="Screenshot showing resources for provisioning" border="false":::
+
+ > [!NOTE]
+ > There are always some Azure resources used for hosting your app.
+
+ A dialog warns you that costs may be incurred when running resources in Azure.
+
+1. Select **Provision**.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/provision-warning.png" alt-text="Screenshot of the provisioning dialog." border="true":::
+
+ 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-successmsg.png" alt-text="Screenshot showing the provisioning complete dialog." border="false":::
+
+ 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.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/provisioned-resources-env.png" alt-text="Screenshot showing the provisioning complete dialog." border="false":::
+
+1. Select **Deploy to the Cloud** from the **Deployment** panel after provisioning is complete.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/deploy-cloud.png" alt-text="Screenshot showing the where to click to deploy to cloud." border="false":::
+
+ 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.
+
+# [Command Line](#tab/cli)
+
+In your terminal window:
+
+1. Run `teamsfx provision`.
+
+ ``` bash
+ teamsfx provision
+ ```
+
+ When prompted, select an Azure subscription to use Azure resources.
+
+ > [!NOTE]
+ > There are always some Azure resources used for hosting your app.
+
+1. Run `teamsfx deploy`.
+
+ ``` bash
+ teamsfx deploy
+ ```
+++
+## Run the deployed app
+
+Once the provisioning and deployment steps are complete:
+
+1. Open the debug panel (**Ctrl+Shift+D** / **⌘⇧-D** or **View > Run**) from Visual Studio Code.
+1. Select **Launch Remote (Edge)** from the launch configuration drop-down.
+1. Select the **Start debugging (F5)** to launch your app from Azure.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/launch-remote.png" alt-text="Screenshot showing the launch app remotely." border="false":::
+
+1. Select **Add** when prompted to sideload the app onto Teams.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/remote-app-client.png" alt-text="Screenshot showing the app being installed." border="false":::
+
+ Congratulations, your first tab app is running in your Azure environment!
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/azure-deployed-apptab.png" alt-text="Screenshot shows message to try the app now or later" border="true":::
+
platform Azure Provisioning Instructions https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/includes/get-started/azure-provisioning-instructions.md
Select the Teams Toolkit :::image type="icon" source="~/assets/images/teams-tool
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-successmsg.png" alt-text="Screenshot showing the provisioning complete dialog." border="false":::
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/deploy-provision-successmsgext.png" alt-text="Screenshot showing the provisioning complete dialog." border="false":::
If you want you can view the provisioned resources. For this tutorial, you don't need to view resources.
Once the provisioning and deployment steps are complete:
:::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/launch-remote.png" alt-text="Screenshot showing the launch app remotely." border="false":::
-1. Select **Add** when prompted to sideload the app onto Teams on your local machine.
+1. Select **Add**.
- :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/add-bot-debug.png" alt-text="Screenshot showing the bot is being added on Teams client.":::
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/add-mex-app.png" alt-text="Screenshot showing the app being installed." border="false":::
+
+ The toolkit displays a message to indicate that the app is added to Teams.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/mex-added-msg.png" alt-text="Screenshot shows message to try the app now or later" border="true":::
+
+ - If you select **Got it**, you can try the app later from the list of Sideloaded apps.
+ - If you select **Try it**, Teams loads your app.
+
+ Your app is loaded on the Azure site.
+
+1. Select **Try it**.
+
+ The Message Extension app is loaded in a chat bot app.
+
+ :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/app-added-mex1.png" alt-text="Screenshot that shows app sideloaded in Teams" border="false":::
- You can type `welcome` to show an introduction card, and type `learn` to go to adaptive card and bot command documentation.
- :::image type="content" source="~/assets/images/teams-toolkit-v2/deploy-azure/azure-deployed-app.png" alt-text="Screenshot showing the learn card in the bot on Teams client.":::