| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| README | https://github.com/MicrosoftDocs/msteams-docs/commits/main/README.md | Microsoft Teams is a cloud-based communications platform that combines different services for collaboration, such as chat, meetings, calling, and files. Teams is well integrated into Microsoft 365 and combines multiple workloads into a unified communication and collaboration system. In addition, Teams offers integration capabilities for other tools and third-party products. -Get documentation, sample code, tutorials, and more to help you build custom Microsoft Teams apps. See [Microsoft Teams developer documentation](https://docs.microsoft.com/microsoftteams/platform/mstdd-landing/). +Get documentation, sample code, tutorials, and more to help you build custom Microsoft Teams apps. See [Microsoft Teams developer documentation](https://learn.microsoft.com/microsoftteams/platform/mstdd-landing/). ## How to contribute -Teams documentation is part of the Microsoft Docs technical documentation library. The content is organized into groups called docsets, each representing a group of related documents managed as a single entity. You can ask questions, provide suggestion, or provide updates. See [how to contribute to Teams documentation](https://docs.microsoft.com/microsoftteams/platform/resources/teams-contributor-reference/). +Teams documentation is part of the Microsoft Docs technical documentation library. The content is organized into groups called docsets, each representing a group of related documents managed as a single entity. You can ask questions, provide suggestion, or provide updates. See [how to contribute to Teams documentation](https://learn.microsoft.com/microsoftteams/platform/resources/teams-contributor-reference/). -To contribute to any Microsoft docs, see the [contributor guide overview](https://docs.microsoft.com/contribute/). +To contribute to any Microsoft docs, see the [contributor guide overview](https://learn.microsoft.com/contribute/). -To know more about Microsoft standards and style guide, see [Microsoft style guide](https://docs.microsoft.com/style-guide/welcome/). +To know more about Microsoft standards and style guide, see [Microsoft style guide](https://learn.microsoft.com/style-guide/welcome/). Most contributions require you to agree to a **Contributor License Agreement (CLA)** declaring that you have the right to contribute and grant us the rights to use your contribution. See [CLA](https://cla.microsoft.com/). This project adopts the [Microsoft Open Source code of conduct](https://opensour ## Learning resources -* [Teams Toolkit fundamentals](https://docs.microsoft.com/microsoftteams/platform/toolkit/teams-toolkit-fundamentals/) -* [Teams Toolkit for Visual Studio](https://docs.microsoft.com/microsoftteams/platform/toolkit/visual-studio-overview/) -* [TeamsFx SDK for TypeScript or JavaScript](https://docs.microsoft.com/microsoftteams/platform/toolkit/teamsfx-sdk/) -* [Teams JavaScript client SDK](https://docs.microsoft.com/microsoftteams/platform/tabs/how-to/using-teams-client-sdk/) and [Teams JavaScript client SDK v2 preview](https://docs.microsoft.com/microsoftteams/platform/m365-apps/using-teams-client-sdk-preview?tabs=manifest-teams-toolkit%2Cjavascript/) -* [Microsoft Graph SDKs](https://docs.microsoft.com/graph/sdks/sdks-overview/) -* [Bots SDK (v3)](https://docs.microsoft.com/microsoftteams/platform/resources/bot-v3/bots-overview/) -* [Messaging extensions SDK (v3)](https://docs.microsoft.com/microsoftteams/platform/resources/messaging-extension-v3/messaging-extensions-overview/) +* [Teams Toolkit fundamentals](https://learn.microsoft.com/microsoftteams/platform/toolkit/teams-toolkit-fundamentals/) +* [Teams Toolkit for Visual Studio](https://learn.microsoft.com/microsoftteams/platform/toolkit/visual-studio-overview/) +* [TeamsFx SDK for TypeScript or JavaScript](https://learn.microsoft.com/microsoftteams/platform/toolkit/teamsfx-sdk/) +* [Teams JavaScript client SDK](https://learn.microsoft.com/microsoftteams/platform/tabs/how-to/using-teams-client-sdk/) and [Teams JavaScript client SDK v2 preview](https://learn.microsoft.com/microsoftteams/platform/m365-apps/using-teams-client-sdk-preview?tabs=manifest-teams-toolkit%2Cjavascript/) +* [Microsoft Graph SDKs](https://learn.microsoft.com/graph/sdks/sdks-overview/) +* [Bots SDK (v3)](https://learn.microsoft.com/microsoftteams/platform/resources/bot-v3/bots-overview/) +* [Messaging extensions SDK (v3)](https://learn.microsoft.com/microsoftteams/platform/resources/messaging-extension-v3/messaging-extensions-overview/) -See [additional Git and GitHub resources](https://docs.microsoft.com/contribute/additional-resources). +See [additional Git and GitHub resources](https://learn.microsoft.com/contribute/additional-resources). |
|
| platform | Teams Contributor Reference | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/teams-contributor-reference.md | -Teams documentation is part of the **Microsoft Docs** technical documentation library. The content is organized into groups called docsets, each representing a group of related documents managed as a single entity. Articles in the same docset have the same URL path extension after **docs.microsoft.com**. For example, `/docs.microsoft.com/microsoftteams/...` is the beginning of the Teams docset file path. Teams articles are written in Markdown syntax and hosted on GitHub. +Teams documentation is part of the **Microsoft Docs** technical documentation library. The content is organized into groups called docsets, each representing a group of related documents managed as a single entity. Articles in the same docset have the same URL path extension after `learn.microsoft.com`. For example, `/learn.microsoft.com/microsoftteams/...` is the beginning of the Teams docset file path. Teams articles are written in Markdown syntax and hosted on GitHub. ## Set up your workspace |
| platform | Cards Actions | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-actions.md | var button = new CardAction() { Type = ActionTypes.OpenUrl, Title = "Tabs in Teams",- Value = "https://docs.microsoft.com/en-us/microsoftteams/platform/" + Value = "https://learn.microsoft.com/en-us/microsoftteams/platform/" }; ``` CardFactory.actions([ { type: 'openUrl', Title: 'Tabs in Teams',- value: 'https://docs.microsoft.com/en-us/microsoftteams/platform/' + value: 'https://learn.microsoft.com/en-us/microsoftteams/platform/' }]) ``` |
| platform | Debug Local | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/debug-local.md | Teams Toolkit helps you to debug and preview your Microsoft Teams app locally. D ::: zone pivot="visual-studio-code" -## Debug your Teams app locally for Visual Studio Code --Teams Toolkit helps you to debug and preview your Teams app locally. During the debug process, Teams Toolkit automatically starts app services, launches debuggers, and side-loads the Teams app. You can preview your Teams app in Teams web client locally after debugging. -- ## Debug your Microsoft Teams app locally for Visual Studio Code Teams Toolkit in Visual Studio Code gives you the features to automate debugging of your Teams app locally. Visual Studio allows you to debug tab, bot, and message extension. You need to set up Teams Toolkit before you debug your app. The configuration **Attach to Frontend** or **Launch Bot** launches a Edge or Ch ::: zone pivot="visual-studio" -## Debug your Microsoft Teams app locally using Visual Studio +## Debug your Teams app locally using Visual Studio Teams Toolkit helps you to debug and preview your Microsoft Teams app locally. Visual Studio allows you to debug tab, bot, and message extension. You can debug your app locally in Visual Studio using Teams Toolkit by performing: Perform the following steps using the Teams Toolkit to debug your app after you * [Add capabilities to your Teams apps](add-capability.md) * [Deploy to the cloud](deploy.md) * [Manage multiple environments in Teams Toolkit](TeamsFx-multi-env.md)-* [Provision cloud resources using Visual Studio](provision-cloud-resources.md) -* [Deploy Teams app to the cloud using Visual Studio](deploy-teams-app.md) -* [Edit Teams app manifest using Visual Studio](VS-TeamsFx-preview-and-customize-app-manifest.md) |
| platform | Debug Overview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/debug-overview.md | Teams Toolkit helps you to debug and preview your Microsoft Teams app. Debug is Teams Toolkit in Microsoft Visual Studio Code automates the debug process. You can detect errors and fix them as well as preview the teams app. You can also customize debug settings to create your tab or bot. -Teams Toolkit helps you to debug and preview your Teams app. Debug is the process of checking, detecting, and correcting issues or bugs to ensure the program runs successfully in Teams. -- ## Debug your Microsoft Teams app for Visual Studio Code Teams Toolkit in Visual Studio Code automates the debug process. You can detect errors and fix them as well as preview the teams app. You can also customize debug settings to create your tab or bot. Teams Toolkit utilizes Visual Studio Code multi-target debugging to debug tab, b ::: zone pivot="visual-studio" -## Debug your Microsoft Teams app using Visual Studio +## Debug your Teams app using Visual Studio Teams Toolkit automates app startup services, initiates debug, and side loads Teams app. After debug, you can preview the Teams app in Teams web client. You can also customize debug settings to use your bot endpoints, or environment variables to load your configured app. Visual Studio allows you to debug tab, bot, and message extension. During the debug process, Teams Toolkit supports the following debug features: You can launch Teams app as a web app instead of running in Teams client. * [Use Teams Toolkit to provision cloud resources](provision.md) * [Deploy to the cloud](deploy.md) * [Preview and customize Teams app manifest](TeamsFx-preview-and-customize-app-manifest.md)-* [Provision cloud resources using Visual Studio](provision-cloud-resources.md) -* [Deploy Teams app to the cloud using Visual Studio](deploy-teams-app.md) -* [Edit Teams app manifest using Visual Studio](VS-TeamsFx-preview-and-customize-app-manifest.md) |
| platform | Connectors Using | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/connectors-using.md | An example of connector message is as follows: "actions": [{ "@type": "HttpPOST", "name": "Add comment",- "target": "https://docs.microsoft.com/outlook/actionable-messages" + "target": "https://learn.microsoft.com/outlook/actionable-messages" }] }, { "@type": "ActionCard", An example of connector message is as follows: "actions": [{ "@type": "HttpPOST", "name": "Save",- "target": "https://docs.microsoft.com/outlook/actionable-messages" + "target": "https://learn.microsoft.com/outlook/actionable-messages" }] }, { "@type": "OpenUri", "name": "Learn More", "targets": [{ "os": "default",- "uri": "https://docs.microsoft.com/outlook/actionable-messages" + "uri": "https://learn.microsoft.com/outlook/actionable-messages" }] }, { "@type": "ActionCard", An example of connector message is as follows: "actions": [{ "@type": "HttpPOST", "name": "Save",- "target": "https://docs.microsoft.com/outlook/actionable-messages" + "target": "https://learn.microsoft.com/outlook/actionable-messages" }] }] } |