| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | App Growth Lifecycle | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/app-growth-lifecycle.md | You can plan your app's growth through the app lifecycle: ## See also -[Strategize and execute growth for your app](overview-app-growth.md) +- [Strategize and execute growth for your app](overview-app-growth.md) +- [Five steps to drive adoption of your app](../../../../../promote-app-adoption.md) <!-- ### Building your collaborative app |
| platform | Gain Traction | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/gain-traction.md | -In the Traction stage, you’ll want to gain mindshare for your collaborative app among top customers. You will build readiness to scale adoption and growth, and start realizing return on investment. Here are the various initiatives and growth levers at your disposal: +In the Traction stage, you’ll want to gain mindshare for your collaborative app among top customers. You'll build readiness to scale adoption and growth, and start realizing return on investment. Here are the various initiatives and growth levers at your disposal: ## What should you do during the Traction stage?++<br> +<details> +<summary>Plan, build readiness and drive adoption among customers</summary> ++As soon as your collaborative app is published and customers are made aware of its existence, the entire focus of your organization must shift towards driving adoption of your app among existing customers first. Follow the step-by-step guidance, resources and best practices available [here](../../../../../promote-app-adoption.md) to plan and support the rollout of your Teams app in your customers’ organizations, navigate business decision makers, IT admins and educate end-users. The outcome of a successful app rollout among your existing customers is a pre-requisite to learn from user feedback, achieve product-market fit, acquire net new customers, monetize your app and eventually derive RoI out of your build and go-to-market investments. ++[Back to top](#what-should-you-do-during-the-traction-stage) +</details> <br> <details> <summary>Upskill customer success team on your new Teams app</summary> Surface [deep links](../../../../build-and-test/deep-links.md) within your brows To get maximum ROI, surface the nudges contextually for scenarios that are inherently collaborative over chat or in meetings. They're best delivered inside Microsoft Teams through your app. +[Back to top](#what-should-you-do-during-the-traction-stage) +</details> +<br> +<details> +<summary>Localize your app to support demand in global markets </summary> ++Microsoft Teams is available for users in more than 180 markets and supports over 50 languages. If you already have a core SaaS product for the web browser or native apps for Windows or mobile phones localized for one or more markets, consider also localizing your Teams app. You can evaluate and prioritize the localization markets based on the [geographical spread of users and tenants](/azure/marketplace/teams-apps-usage) and the [Teams app usage report](../overview.md#analyze-app-usage) in Partner Center. You can easily localize your Teams app by following the extensive developer guidance available [here](../../../../build-and-test/apps-localization.md). + [Back to top](#what-should-you-do-during-the-traction-stage) </details> Contact the Microsoft field, account, or engineering representatives to feature ## See also [Strategize and execute growth for your app](overview-app-growth.md)- |
| platform | Overview App Growth | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/overview-app-growth.md | Monetization investments encompass defining role of Teams app in your business a - [Distribute your Microsoft Teams app](../../../apps-publish-overview.md) - [Monetize your app](../../prepare/monetize-overview.md)+- [Five steps to drive adoption of your app](../../../../../promote-app-adoption.md) - [Build your collaborative app](build-app.md) - [Gain traction for your collaborative app in the market](gain-traction.md) - [Launch your collaborative app](launch-app.md) |
| platform | Scale App | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/scale-app.md | Help your sales team secure large new customer deals leading with your Teams col <details> <summary>Digital webinars for existing customers and new prospects</summary> -Host digital webinars at regular cadences to showcase the value of your Teams app to customers. Your customer success team and pre-sales or sales team must funnel relevant existing customers and new prospects as preferred leads for targeting webinar inviations to. Ensure that you include links to sign up for the webinars on your appΓÇÖs landing page on your website and your app store listing. It attracts new, exploratory users who may be interested in learning more about your app. +Host digital webinars at regular cadences to showcase the value of your Teams app to customers. Your customer success team and pre-sales or sales team must funnel relevant existing customers and new prospects as preferred leads to invite for the webinars. Ensure that you include links to sign up for the webinars on your appΓÇÖs landing page on your website and your app store listing. It attracts new, exploratory users who may be interested in learning more about your app. Get in touch with your field, account, or engineering representatives from Microsoft to request their participation in hero instances of these direct-to-customer webinars. Generate interest from new customer accounts and drive traffic to your collabora <details> <summary>Publish customer demand and appΓÇÖs impact story</summary> -Share real customer stories using a four to five minute video. Nominate a customer and gain their commitment to participate in the story. Work with the customer on the narrative. Ensure that you include the benefits derived from your collaborative app, showcase resulting increased employee productivity (preferably quantifiable gains) and how customers prefer to use your SaaS service inside Teams as a collaborative app. Use this video for demand generation, digital marketing campaigns or showcase on public pages. +Share real customer stories using a four to five-minute video. Nominate a customer and gain their commitment to participate in the story. Work with the customer on the narrative. Ensure that you include the benefits derived from your collaborative app, showcase resulting increased employee productivity (preferably quantifiable gains) and how customers prefer to use your SaaS service inside Teams as a collaborative app. Use this video for demand generation, digital marketing campaigns or showcase on public pages. After developing it, host these customer stories on the landing page of the Teams app on your website. Link this video in the marketplace listing of your collaborative app. Promote it via paid, earned media, or social media posts to highlight the success of the app. While building traction, you showcased the collaborative app in Teams during you <details> <summary>User retargeting and re-engagement basis app analytics</summary> -A key product-led growth initiative, use signals from your app analytics to re-target users who have recently engaged with your app in Teams but haven't reached a value realization milestone defined by you. Users who haven't visited your app or churned recently must be re-engaged to bring back to your app. +A key product-led growth initiative, use signals from your app analytics to retarget users who have recently engaged with your app in Teams but haven't reached a value realization milestone defined by you. Users who haven't visited your app or churned recently must be re-engaged to bring back to your app. Remember, your goal is to get users to experience value at the earliest by using your collaborative app. By converting your user who tries your app into a sticky, habitual user is eventually going to result in paying customers. Based on the list youΓÇÖve shared with your Microsoft field, account, or enginee Remember, just enabling the app inside Teams won't be enough. Instead, adoption and change management practices led by your customer success team such as organization-wide emails at regular cadences, flyers, retention campaigns, user trainings, identifying and scaling through app champions in each team, gamification and constantly keeping an eye on app usage metrics within the customerΓÇÖs tenant is required to form a habit among users. +To plan and support the rollout of your Teams app in your customersΓÇÖ organizations, follow the guidance, resources, and best practices available [here](../../../../../promote-app-adoption.md). + [Back to top](#what-should-you-do-during-the-scale-stage) </details> <br> |
| platform | Succeed | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/succeed.md | To wrap up, your collaborative app is now becoming a full-fledged strategic prod Continue to increase the usage of your collaborative app on Teams through existing customer activation. You can continue new customer acquisition via the Teams marketplace or through sales-led customer deal wins leading with your collaborative app. +To plan and support the rollout of your Teams app in your customersΓÇÖ organizations, follow the guidance, resources, and best practices available [here](../../../../../promote-app-adoption.md). + </details> <br> <details> This stage is ripe to further sales, customer success and product-led initiative <details> <summary>Continuously reduce churn via product and analytics-led insights</summary> -Retaining users by providing them with a sticky experience is key to growing your Teams app and realizing economic value from your product and GTM investments. Ensure that youΓÇÖve [implemented robust and granular analytics](../../../../design/overview-analytics.md) for your Teams app. It should serve your need to measure when and which users have churned or are likely to churn from your app. You can them re-engage and re-target them via outreach channels within or outside your app. +Retaining users by providing them with a sticky experience is key to growing your Teams app and realizing economic value from your product and GTM investments. Ensure that youΓÇÖve [implemented robust and granular analytics](../../../../design/overview-analytics.md) for your Teams app. It should serve your need to measure when and which users have churned or are likely to churn from your app. You can them re-engage and retarget them via outreach channels within or outside your app. </details> <br> Microsoft will evaluate co-activation opportunities in large customer accounts b <details> <summary>Get included in Microsoft exec blog or flagship event endorsement</summary> -Get the power of the Microsoft executive team behind your next leadership blog or event. Review your plans for blogs or events in which you'll be participating. Develop ideas on how a Microsoft executive can help to promote your commercial marketplace offer in a blog or at an event. Reach out to the [ISV Marketplace Success Rewards Program team](mailto:rewards@microsoft.com) to request Microsoft executive endorsement. If eligibile, the team will work with you to find a Microsoft executive (Director level or higher) to help endorse your Teams collaborative app available on the marketplace. +Get the power of the Microsoft executive team behind your next leadership blog or event. Review your plans for blogs or events in which you'll be participating. Develop ideas on how a Microsoft executive can help to promote your commercial marketplace offer in a blog or at an event. Reach out to the [ISV Marketplace Success Rewards Program team](mailto:rewards@microsoft.com) to request Microsoft executive endorsement. If eligible, the team will work with you to find a Microsoft executive (Director level or higher) to help endorse your Teams collaborative app available on the marketplace. </details> <br> |
| platform | Extend M365 Teams Personal Tab | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/m365-apps/extend-m365-teams-personal-tab.md | If your app makes use of [Content Security Policy](https://developer.mozilla.org |Microsoft 365 web |4765445b-32c6-49b0-83e6-1d93765276ca| |Microsoft 365 desktop | 0ec893e0-5785-4de6-99da-4ed124e5296c | |Microsoft 365 mobile | d3590ed6-52b3-4102-aeff-aad2292ab01c |- |Outlook desktop, mobile | d3590ed6-52b3-4102-aeff-aad2292ab01c | + |Outlook desktop | d3590ed6-52b3-4102-aeff-aad2292ab01c | |Outlook web | bc59ab01-8403-45c6-8796-ac3ef710b3e3|+ |Outlook mobile | 27922004-5251-4030-b22d-91ecd9a37ea4 | > [!NOTE] > Some Microsoft 365 client applications share Client IDs. |
| platform | Promote App Adoption | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/promote-app-adoption.md | For better communication and adoption campaign, identify your metrics in advance After successful app adoption and analysis, share your journey and your achievements in the form of a case study or an app success story. Work with [Microsoft ISV success program](https://www.microsoft.com/isv/program-benefits) to publish it with Microsoft. For information on how Microsoft can help, see [Succeed with your collaborative app](concepts/deploy-and-publish/appsource/post-publish/app-growth/succeed.md). [Back to top](#understand-how-you-can-drive-app-adoption)++## See also ++* [Gain traction for your collaborative app in the market](concepts/deploy-and-publish/appsource/post-publish/app-growth/gain-traction.md) +* [Succeed with your collaborative app](concepts/deploy-and-publish/appsource/post-publish/app-growth/succeed.md) +* [Scale your collaborative app](concepts/deploy-and-publish/appsource/post-publish/app-growth/scale-app.md) |
| platform | Access Teams Context | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/access-teams-context.md | The following table lists commonly used context properties of the *context* obje | page.frameContext | frameContext | The context where page url is loaded (content, task, setting, remove, sidePanel) | | sharepoint | sharepoint | SharePoint context. This is only available when hosted in SharePoint. | | user.tenant.teamsSku | tenantSKU | The license type for the current user tenant. Possible values are enterprise, free, edu, unknown |-| user.licenseType | userLicenseType | The license type for the current user. Possible values are: Unknown, Teacher, Student, Free, SmbBusinessVoice, SmbNonVoice, FrontlineWorker | +| user.licenseType | userLicenseType | The license type for the current user. Possible values are Unknown, Teacher, Student, Free, SmbBusinessVoice, SmbNonVoice, FrontlineWorker, and Anonymous. | | app.parentMessageId | parentMessageId | The ID of the parent message from which this task module was launched. This is only available in task modules launched from bot cards. | | app.host.ringId | ringId | Current ring ID. | | app.sessionId | appSessionId | Unique ID for the current Host session for use in correlating telemetry data. | |
| platform | Tab Sso Register Aad | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/tabs/how-to/authentication/tab-sso-register-aad.md | To configure scope and authorize trusted client applications, you'll need: | 5e3ce6c0-2b1f-4285-8d4b-75ee78787346 | Teams web application | | 4765445b-32c6-49b0-83e6-1d93765276ca | Microsoft 365 web application | | 0ec893e0-5785-4de6-99da-4ed124e5296c | Microsoft 365 desktop application |- | d3590ed6-52b3-4102-aeff-aad2292ab01c | Outlook desktop, mobile application | + | d3590ed6-52b3-4102-aeff-aad2292ab01c | Outlook desktop application | | bc59ab01-8403-45c6-8796-ac3ef710b3e3 | Outlook web application |+ | 27922004-5251-4030-b22d-91ecd9a37ea4 | Outlook mobile application | 1. Select the application ID URI you created for your app in **Authorized scopes** to add the scope to the web API you exposed. |
| platform | Explore Teams Toolkit | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/explore-Teams-Toolkit.md | zone_pivot_groups: teams-app-platform # Explore Teams Toolkit -In this document, you can understand different UI elements along with description and basic usage in Teams Toolkit. +You can explore the Teams Toolkit look and feel within the Visual Studio Code or Visual Studio. ++This section gives you a tour of Teams Toolkit and its features. ::: zone pivot="visual-studio-code" -## Basic UI elements of Teams Toolkit +## Take a tour of Teams Toolkit -After Teams Toolkit installation, the following Teams Toolkit UI appears: +Teams Toolkit appears within Visual Studio Code as an extension. After you install Teams Toolkit, it opens within the Visual Studio Code window. :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/overview1_1.png" alt-text="Overview of Teams Toolkit" lightbox="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/overview1_1.png"::: | Serial No. | UI Elements | Definition |-| | | -| 1 | **Get Started** | Explore Teams Toolkit and get an overview of the fundamentals. | -| 2 | **Create a new Teams app** | Create a new Teams app based on your requirement. | -| 3 | **View samples** | Access existing samples to build apps based on your requirement. | -| 4 | **Documentation** | Access the Microsoft Teams Developer documentation. | -| 5 | **Tutorials** | Access different tutorials. | -| 6 | **New File** | Create a new file. | -| | **Open File** | Open the existing file. | -| | **Open Folder** | Open the existing folder. | -| 7 | **Recent** | View the recent files. | +| | | | +| 1 | **Documentation** | Access the Microsoft Teams Developer documentation. | +| 2 | **How-to guides** | Access how-to guides for app scenario and app development. | +| 3 | **Create a new Teams app** | Create a new Teams app based on your requirement. | +| 4 | **View samples** | Select and build existing app samples based on common use cases for a Teams app. | +| 5 | ΓÇó **New File** <br> ΓÇó **Open File** <br> ΓÇó **Open Folder** <br> ΓÇó **Clone Git Repository** | ΓÇó Create a new file. <br> ΓÇó Open the existing file. <br> ΓÇó Open the existing folder. <br> ΓÇó Clone the Git repository of your app project. | +| 6 | **Recent** | View the recent files. | +| 7 | **Get Started** | Explore Teams Toolkit and get an overview of the fundamentals. | ### Explore the Teams Toolkit task pane -You can explore UI elements from task pane in the Teams Toolkit. Task pane appears after creating an app using Teams Toolkit. The following video helps you to learn about the process of creating a new Teams app: +You can explore the available functionalities from the Teams Toolkit task pane. The task pane appears only after you've created an app project using Teams Toolkit. The following video helps you to learn about the process of creating a new Teams app: :::image type="content" source="../assets/videos/javascript-bot-app1_1.gif" alt-text="Create a Teams app"::: -After creating a new Teams app, the directory structure of the app appears in the left panel and the **`README`** file in the right panel. +After you create a new Teams app project, the directory structure of the app appears in the left panel and the **`README`** file in the right panel. :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/first-page_1.png" alt-text="First page of Teams Toolkit" lightbox="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/first-page_1.png"::: -Let's take a tour of the Teams Toolkit UI. +Let's take a tour of Teams Toolkit. - In Visual Studio Code activity bar, the following icons are relevant to the Teams Toolkit: + In Visual Studio Code activity bar, the following icons are relevant to Teams Toolkit: -| Icon | Description | +| Select | To... | | | |-| **Explorer** :::image type="icon" source="../assets/images/teams-toolkit-v2/file-explorer-icon.PNG"::: | To view the directory structure of the app. | -| **Run and Debug** :::image type="icon" source="../assets/images/teams-toolkit-v2/run-debug-icon.PNG"::: | To start the local or remote debug process. | -| **Teams Toolkit** :::image type="icon" source="../assets/images/teams-toolkit-v2/teams-toolkit-sidebar-icon.PNG"::: | To view the task pane in the Teams Toolkit. | +| **Explorer** :::image type="icon" source="../assets/images/teams-toolkit-v2/file-explorer-icon.PNG"::: | View the directory structure of the app. | +| **Run and Debug** :::image type="icon" source="../assets/images/teams-toolkit-v2/run-debug-icon.PNG"::: | Start the local or remote debug process. | +| **Teams Toolkit** :::image type="icon" source="../assets/images/teams-toolkit-v2/teams-toolkit-sidebar-icon.PNG"::: | View the task pane in the Teams Toolkit. | From the task pane, you can see the following sections: From the task pane, you can see the following sections: * **Sign in to Microsoft 365**: Use your Microsoft 365 account with a valid E5 subscription for building your app. - * **Sign in to Azure**: Use your Azure account for deploying an app on Azure. You can [create a free Azure account](https://azure.microsoft.com/free/) before you start. + * **Sign in to Azure**: Use your Azure account for deploying your app on Azure. You can [create a free Azure account](https://azure.microsoft.com/free/) before you start. :::column-end::: :::row-end::: From the task pane, you can see the following sections: To deploy your Teams app, you need the following environments: - * **local**: Deploy your app in the default local environment with local machine environment configurations. + * **local**: Deploy your app in the default local environment with local environment configurations. ++ * **dev**: Deploy your app in the default dev environment with remote or cloud environment configurations. - * **dev**: Deploy your app in the default dev environment with remote or cloud environment configurations. You can create more environments, as you need. + You can create more environments, such as production or test, as you need. :::column-end::: :::row-end::: :::row::: :::column span="":::- :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/development_1.png" alt-text="Development section"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/development-vsc.png" alt-text="Development section"::: :::column-end::: :::column span=""::: From the task pane, you can see the following sections: * **Create a new Teams app**: Use the Teams Toolkit wizard to prepare project scaffolding for app development. * **View samples**: Select any of the Teams Toolkit's sample apps. The toolkit downloads the app code from GitHub and you can build the sample app.- - * **Add features**: Add other required Teams capabilities to the Teams app during the development process and add optional cloud resources suitable for your app. ++ * **View how-to-guides**: Select to view Teams app scenario guides and development guides. ++ * **Add features**: Add other Teams capabilities to the Teams app during the development process and add optional cloud resources suitable for your app. * **Preview your Teams app (F5)**: Press **F5** to debug and preview your Teams app. - * **Edit manifest file**: Edit the Teams app integration with the Teams client. + * **Edit manifest file**: Edit the Teams app manifest file with the Teams client. :::column-end::: :::row-end::: From the task pane, you can see the following sections: To provision, deploy, and publish your Teams app, you need the following features: - * **Provision in the cloud**: Allocate Azure resources for your application. Teams Toolkit is integrated with Azure Resource Manager. + * **Provision in the cloud**: Allocate Azure resources for your application. Teams Toolkit is integrated with Azure Resource Manager, and it registers your app with Azure AD automatically. * **Zip Teams metadata package**: Create the app package that can be uploaded to Teams or Developer Portal. It contains the app manifest and app icons. From the task pane, you can see the following sections: To access more information on Teams Toolkit, you need the following documentation and resources: + * **Documentation**: Select to access the Microsoft Teams Developer documentation. + * **Get started**: View Teams Toolkit Get started help within Visual Studio Code. - * **Tutorials**: Select to access different tutorials. - - * **Documentation**: Select to access the Microsoft Teams Developer documentation. - * **Report issues on GitHub**: Select to access GitHub page and raise any issues. :::column-end::: :::row-end::: +### To view how-to guides ++1. Select **View how-to guides** from the Teams Toolkit task pane under Development section. ++ The **View how-to guides** menu appears. ++2. Select the type of how-to guide that you want to view. ++ :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/view-how-to-guides.png" alt-text="Screenshot showing the how-to guides menu options." lightbox="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/view-how-to-guides.png"::: ++ * Select any one of the Teams app scenario guides to view the guide to develop an app for a common app scenario, such as sending notifications using a bot. ++ * Select any one of the Teams app development guides to view a guide that helps in app development, such as embedding a dashboard tab in a Teams app. + ::: zone-end ::: zone pivot="visual-studio" ## Explore Teams Toolkit for Visual Studio -After Teams Toolkit installation, you can see Teams Toolkit options in the following ways: +Teams Toolkit appears within Visual Studio as a workload. When you've created a Teams Toolkit app, you can see Teams Toolkit options in the following ways: # [Project](#tab/prj) You can access Teams Toolkit under **Project**. 1. Select **Project** > **Teams Toolkit**.-1. You can access different Teams Toolkit options. +1. You can access different Teams Toolkit options: - :::image type="content" source="../assets/images/teams-toolkit-overview/teams-toolkit-operations-menu_1_2.png" alt-text="Teams toolkit operations menu"::: + :::image type="content" source="../assets/images/teams-toolkit-overview/teams-toolkit-project-menu.png" alt-text="Teams toolkit project menu" lightbox="../assets/images/teams-toolkit-overview/teams-toolkit-project-menu.png"::: # [Solution Explorer](#tab/solutionexplorer) You can access Teams Toolkit under **Solution Explorer**. 1. Select **View** > **Solution Explorer** to view **Solution Explorer** panel.-1. Right-click on your **Project**. -1. Select **Teams Toolkit** to access different Teams Toolkit options. +1. Right-click on your app project name. +1. Select **Teams Toolkit** to see the menu items. :::image type="content" source="../assets/images/teams-toolkit-overview/teams-toolkit-operations-menu1_1_2.png" alt-text="Teams toolkit operations from Project"::: You can access Teams Toolkit under **Project**. -After you've created your Teams Project, you can perform the following functions in Teams Toolkit for Visual Studio: +After you've created your Teams app project, you can use the following options to develop and build your app: :::image type="content" source="../assets/images/teams-toolkit-overview/teams-toolkit-menu-options_2.png"alt-text="Teams toolkit operations from Project menu"::: |Function |Description | |||-|Prepare Teams App Dependencies |Before you debug locally, perform this step. It helps you to set up the local debug dependencies and register Teams app in the Teams platform. You need a Microsoft 365 account. For more information, see [how to debug your Teams app locally using Visual Studio](debug-local.md). | -|Open Manifest File |To open Teams app manifest file, you can hover over the parameters to preview the values. For more information, see [how to edit Teams app manifest using Visual Studio](VS-TeamsFx-preview-and-customize-app-manifest.md). | -|Update Manifest in Teams Developer Portal |When you update the manifest file, only then you can redeploy the manifest file to Azure without deploying the whole project again. Use this command to update your changes to remote. For more information, see [how to edit Teams app manifest using Visual Studio](VS-TeamsFx-preview-and-customize-app-manifest.md). | -|Add Authentication Code |This option helps you to obtain signed-in Teams user token to access Microsoft Graph and other APIs. Teams Toolkit facilitates the interaction by abstracting from the Microsoft Azure Active Directory (Azure AD) which flows and integrations with simple APIs. For more information, see [how to add single sign-on to Teams app](add-single-sign-on.md). | -|Provision to the Cloud |This option helps you to create Azure resources that host your Teams app. For more information, see [how to provision cloud resources using Visual Studio](provision-cloud-resources.md). | -|Deploy to the Cloud |This option helps you to copy your code to the Azure resources created when you provisioned to the cloud. For more information, see [how to deploy Teams app to the cloud using Visual Studio](deploy.md#deploy-teams-app-to-the-cloud-using-visual-studio). | -|Preview in Teams |This option launches the Teams web client and lets you preview the Teams app in your browser. | -|Zip App Package |This option generates a Teams app package in the `Build` folder under the project. You can upload the package to the Teams client and run the Teams app. | +|Prepare Teams App Dependencies |Before you debug locally, ensure that you prepare your app for dependencies. This option helps you to set up the local debug dependencies and register Teams app in the Teams platform. You must have a Microsoft 365 account. For more information, see [how to debug your Teams app locally using Visual Studio](debug-local.md). | +|Open Manifest File | This option helps you to open Teams app manifest file. Hover over the parameters to preview the values. For more information, see [how to edit Teams app manifest using Visual Studio](VS-TeamsFx-preview-and-customize-app-manifest.md). | +|Update Manifest in Teams Developer Portal | This option helps you to update the manifest file. When you update the manifest file, only then you can redeploy the manifest file to Azure without deploying the whole project again. Use this command to update your changes to remote. For more information, see [how to edit Teams app manifest using Visual Studio](VS-TeamsFx-preview-and-customize-app-manifest.md). | +|Add Authentication Code | This option helps you obtain signed-in Teams user token to access Microsoft Graph and other APIs. Teams Toolkit facilitates the interaction by abstracting from the Microsoft Azure Active Directory (Azure AD) which flows and integrates with simple APIs. For more information, see [how to add single sign-on to Teams app](add-single-sign-on.md). | +|Provision to the Cloud | This option helps you to create Azure resources that host your Teams app. For more information, see [how to provision cloud resources using Visual Studio](provision-cloud-resources.md). | +|Deploy to the Cloud | This option helps you to copy your code to the cloud resources that you provisioned in Azure AD. For more information, see [how to deploy Teams app to the cloud using Visual Studio](deploy.md#deploy-teams-app-to-the-cloud-using-visual-studio). | +|Preview in Teams | This option launches the Teams web client and lets you preview the Teams app in your browser. | +|Zip App Package | This option generates a Teams app package in the `Build` folder under the project. You can upload the app package to the Teams client and run the Teams app. | ::: zone-end |