| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | Create A Bot Commands Menu | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/bots/how-to/create-a-bot-commands-menu.md | Following are the command menu best practices: * [Build bots for Teams](../what-are-bots.md) * [App manifest schema for Teams](../../resources/schem) * [Messages in bot conversations](conversations/conversation-messages.md)+* [Adaptive Cards for bot developers](/adaptive-cards/getting-started/bots) |
| platform | Teams Developer Portal | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/concepts/build-and-test/teams-developer-portal.md | Follow the steps to import and manage your existing app in Developer Portal: * Developer Portal creates a unique app ID and locks the ID for your registered Teams app. You canΓÇÖt edit or provide an ID of your choice, which prevents to have duplicate app IDs for multiple apps. * If you create an app using the Microsoft Teams Toolkit for Visual Studio Code, you can manage your app in Developer Portal.- * You can import an existing app which you created on App Studio to Developer Portal. To import an already published app to Developer Portal, the [app owner](~/concepts/build-and-test/manage-your-apps-in-developer-portal.md#advanced) needs to raise a service request through [admin portal](https://admin.microsoft.com/Adminportal/Home?#/support) to transfer the ownership over the app ID. + * You can import an existing app to Developer Portal that was created in App Studio. If an app in your tenant doesn't have an owner, the Teams Tenant admin or Global admin can take ownership of the app from Teams Developer Portal. ++ :::image type="content" source="../../assets/images/tdp/change-ownership-app-teams-global-admin.png" alt-text="Screenshot shows an example of a tenant admin taking ownership of an app in Teams Developer Portal."::: ## Changelog for Developer Portal |
| platform | Cards Format | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/task-modules-and-cards/cards/cards-format.md | The following code shows an example of Adaptive Card with typeahead support: ### Stage view for images in Adaptive Cards -In an Adaptive Card, you can use the `msteams` property to add the ability to display images in stage view selectively. When users hover over the images, they can see an expand icon, for which the `allowExpand` attribute is set to `true`. For information on how to use the property, see the following example: +In an Adaptive Card, you can use the `msteams` property to add the ability to display images in stage view selectively. When users hover over the images, they can see an expand icon, for which the `allowExpand` attribute is set to `true`. The following is an example of the `msteams` property: ``` json { In the stage view, users can zoom in and zoom out of the image. You can select t > > * Zoom in and zoom out capability applies only to the image elements that is image type in an Adaptive Card. > * For Teams mobile apps, stage view functionality for images in Adaptive Cards is available by default. Users can view Adaptive Card images in stage view by simply tapping on the image, irrespective of whether the `allowExpand` attribute is present or not.+> * Stage view for images in Adaptive Cards doesn't support Base64 encoded images. # [Markdown format for connector cards for Microsoft 365 Groups](#tab/connector-md) |