| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Bots Filesv4 | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/bots-filesv4.md | There are two ways to send files to and receive files from a bot: * [**Use the Teams bot APIs:**](#use-the-teams-bot-apis) These only support files in `personal` context. +The following video demonstrates how a bot simplifies the process of sending and receiving files with ease and efficiency: ++<br> ++> [!VIDEO https://www.youtube.com/embed/-UeDi5X3qWk] + ## Use the Graph APIs Post messages with card attachments that refer to existing SharePoint files, using the Graph APIs for [OneDrive and SharePoint](/onedrive/developer/rest-api/). To use the Graph APIs, obtain access to either of the following through the standard OAuth 2.0 authorization flow: |
| platform | Subscribe To Conversation Events | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md | When building your conversational bots for Microsoft Teams, you can work with co * Trigger a notification when a bot message is liked by a user. * Identify the default channel for your bot from user input (selection) during installation. +The following video demonstrates how a conversation bot can improve customer engagement through smooth, intelligent interactions: ++<br> ++> [!VIDEO https://www.youtube.com/embed/HWw99yPsAes] + ## Conversation update events You can use conversation update events to provide better notifications and effective bot actions. |
| platform | Publish | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/deploy-and-publish/appsource/publish.md | You can distribute your app directly to the Microsoft Teams Store inside Microso Apps published to the Teams Store also automatically list on [the Microsoft commercial marketplace](https://appsource.microsoft.com), which is the official marketplace for Microsoft 365 apps and solutions. +The following video on publish your Teams app to Teams Store outlines the steps involved in the app publishing process: ++<br> ++> [!VIDEO https://www.youtube.com/embed/cFqAuLy0JaE] + ## Understand the publishing process If your app is production ready, you can begin the process of getting it listed on the Teams Store. |
| platform | Manifest Schema Dev Preview | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema-dev-preview.md | App manifest describes how the app integrates into the Microsoft Teams platform. "canUpdateConfiguration": true, "scopes": [ "team",- "groupchat" + "groupChat" ], "context": [] } App manifest describes how the app integrates into the Microsoft Teams platform. "scopes": [ "team", "personal",- "groupchat" + "groupChat" ], "supportsFiles": true, "commandLists": [ { "scopes": [ "team",- "groupchat" + "groupChat" ], "commands": [ { App manifest describes how the app integrates into the Microsoft Teams platform. { "scopes": [ "personal",- "groupchat" + "groupChat" ], "commands": [ { When a group install scope is selected, it defines the default capability when t |Name| Type| Maximum size | Required | Description| |||||| |`team`|String|||When the install scope selected is `team`, this field specifies the default capability available. <br>Options: `tab`, `bot`, or `connector`.|-|`groupchat`|String|||When the install scope selected is `groupchat`, this field specifies the default capability available. <br>Options: `tab`, `bot`, or `connector`.| +|`groupchat`|String|||When the install scope selected is `groupChat`, this field specifies the default capability available. <br>Options: `tab`, `bot`, or `connector`.| |`meetings`|String|||When the install scope selected is `meetings`, this field specifies the default capability available. <br>Options: `tab`, `bot`, or `connector`.| ## subscriptionOffer |
| platform | Manifest Schema | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/resources/schema/manifest-schema.md | The following is the sample app manifest schema: "defaultGroupCapability": { "meetings": "tab", "team": "bot",- "groupChat": "bot" + "groupchat": "bot" }, "configurableProperties": [ "name", When a group install scope is selected, it defines the default capability when t |Name| Type| Maximum size | Required | Description| |||||| |`team`|String|||When the install scope selected is `team`, this field specifies the default capability available. Options: `tab`, `bot`, or `connector`.|-|`groupChat`|String|||When the install scope selected is `groupChat`, this field specifies the default capability available. Options: `tab`, `bot`, or `connector`.| +|`groupchat`|String|||When the install scope selected is `groupChat`, this field specifies the default capability available. Options: `tab`, `bot`, or `connector`.| |`meetings`|String|||When the install scope selected is `meetings`, this field specifies the default capability available. Options: `tab`, `bot`, or `connector`.| ## configurableProperties |