| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| platform | High Quality Message Extension | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/messaging-extensions/high-quality-message-extension.md | The requirements for building message extension plugins for Copilot for Microsof > > * [Define app, command, and parameter descriptions](#define-descriptions) > * [Enhance message extension to retrieve information through compound utterances](#compound-utterances)-> * [Define sample prompts](#sample-prompts) > * [Create rich Adaptive Card responses](#adaptive-card-response) ## Define descriptions For Copilot for Microsoft 365, a search-based message extension must support mor The search parameters must have good descriptions with acceptable parameters, enums, acronyms, and output format. For more information and examples, see [Parameter description](#parameter-description). -## Sample prompts --The [`samplePrompts`](../resources/schem#composeextensionscommands) property guides users on how to use the various plugins within Copilot. Copilot uses the sample prompts to display the prompts for the user. The prompts must be adaptable to different locales and clear across different commands. Sample prompts are available in the following areas within Copilot for Microsoft 365: --* First Run Experience (FRE): When a user first installs or enables a plugin. -* Prompt library or Copilot Lab: When a user seeks help with prompts. -* Plugin suggestions: To guide users towards better utterances. ---> [!NOTE] -> -> * If the app manifest doesn't specify the `samplePrompts` property, the prompts aren't displayed. -> * The `samplePrompts` property is mandatory for app validation during the app submission process. -> * If you define multiple commands for your app, a maximum of three prompts (one from each of the top three commands) are displayed to the user. The prompts rotate to provide the user with a diverse set of prompts across different commands. --We recommend you to follow these guidelines to increase the chances of your app to pass the Microsoft Teams Store submission process: --* A plugin must have at least three prompts and maximum of five prompts for each command. -* Each prompt must not exceed 128 characters. -* Two commands within the same plugin must not have identical prompts. -* Sample prompts must be generic in nature and not include custom references. For example, project names and task name. -* All sample prompts must be functional and return responses. -* Prompt must be relevant to the commands. --The following code is an example of the `samplePrompts` property in app manifest: --```json -"composeExtensions": [ - { - "canUpdateConfiguration": true, - "botId": "bxxxxxx5-xxxx-xxxx-xxxx-4xxxxxx16599", - "commands": [ - { - "id": "orders", - "title": "Orders", - "context": [ - "Commandbox", - "Compose" - ], - "description": "Search for orders", - "semanticDescription": "Search for orders", - "samplePrompts": [ - { - "text": "Search for all orders" - }, - { - "text": "Search for orders related to Contoso" - }, - { - "text": "Search for all pending orders" - }, - { - "text": "Search for all completed ordered for Fabrikam" - } - ] - } - ] - } -] -``` - ## Adaptive Card response Message extensions respond to a user input with an Adaptive Card. An Adaptive Card for a message extension plugin must function effectively, appear rich, and meet the following requirements: |
| platform | Whats New | https://github.com/MicrosoftDocs/msteams-docs/commits/main/msteams-platform/whats-new.md | Teams platform features that are available to all app developers. |12/04/2024|Create Dashboardcards that can be pinned to a dashboard such as Microsoft Viva Connections to provide a summarized view of app information|App manifest > [dashboardCards](resources/schem#dashboardcards)| |12/04/2024|Share code snippets as richly formatted Adaptive Cards in Teams chats, channels, and meetings with the CodeBlock element.|Build cards and dialogs > [CodeBlock in Adaptive Cards](task-modules-and-cards/cards/cards-format.md#codeblock-in-adaptive-cards)| |12/04/2024|Introduced bot configuration experience that helps you to enable the bot settings for users to configure their bot during installation and reconfigure the bot.|Build bots > [Bot configuration experience](bots/how-to/bot-configuration-experience.md)|-|12/04/2024|Use sample prompts to guide users on how to use the various plugins within Copilot.|Build message extensions > Build message extensions using Bot Framework > Search commands > [Sample prompts](messaging-extensions/high-quality-message-extension.md#sample-prompts)| |10/04/2024|Define and deploy Outlook Add-ins in version 1.17 and later of the app manifest schema.|Extend your app across Microsoft 365 > [Outlook Add-ins](m365-apps/overview.md#outlook-add-ins)| |04/04/2024|Added support for python in Teams AI library.|Build bots > Teams AI library > [Teams AI library](bots/how-to/Teams%20conversational%20AI/teams-conversation-ai-overview.md)| |04/04/2024|Stageview API with the openmode property allows you to open your app content in different Stageview experience.|Build tabs > [Open content in Stageview](tabs/open-content-in-stageview.md)| |