Docs update tracker

Updates from: 09/24/2022 01:25:53

Service	Microsoft Docs article	Related commit history on GitHub	Change details
platform	Send Proactive Messages	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/send-proactive-messages.md	A proactive message is any message sent by a bot that isn't in response to a req * Scheduled messages > [!IMPORTANT] -> Bots are available in Government Community Cloud (GCC) and GCC-High but not in Department of Defense (DOD) environments. > -> For proactive messages the bots should use the following end points for government cloud environments: +> * To send proactive message, it's recommended to start with [building notification bot with JavaScript](../../../sbs-gs-notificationbot.yml) or [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification). To get started, download [Teams Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) explore. For more information, see [Teams Toolkit documents](../../../toolkit/teams-toolkit-fundamentals.md). > -> * GCC: `https://smba.infra.gcc.teams.microsoft.com/gcc`. -> * GCCH: `https://smba.infra.gov.teams.microsoft.us/gcch`. +> * Currently, bots are available in Government Community Cloud (GCC) and GCC-High but not in Department of Defense (DOD). For proactive messages the bots should use the following end points for government cloud environments: <br> - GCC: `https://smba.infra.gcc.teams.microsoft.com/gcc`<br> - GCCH: `https://smba.infra.gov.teams.microsoft.us/gcch`. To send a proactive message to a user, a group chat, or a team, your bot must have the requisite access to send the message. For a group chat or team, the app that contains your bot must be first installed in that location. See the following video to learn how to send proactive message from bots: <br> -> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4NHyk] +> [!VIDEO <https://www.microsoft.com/en-us/videoplayer/embed/RE4NHyk>] <br> ### Understand who blocked, muted, or uninstalled a bot
platform	What Are Bots	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/what-are-bots.md	# Build bots for Teams -> [!NOTE] -> It's recommended that you'd create your first bot app or notification bot app using the new generation development tool for Teams. For more information, see [Teams Toolkit for Visual Studio Code](../toolkit/teams-toolkit-fundamentals.md) and [Teams Toolkit for Visual Studio](../toolkit/teams-toolkit-overview-visual-studio.md). - A bot is also referred to as a chatbot or conversational bot. It's an app that runs simple and repetitive tasks by users such as customer service or support staff. Everyday use of bots include, bots that provide information about the weather, make dinner reservations, or provide travel information. Interactions with bots can be quick questions and answers or complex conversations. +> [!NOTE] +> It's recommended to start with [build your first bot app using JavaScript](../sbs-gs-bot.yml) or [build notification bot with JavaScript](../sbs-gs-notificationbot.yml) by using the new generation development tool for Teams. For more information, see [Teams Toolkit overview](../toolkit/teams-toolkit-fundamentals.md). + > [!IMPORTANT] > > * Currently, bots are available in Government Community Cloud (GCC) and GCC-High but not in Department of Defense (DOD).
platform	Manifest Schema Dev Preview	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema-dev-preview.md	Delegated permissions allow the app to access data on behalf of the signed-in us \|`ChannelMeetingParticipant.Read.Group`\| Allows the app to read participant information, including name, role, id, joined, and left times, of channel meetings associated with this team, on behalf of the signed-in user.\| \|`InAppPurchase.Allow.Group`\| Allows the app to show marketplace offers to users in this team and complete their purchases within the app, on behalf of the signed-in user.\| \|`ChannelMeetingStage.Write.Group`\| Allows the app to show content on the meeting stage in channel meetings associated with this team, on behalf of the signed-in user.\| + \|`LiveShareSession.ReadWrite.Group`\|Allows the app to create and synchronize Live Share sessions for meetings associated with this team, and access related information about the meeting's roster, such as member's meeting role, on behalf of the signed-in user.\| * Resource-specific delegated permissions for chats or meetings Delegated permissions allow the app to access data on behalf of the signed-in us \|`MeetingStage.Write.Chat`\|Allows the app to show content on the meeting stage in meetings associated with this chat, on behalf of the signed-in user.\| \|`OnlineMeetingParticipant.Read.Chat`\|Allows the app to read participant information, including name, role, id, joined, and left times, of meeting associated with this chat, on behalf of the signed-in user.\| \|`OnlineMeetingParticipant.ToggleIncomingAudio.Chat`\|Allows the app to toggle incoming audio for participants in meetings associated with this chat, on behalf of the signed-in user.\| + \|`LiveShareSession.ReadWrite.Chat`\|Allows the app to create and synchronize Live Share sessions for meetings associated with this chat, and access related information about the meeting's roster, such as member's meeting role, on behalf of the signed-in user.\| + \|`OnlineMeetingIncomingAudio.Detect.Chat`\|Allows the app to detect changes in the status of incoming audio in meetings associated with this chat, on behalf of the signed-in user.\| * Resource-specific delegated permissions for users Delegated permissions allow the app to access data on behalf of the signed-in us \|\|\| \|`InAppPurchase.Allow.User`\|Allows the app to show the user marketplace offers and complete the user's purchases within the app, on behalf of the signed-in user.\| -* Resource-specific permissions for Teams live share - - \|Name\| Description \| - \| -- \| -- \| - \|`LiveShareSession.ReadWrite.Chat`\|<! need info >\| - \|`LiveShareSession.ReadWrite.Channel`\|<! need info >\| - \|`MeetingStage.Write.Chat`\|<! need info >\| - \|`OnlineMeetingIncomingAudio.Detect.Chat`\|<! need info >\| - ## See also * [Understand the Microsoft Teams app structure](~/concepts/design/app-structure.md)
platform	Manifest Schema	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md	Delegated permissions allow the app to access data on behalf of the signed-in us \|`ChannelMeetingParticipant.Read.Group`\| Allows the app to read participant information, including name, role, id, joined, and left times, of channel meetings associated with this team, on behalf of the signed-in user.\| \|`InAppPurchase.Allow.Group`\| Allows the app to show marketplace offers to users in this team and complete their purchases within the app, on behalf of the signed-in user.\| \|`ChannelMeetingStage.Write.Group`\| Allows the app to show content on the meeting stage in channel meetings associated with this team, on behalf of the signed-in user.\| + \|`LiveShareSession.ReadWrite.Group`\|Allows the app to create and synchronize Live Share sessions for meetings associated with this team, and access related information about the meeting's roster, such as member's meeting role, on behalf of the signed-in user.\| * Resource-specific delegated permissions for chats or meetings Delegated permissions allow the app to access data on behalf of the signed-in us \|`MeetingStage.Write.Chat`\|Allows the app to show content on the meeting stage in meetings associated with this chat, on behalf of the signed-in user.\| \|`OnlineMeetingParticipant.Read.Chat`\|Allows the app to read participant information, including name, role, id, joined, and left times, of meeting associated with this chat, on behalf of the signed-in user.\| \|`OnlineMeetingParticipant.ToggleIncomingAudio.Chat`\|Allows the app to toggle incoming audio for participants in meetings associated with this chat, on behalf of the signed-in user.\| + \|`LiveShareSession.ReadWrite.Chat`\|Allows the app to create and synchronize Live Share sessions for meetings associated with this chat, and access related information about the meeting's roster, such as member's meeting role, on behalf of the signed-in user.\| + \|`OnlineMeetingIncomingAudio.Detect.Chat`\|Allows the app to detect changes in the status of incoming audio in meetings associated with this chat, on behalf of the signed-in user.\| * Resource-specific delegated permissions for users
platform	Teamsfx Preview And Customize App Manifest	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/TeamsFx-preview-and-customize-app-manifest.md	The following steps help to preview local manifest file by using preview option 1. Select Preview in the codelens of `manifest.template.json` file. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png" alt-text="Preview"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png" alt-text="Screenshot is an example showing the preview in the codelens of manifest file."::: 1. Select local. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-env1.png" alt-text="Select environment1"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-env1.png" alt-text="Screenshot is an example of showing the selection of local in the environment."::: The following steps help to preview local manifest file by using Zip Teams metadata package option: 1. Select `manifest.template.json` file. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-manifest-json.png" alt-text="Select Manifest"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-manifest-json.png" alt-text="Screenshot is an example of showing the selection of manifest.template.json."::: 1. Select the Teams Toolkit :::image type="icon" source="../assets/images/teams-toolkit-v2/teams-toolkit-sidebar-icon.PNG"::: icon in the Visual Studio Code toolbar. 1. Select Zip Teams metadata package under DEPLOYMENT. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/teams-metadata-package.png" alt-text="Select Teams metadata package"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/teams-metadata-package.png" alt-text="Screenshot is an example of showing the selection of zip Teams metadata package."::: 1. Select local. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-env1.png" alt-text="Select environment"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-env1.png" alt-text="Screenshot is an example of showing the selection of local in the environment."::: The preview local appears as shown in the image: ## Preview manifest file in remote environment To preview manifest file using Visual Studio Code: * Select Provision in the cloud under DEVELOPMENT in Teams Toolkit extension - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/provision.png" alt-text="Provision cloud resource"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/provision.png" alt-text="Screenshot is an example of showing the selection of provision in the cloud resource."::: To preview manifest file using command palatte: * Trigger Teams: Provision in the cloud from command palette. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/command palatte.png" alt-text="Provision cloud resource using command palatte"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/command palatte.png" alt-text="Screenshot is an example of showing provision cloud resource using command palatte."::: It generates configuration for remote Teams app, and builds package and preview manifest under `build/appPackage` folder. The following steps help to preview manifest file by using preview option in cod 1. Select Preview in the codelens of `manifest.template.json` file. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png" alt-text="Preview"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/preview-23.png" alt-text="Screenshot is an example of showing preview in the codelens of manifest file."::: 1. Select your environment. > [!NOTE] > If there are more than one environment, you need to select the environment you want to preview as shown in the image: - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/manifest preview-1.png" alt-text="Add env"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/manifest preview-1.png" alt-text="Screenshot is an example of showing the adding of environment."::: The following steps help to preview manifest file by using Zip Teams metadata package option in remote environment: 1. Select `manifest.template.json` file. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-manifest-json.png" alt-text="Select Manifest"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/select-manifest-json.png" alt-text="Screenshot is an example of showing the selection of manifest.template.json."::: 1. Select the Teams Toolkit :::image type="icon" source="../assets/images/teams-toolkit-v2/teams-toolkit-sidebar-icon.PNG"::: icon in the Visual Studio Code toolbar. 1. Select Zip Teams metadata package under DEPLOYMENT. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/teams-metadata-package.png" alt-text="Select Teams metadata package"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/teams-metadata-package.png" alt-text="Screenshot is an example of showing the selection of zip Teams metadata package."::: 1. Select your environment. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/manifest preview-1.png" alt-text="Add env"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/manifest preview-1.png" alt-text="Screenshot is an example of showing the adding of environment."::: > [!NOTE] > If there are more than one environment, you need to select the environment you want to preview as shown in the image: After previewing the manifest file, you can sync your local changes to Developer * Go to `manifest.template.json` file, and right-click to select `Deploy Teams app manifest` from context menu. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/deploy-manifest.png" alt-text="Deploy manifest"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/deploy-manifest.png" alt-text="Screenshot is an example of showing the selection of deploy Teams app manifest."::: * Trigger `Teams: Deploy Teams app manifest` from command palette. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/deploy-command.png" alt-text="Deploy from command palette"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/deploy-command.png" alt-text="Screenshot is an example of showing the deploy from command palette."::: 2. Update to Teams platform. After previewing the manifest file, you can sync your local changes to Developer * Trigger Teams: Update manifest to Teams platform on the menu bar of `manifest.{env}.json`. - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/update-to-teams.png" alt-text="Update to teams"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/update-to-teams.png" alt-text="Screenshot is an example of showing the update to Teams platform on the menu bar of manifest."::: You can also trigger Teams: Update manifest to Teams platform from the command palette: > [!NOTE] > Trigger from editor codelens or menu bar updates current manifest file to Teams platform. Trigger from command palette requires selecting target environment. If the manifest file is outdated due to configuration file change or template ch * Preview and update: Local manifest file is overwritten according to current configuration and also updated to Teams platform. * Cancel: No action is taken. ## Customize your Teams app manifest During operations such as, Zip Teams metadata package, Teams Toolkit validat * In VSC, trigger `Teams: Validate manifest file` from command palette: - :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/validate.png" alt-text="Validate file"::: + :::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/validate.png" alt-text="Screenshot is an example of showing Teams validate manifest file from command palette."::: * In CLI, use command: During operations such as, Zip Teams metadata package, Teams Toolkit validat In `manifest.template.json`, you can navigate to codelens to preview the values for `local` and `dev` environment. > [!NOTE] > Provision the environment or execute local debug to generate values for placeholders. You can navigate to state file or configuration file by selecting the codelens, which provides a drop-down list with all the environment names. After selecting one environment, the corresponding state file or configuration file opens. To preview values for all the environments, you can hover over the placeholder. It shows a list with environment names and corresponding values. If you haven't provisioned the environment or executed the local debug, select `Trigger Teams: Provision in the cloud command to see placeholder value` or `Trigger local debug to see placeholder value`. ::: zone-end After scaffolding, in the manifest template file under `templates/appPackage` fo In the manifest template, select Project > Teams Toolkit > Open Manifest File. ### Customize app manifest in Teams Toolkit You can preview values in app manifest in two ways: * When you hover over the placeholder in `manifest.template.json`, then you can see the values for dev and local environment. - :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-placeholder1.png" alt-text="Hover over placeholder" lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-placeholder1.png"::: + :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-placeholder1.png" alt-text="Screenshot is an example showing when you hover over placeholder, can view the values for dev and local environment." lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-placeholder1.png"::: * You can also hover over the key besides each placeholder in `manifest.template.json`, and you can see the same values for dev and local environment. - :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-key-placeholder.png" alt-text="Hover over key beside placeholder" lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-key-placeholder.png"::: + :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-key-placeholder.png" alt-text="Screenshot is an example showing when you hover over key beside placeholder can view the same values for dev and local environment." lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-hover-key-placeholder.png"::: > [!NOTE] > If the environment has not been provisioned, or the Teams app dependencies have not been prepared, it indicates that the values for placeholder have not been generated. Please follow the guidance inside hover to generate corresponding values. To preview the manifest file, you can sideload for local or deploy for Azure. Yo * Select Project > Teams Toolkit and trigger Prepare Teams App Dependencies or Provision in the Cloud that generates configuration for local or remote Teams app. - :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview-manifest1.png" alt-text="Preview manifest file" lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview-manifest1.png"::: + :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview-manifest1.png" alt-text="Screenshot is an example of showing preview manifest file." lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview-manifest1.png"::: There are two other ways to upload zip app package before you can preview manifest file: 1. From the list of menu select Project > Teams Toolkit > Zip App Package, and select For Local or For Azure. - :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-zip1.png" alt-text="Zip app package" lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-zip1.png"::: + :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-zip1.png" alt-text="Screenshot is an example of showing the navigation to zip app package for local and azure." lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-zip1.png"::: 1. You can also upload zip app package from Solution Explorer, if you right-click on MyTeamsApp1 and then select Teams Toolkit > Zip App Package > For Local or For Azure. > [!NOTE] > In this scenario the project name is MyTeamsApp1. - :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-solution-explorer1.png" alt-text="List of Teams Toolkit menus from solution explorer" lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-solution-explorer1.png"::: + :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-solution-explorer1.png" alt-text="Screenshot is an example of showing the list of Teams toolkit menus from solution explorer." lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-solution-explorer1.png"::: Teams Toolkit generates the zip app package, and to preview manifest file content you can follow the step below: * Right-click on manifest.template.json under appPackage folder, select Preview Manifest File > For Local or For Azure. - :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview1.png" alt-text="Preview context menu" lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview1.png"::: + :::image type="content" source="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview1.png" alt-text="Screenshot is an example of showing the preview manifest menu for local and azure." lightbox="../assets/images/Tools-and-SDK-revamp/edit-manifest-for-visual-studio/vs-preview1.png"::: This displays the preview of the manifest file in Visual Studio. This displays the preview of the manifest file in Visual Studio. After you've previewed the manifest file in Visual Studio, you can now sync the local changes to the Developer Portal. Select Project > Teams Toolkit > Update Manifest in Teams Developer Portal, or context menu from Solution Explorer. You can now preview the manifest file in Developer Portal as a result of syncing the local changes. + +The changes are updated to Teams Developer Portal. > [!NOTE] -> The changes are updated to Teams Developer Portal. If you have some manual updates in Developer Portal, that can be overwritten. In the Warning dialog box you can select Overwrite and update or Cancel. +> +> * Select Overwrite and update or Cancel from the Warning dialog box to make any maual updates that can be overwritten in the Develope Portal. +> * When you create a Teams command bot using Visual Studio, two app IDs are registered in Azure Active Directory. You can identify the app IDs in the Developer Portal as Application client ID under Basic information and existing Bot ID under App features. ::: zone-end
platform	Install Teams Toolkit	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/toolkit/install-Teams-Toolkit.md	Title: Install Teams Toolkit -description: In this module, learn Installation of Teams Toolkit +description: In this module, learn installation of Teams Toolkit ms.localizationpriority: medium
platform	Add Incoming Webhook	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md	An Incoming Webhook lets external applications to share content in Microsoft Tea * Message extensions * Connectors +> [!IMPORTANT] +> You can choose to build notification bot Teams app other than incoming webhooks. They perform similarly but notification bot has more functionalities. For more information, see [Build notification bot with JavaScript](../../sbs-gs-notificationbot.yml) or [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification). To get started, download [Teams Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) now and explore. For more information, see [Teams Toolkit documents](../../toolkit/teams-toolkit-fundamentals.md). + See the following video to learn how to create an Incoming Webhooks: <br> -> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4ODcY] +> [!VIDEO <https://www.microsoft.com/en-us/videoplayer/embed/RE4ODcY>] ## Key features of an Incoming Webhook To remove an Incoming Webhook from a Teams channel, follow these steps: ## Code sample -\| Sample Name \| Description \| C# \| Node.js \| +\| Sample Name \| Description \| C# \| TypeScript \| \|:\|:--\|:\|:--\| -\|Incoming Webhook\|This sample code demonstrates how to send card using incoming webhook. \|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/incoming-webhook/csharp)\|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/incoming-webhook/nodejs) \| +\|Incoming Webhook\|This sample code demonstrates how to send card using incoming webhook. \|[View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/incoming-webhook/csharp)\|[View](https://github.com/OfficeDev/TeamsFx-Samples/tree/release/incoming-webhook-notification) \| ## See also
platform	What Are Webhooks And Connectors	https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md	# Webhooks and connectors -Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams. Webhooks are user defined HTTP callback that notifies users about any action that has taken place in the Teams channel. It is a way for an app to get real time data. Connectors allow users to subscribe to receive notifications and messages from your web services. They expose an HTTPS endpoint for your service to post messages in the form of cards. +Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams. Webhooks are user defined HTTP callback that notifies users about any action that has taken place in the Teams channel. It's a way for an app to get real time data. Connectors allow users to subscribe to receive notifications and messages from your web services. They expose an HTTPS endpoint for your service to post messages in the form of cards. + +> [!IMPORTANT] +> You can choose to build notification bot Teams app other than incoming webhooks. They perform similarly but notification bot has more functionalities. For more information, see [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) or [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification). To get started, download [Teams Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) now and explore. For more information, see [Teams Toolkit documents](../toolkit/teams-toolkit-fundamentals.md). ## Outgoing Webhooks -Webhooks help Teams to integrate with external apps. With Outgoing Webhooks, you can send text messages from a channel to the web services. After configuring the Outgoing Webhooks, users can @mention Outgoing Webhook and send a message to web services. The service responds within ten seconds to the message with a text or a card. +Webhooks help Teams to integrate with external apps. With Outgoing Webhooks, you can send text messages from a channel to the web services. After configuring the Outgoing Webhooks, users can @mention Outgoing Webhook and send a message to web services. The service responds within 10 seconds to the message with a text or a card. > [!NOTE] > Outgoing Webhooks are configured on a per team basis and cannot be included as part of a normal Teams app. Connectors allow users to subscribe to receive notifications and messages from t Incoming Webhooks help in posting messages from apps to Teams. If Incoming Webhooks are enabled for a team in any channel, it exposes the HTTPS endpoint, which accepts correctly formatted JSON and inserts the messages into that channel. For example, you can create an Incoming Webhook in your DevOps channel, configure your build, and simultaneously deploy and monitor services to send alerts. -#### Notification bot or incoming webhook - choose the right one! +#### Notification bot or incoming webhook - choose the right one Before you start to learn how to build Incoming webhooks, you may also want to know that you can build Notification Bot using Teams Toolkit. Notification Bots can enable more customizable experience to meet different business scenarios. Learn more about the differences between Notification Bot and Incoming webhook s \| Send Adaptive Card \| Yes \| Yes \| \| Send a welcome message \| Can send a welcome message \| No welcome message \| \| Trigger Supported \| All triggers supported. If you use Teams Toolkit, you can quickly get template projects with following triggers: <br> ΓÇó Time trigger hosted on Azure functions. <br> ΓÇó Restify HTTP trigger hosted on Azure app service <br> ΓÇó HTTP trigger hosted on Azure Functions \| All triggers supported \| -\| Building Tools \| ΓÇó [Teams Toolkit Overview for Visual Studio Code](../toolkit/teams-toolkit-fundamentals.md) <br> ΓÇó [Teams Toolkit overview for Visual Studio](../toolkit/teams-toolkit-overview-visual-studio.md) <br> ΓÇó [TeamsFx Library](../toolkit/TeamsFx-CLI.md) <br> ΓÇó [TeamsFx SDK](../toolkit/TeamsFx-SDK.md) \| No tools required \| +\| Building Tools \| ΓÇó [Teams Toolkit Overview for Visual Studio Code](../toolkit/teams-toolkit-fundamentals.md) <br> ΓÇó [Teams Toolkit overview for Visual Studio](../toolkit/teams-toolkit-fundamentals.md) <br> ΓÇó [TeamsFx Library](../toolkit/TeamsFx-CLI.md) <br> ΓÇó [TeamsFx SDK](../toolkit/TeamsFx-SDK.md) \| No tools required \| \| Cloud resource required \| Azure Bot Framework \| No resources required \| -\| Tutorial \| [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) \| NA \| +\| Tutorial \| [Build notification bot with JavaScript](../sbs-gs-notificationbot.yml) \| [incoming webhook notification sample](https://github.com/OfficeDev/TeamsFx-Samples/tree/dev/incoming-webhook-notification) \| ### Office 365 Connectors -Office 365 Connectors allow you to create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You send messages primarily using Office 365 Connector cards and have the ability to add a limited set of card actions to them. For example, a weather connector that allows users to select a location and a time of day, to receive updates about tomorrow's weather. They are configured on a channel level but are installed at a team level. +Office 365 Connectors allow you to create a custom configuration page for your Incoming Webhook and package them as part of a Teams app. You send messages primarily using Office 365 Connector cards and have the ability to add a limited set of card actions to them. For example, a weather connector that allows users to select a location and any time of the day, to receive updates about tomorrow's weather. They're configured at channel level but are installed at team level. > [!NOTE] > You can distribute the Office 365 Connector Teams app to our AppStore.