|Service||Microsoft Docs article||Related commit history on GitHub||Change details|
|platform||Notification Bot In Teams||https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/notification-bot-in-teams.md||
Follow the [step-by-step](../../../sbs-gs-notificationbot.yml) guide to build Te* [Adaptive Cards](../../../task-modules-and-cards/cards/cards-reference.md#adaptive-card) * [TeamsFx SDK](../../../toolkit/TeamsFx-SDK.md) * [Bot Framework SDK](/azure/bot-service/bot-builder-basics)
+* [Send proactive installation messages](../../../graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md)
Create the link using the following URL appended with your app ID: `https://team## Stop app distribution
-You can remove an app from the [Microsoft commercial marketplace](/azure/marketplace/overview) to prevent its discovery and use.
+You can remove an app from the [Microsoft commercial marketplace](/azure/marketplace/overview) and the Microsoft Teams store to prevent its discovery and use.To stop distribution of an app after you've published, follow the steps:
-1. On the **Product overview** page, select **Stop selling**. It removes the app from the Microsoft AppSource.
-1. To initiate de-listing of the app, on **Partner Center**, select the **Overview** page, and then select **Stop selling**.
+1. In **Partner Center**, on the **Product overview** page, select **Stop selling**. It removes the app from the Microsoft AppSource.
+1. To initiate de-listing of the app from the Microsoft Teams store, write to [apphealthevaluation](mailto:email@example.com).After you stop the distribution of an app, you can still see it in Partner Center with a **Not available** status. If you decide to list the app again, follow the instructions to [Publish your app to the Microsoft Teams store](../publish.md).
|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||
Learn more about the differences between a notification bot and Incoming Webhook| Installation required | Yes | No | | Suitable scenarios | ΓÇó Receive regular notifications and messages periodically, for example, receive daily notification of team tasks. <br> ΓÇó Receive notifications and messages based on real events. For example, once teammates upload files, you receive notifications. | Communicate with external apps and receive notifications and messages from other apps. | | Scope configuration | ΓÇó Teams channel <br> ΓÇó Group chat <br> ΓÇó Personal chat | Teams channel |
-| Message process | A notification not works as a Teams application. You can define your business logic to process data and show data in a customized format. | Webhook is a Teams feature rather than a Teams application, so it only receives and shows data without processing. |
+| Message process | A notification bot works as a Teams application. You can define your business logic to process data and show data in a customized format. | Webhook is a Teams feature rather than a Teams application, so it only receives and shows data without processing. || Retrieve Teams context | Notification bot can retrieve Teams context such as the channel or user information, messages, etc. | No | | Send Adaptive Card | Yes | Yes | | Send a welcome message | Yes | No |