-The meeting extensibility provide APIs to enhance meeting experience. You can perform the following with help of the listed APIs:

-|[**Share app content to stage**](#share-app-content-to-stage-api)| Share specific parts of the app to meeting stage from the app side panel in a meeting. | [MSTC SDK](/javascript/api/@microsoft/teams-js/microsoftteams.meeting?view=msteams-client-js-latest&preserve-view=true) |

-|[**Get app content stage sharing state**](#get-app-content-stage-sharing-state-api)| Fetch information about app's sharing state on the meeting stage. | [MSTC SDK](/javascript/api/@microsoft/teams-js/microsoftteams.meeting.iappcontentstagesharingstate?view=msteams-client-js-latest&preserve-view=true) |

-|[**Get app content stage sharing capabilities**](#get-app-content-stage-sharing-capabilities-api)| Fetch the app's capabilities for sharing to the meeting stage. | [MSTC SDK](/javascript/api/@microsoft/teams-js/microsoftteams.meeting.iappcontentstagesharingcapabilities?view=msteams-client-js-latest&preserve-view=true) |

-| **user.email** | Mail Id of the user. |

-| **details.id** | The meeting's Id, encoded as a BASE64 string. |

-**startDate**: Specifies the date to start applying the pattern. The value of startDate must correspond to the date value of the start property on the event resource. Note that the first occurrence of the meeting may not occur on this date if it does not fit the pattern.

-**endDate**: Specifies the date to stop applying the pattern. Note that the last occurrence of the meeting may not occur on this date if it does not fit the pattern.

-The `meetingSidePanel` enables you to customize experiences in a meeting that allow organizers and presenters to have different set of views and actions. In your app manifest, you must add `meetingSidePanel` to the context array. In the meeting and in all scenarios, the app is rendered in an in-meeting tab that is 320 pixels in width. For more information, see [FrameContext interface](/javascript/api/@microsoft/teams-js/microsoftteams.framecontext?view=msteams-client-js-latest&preserve-view=true).

-To use the `userContext` API to route requests, see [Teams SDK](../tabs/how-to/access-teams-context.md#user-context). For more information, see [Teams authentication flow for tabs](../tabs/how-to/authentication/auth-flow-tab.md). Authentication flow for tabs is similar to the authentication flow for websites. So tabs can use OAuth 2.0 directly. For more information, see [Microsoft identity platform and OAuth 2.0 authorization code flow](/azure/active-directory/develop/v2-oauth2-auth-code-flow).

- $ git clone https://github.com/microsoft/live-share-sdk.git

- $ cd live-share-sdk\samples\01.dice-roller

- $ npm install

- $ npm start

-For more information about working with the calendar, see, the [calendar](/javascript/api/@microsoft/teams-js/calendar?view=msteams-client-js-latest&preserve-view=true) namespace in the API reference documentation.

-### tab/Teams JS v1

-For effective integration, you must have a good understanding of [code snippets](#code-snippets) for calling the respective APIs, which allow you to use native media capabilities. It is important to familiarize yourself with the [API response errors](#error-handling) to handle the errors in your Teams app.

-The [selectMedia](/javascript/api/@microsoft/teams-js/microsoftteams.media.media?view=msteams-client-js-latest&preserve-view=true), [getMedia](/javascript/api/@microsoft/teams-js/microsoftteams.media.mediachunk?view=msteams-client-js-latest&preserve-view=true), and [viewImages](/javascript/api/@microsoft/teams-js/microsoftteams.media.imageuri?view=msteams-client-js-latest&preserve-view=true) APIs enable you to use native media capabilities as follows:

-> * The `selectMedia`, `getMedia`, and `viewImages` APIs can be invoked from multiple Teams surfaces, such as task modules, tabs, and personal apps. For more details, see [Entry points for Teams apps](../extensibility-points.md).</br>

-| [**selectMedia**](/javascript/api/@microsoft/teams-js/microsoftteams.media.media?view=msteams-client-js-latest&preserve-view=true) (**Camera)**| This API allows users to **capture or select media from the device camera** and return it to the web-app. The users can edit, crop, rotate, annotate, or draw over images before submission. In response to `selectMedia`, the web-app receives the media IDs of selected images and a thumbnail of the selected media. This API can be further configured through the [ImageProps](/javascript/api/@microsoft/teams-js/microsoftteams.media.imageprops?view=msteams-client-js-latest&preserve-view=true) configuration. |

-| [**selectMedia**](/javascript/api/@microsoft/teams-js/microsoftteams.media.media?view=msteams-client-js-latest&preserve-view=true) (**Microphone**)| Set the [mediaType](/javascript/api/@microsoft/teams-js/microsoftteams.media.mediatype?view=msteams-client-js-latest&preserve-view=true) to `4` in `selectMedia` API for accessing microphone capability. This API also allows users to record audio from the device microphone and return recorded clips to the web-app. The users can pause, re-record, and play recording preview before submission. In response to **selectMedia**, the web-app receives media IDs of the selected audio recording. <br/> Use `maxDuration`, if you require to configure a duration in minutes for recording the conversation. The current duration for recording is 10 minutes, after which the recording terminates. |

-| [**getMedia**](/javascript/api/@microsoft/teams-js/microsoftteams.media.mediachunk?view=msteams-client-js-latest&preserve-view=true)| This API retrieves the media captured by `selectMedia` API in chunks, irrespective of the media size. These chunks are assembled and sent back to the web app as a file or blob. Breaking media into smaller chunks facilitates large file transfer. |

-| [**viewImages**](/javascript/api/@microsoft/teams-js/microsoftteams.media.imageuri?view=msteams-client-js-latest&preserve-view=true)| This API enables the user to view images in full-screen mode as a scrollable list.|

-| **404** | FILE_NOT_FOUND | File specified is not found in the given location.|

-| **9000**| OLD_PLATFORM | Platform code is outdated and does not implement this API.|

- navigator.geolocation.getCurrentPosition (function (position) { /*... */ });

-microsoftTeams.people.selectPeople((error: microsoftTeams.SdkError, people: microsoftTeams.people.PeoplePickerResult[]) =>

- },{ setSelected: ["aad id"], openOrgWideSearchInChatOrChannel: true, singleSelect: false});

-> This topic reflects version 2.0.0 of the Microsoft Teams JavaScript client SDK. If you are using an earlier version, refer to the [Teams JS SDK overview](msteams-docs/msteams-platform/tabs/how-to/../../../../../tabs/how-to/using-teams-client-sdk.md) for guidance on the differences between v1 and v2.

-* Read the `entityId` or `subEntityId` that identifies what is in this tab.

-* Insert URL placeholder values.

-* Use the [Microsoft Teams JavaScript client SDK](/javascript/api/overview/msteams-client).

-Use placeholders in your configuration or content URLs. Microsoft Teams replaces the placeholders with the relevant values when determining the actual configuration or content URL. The available placeholders include all fields on the [context](/javascript/api/@microsoft/teams-js/microsoftteams.context?view=msteams-client-js-1.12.1&preserve-view=true) object. Common placeholders include the following:

-* {entityId}: The ID you supplied for the item in this tab when first [configuring the tab](~/tabs/how-to/create-tab-pages/configuration-page.md).

-* {subEntityId}: The ID you supplied when generating a [deep link](~/concepts/build-and-test/deep-links.md) for a specific item within this tab. This must be used to restore to a specific state within an entity; for example, scrolling to or activating a specific piece of content.

-* {loginHint}: A value suitable as a login hint for Azure AD. This is usually the login name of the current user in their home tenant.

-* {userPrincipalName}: The User Principal Name of the current user in the current tenant.

-* {userObjectId}: The Azure AD object ID of the current user in the current tenant.

-* {theme}: The current user interface (UI) theme such as `default`, `dark`, or `contrast`.

-* {groupId}: The ID of the Office 365 group in which the tab resides.

-* {tid}: The Azure AD tenant ID of the current user.

-* {locale}: The current locale of the user formatted as languageId-countryId(en-us).

-> The previous `{upn}` placeholder is now deprecated. For backward compatibility, it is currently a synonym for `{loginHint}`.

-For example, in your tab manifest you set the `configURL` attribute to `"https://www.contoso.com/config?name={loginHint}&tenant={tid}&group={groupId}&theme={theme}"`, the signed-in user has the following attributes:

-* They're a member of the Office 365 group with id **00209384-etc**.

-When they configure the tab, Teams calls the following URL:

-The following code provides an example of context variable:

-```json

-{

- "teamId": "The Microsoft Teams ID in the format 19:[id]@thread.skype",

- "teamName": "The name of the current team",

- "channelId": "The channel ID in the format 19:[id]@thread.skype",

- "channelName": "The name of the current channel",

- "chatId": "The chat ID in the format 19:[id]@thread.skype",

- "locale": "The current locale of the user formatted as languageId-countryId (for example, en-us)",

- "entityId": "The developer-defined unique ID for the entity this content points to",

- "subEntityId": "The developer-defined unique ID for the sub-entity this content points to",

- "loginHint": "A value suitable as a login hint for Azure AD. This is usually the login name of the current user, in their home tenant",

- "userPrincipalName": "The principal name of the current user, in the current tenant",

- "userObjectId": "The Azure AD object id of the current user, in the current tenant",

- "tid": "The Azure AD tenant ID of the current user",

- "groupId": "Guid identifying the current Office 365 Group ID",

- "theme": "The current UI theme: default | dark | contrast",

- "isFullScreen": "Indicates if the tab is in full-screen",

- "teamType": "The type of team",

- "teamSiteUrl": "The root SharePoint site associated with the team",

- "teamSiteDomain": "The domain of the root SharePoint site associated with the team",

- "teamSitePath": "The relative path to the SharePoint site associated with the team",

- "channelRelativeUrl": "The relative path to the SharePoint folder associated with the channel",

- "sessionId": "The unique ID for the current Teams session for use in correlating telemetry data",

- "userTeamRole": "The user's role in the team",

- "isTeamArchived": "Indicates if team is archived",

- "hostClientType": "The type of host client. Possible values are android, ios, web, desktop, surfaceHub, teamsRoomsAndroid, teamsPhones, teamsDisplays rigel (deprecated, use teamsRoomsWindows instead)",

- "frameContext": "The context where tab URL is loaded (for example, content, task, setting, remove, sidePanel)",

- "sharepoint": "The SharePoint context is available only when hosted in SharePoint",

- "tenantSKU": "The license type for the current user tenant. Possible values are enterprise, free, edu, unknown",

- "userLicenseType": "The license type for the current user. Possible values are E1, E3, and E5 enterprise plans",

- "parentMessageId": "The parent message ID from which this task module is launched",

- "ringId": "The current ring ID",

- "appSessionId": "The unique ID for the current session used for correlating telemetry data",

- "isCallingAllowed": "Indicates if calling is allowed for the current logged in user",

- "isPSTNCallingAllowed": "Indicates if PSTN calling is allowed for the current logged in user",

- "meetingId": "The meeting ID used by tab when running in meeting context",

- "defaultOneNoteSectionId": "The OneNote section ID that is linked to the channel",

- "isMultiWindow": "The indication whether the tab is in a pop out window"

-You can also retrieve the information listed above using the [Microsoft Teams JavaScript client SDK](/javascript/api/overview/msteams-client) by calling the `app.getContext()` function. For additional information, see the properties of the [Context interface](/javascript/api/@microsoft/teams-js/app.context?view=msteams-client-js-latest&preserve-view=true).

-* `groupId`: Undefined for private channels

-* `teamId`: Set to the threadId of the private channel

-* `teamName`: Set to the name of the private channel

-* `teamSiteUrl`: Set to the URL of a distinct, unique SharePoint site for the private channel

-* `teamSitePath`: Set to the path of a distinct, unique SharePoint site for the private channel

-* `teamSiteDomain`: Set to the domain of a distinct, unique SharePoint site domain for the private channel

-If your page makes use of any of these values, the value of `channelType` field must be `Private` to determine if your page is loaded in a private channel and can respond appropriately.

-* `groupId`: Undefined for shared channels.

-* `teamId`: Set to the `threadId` of the team, the channel is shared for the current user. If the user has access to multiple teams, the `teamId` is set to the team that hosts (creates) the shared channel.

-* `teamName`: Set to the name of the team, the channel is shared for the current user. If the user has access to multiple teams, the `teamName` is set to the team that hosts (creates) the shared channel.

-* `teamSiteUrl`: Set to the URL of a distinct, unique SharePoint site for the shared channel.

-* `teamSitePath`: Set to the path of a distinct, unique SharePoint site for the shared channel.

-* `teamSiteDomain`: Set to the domain of a distinct, unique SharePoint site domain for the shared channel.

-In addition to these field changes, there're two new fields available for shared channels:

-* `hostTeamGroupId`: Set to the `groupId` associated with the hosting team, or the team that created the shared channel. The property can make Microsoft Graph API calls retrieve membership of the shared channel.

-* `hostTeamTenantId`: Set to the `tenantId` associated with the hosting team, or the team that created the shared channel. The property can be cross referenced with the current user's tenant ID found in the `tid` field of `getContext` to determine if the user is internal or external to the hosting team's tenant.

-If your page makes use of any of these values, the value of `channelType` field must be `Shared` to determine if your page is loaded in a shared channel and can respond appropriately.

-You can register your app to be informed if the theme changes by calling `app.registerOnThemeChangeHandler(function(theme) { /* ... */ })`.

-Most of these values can also be retrieved from the `getContext` API.

- {

- services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_2);

- }

- {

- }

- <script src="https://statics.teams.cdn.office.net/sdk/v1.6.0/js/MicrosoftTeams.min.js"></script>

-1. Insert a call to `microsoftTeams.initialize();` in the `script` tag.

- Within **Tab.cshtml** the application presents the user with two option buttons for displaying the tab with either a red or gray icon. Choosing the **Select Gray** or **Select Red** button triggers `saveGray()` or `saveRed()`, respectively, sets `settings.setValidityState(true)`, and enables the **Save** button on the configuration page. This code lets Teams know that you have completed the configuration requirements and the installation can proceed. The parameters of `settings.setSettings` are set. Finally, `saveEvent.notifySuccess()` is called to indicate that the content URL has been successfully resolved.

- microsoftTeams.settings.registerOnSaveHandler(function (saveEvent) {

- microsoftTeams.settings.setSettings({

- suggestedDisplayName: "MyNewTab"

- microsoftTeams.settings.registerOnSaveHandler(function (saveEvent) {

- microsoftTeams.settings.setSettings({

- suggestedDisplayName: "MyNewTab"

- });

- {

- services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_2);

- }

- {

- }

- <script src="https://statics.teams.cdn.office.net/sdk/v1.6.0/js/MicrosoftTeams.min.js"></script>

-1. Insert a call to `microsoftTeams.initialize();` in the `script` tag.

- Within **Tab.cshtml** the application presents the user with two option buttons for displaying the tab with either a red or gray icon. Choosing the **Select Gray** or **Select Red** button triggers `saveGray()` or `saveRed()`, respectively, sets `settings.setValidityState(true)`, and enables the **Save** button on the configuration page. This code lets Teams know that you have completed the configuration requirements and the installation can proceed. The parameters of `settings.setSettings` are set. Finally, `saveEvent.notifySuccess()` is called to indicate that the content URL has been successfully resolved.

- microsoftTeams.settings.registerOnSaveHandler(function (saveEvent) {

- microsoftTeams.settings.setSettings({

- suggestedDisplayName: "MyNewTab"

- microsoftTeams.settings.registerOnSaveHandler(function (saveEvent) {

- microsoftTeams.settings.setSettings({

- suggestedDisplayName: "MyNewTab"

- <script src="https://statics.teams.cdn.office.net/sdk/v2.0.0/js/MicrosoftTeams.min.js"></script>

- <script src="https://statics.teams.cdn.office.net/sdk/v2.0.0/js/MicrosoftTeams.min.js"></script>

- <script src='https://statics.teams.cdn.office.net/sdk/v2.0.0/js/MicrosoftTeams.min.js'></script>

-</head>

- <script>

- app.initialize();

- app.initialize();

-<script>

-Your tab's overall objective is to provide access to the meaningful and engaging content that has a practical value and an evident purpose.

- <script src= 'https://statics.teams.cdn.office.net/sdk/v2.0.0/js/MicrosoftTeams.min.js'></script>

-</head>

- <script>

- app.initialize();

-The optional removal page is an HTML page that you host and is displayed when the tab is removed. The removal page URL is designated by the `setConfig()` method (formerly `setSettings()`) within your configuration page. As with all pages in your app, the removal page must comply with [Teams tab prerequisites](../../../tabs/how-to/tab-requirements.md).

-Authentication is required before allowing a user to delete the tab content. Context information can be used to help construct authentication requests and authorization page URLs. See [Microsoft Teams authentication flow for tabs](~/tabs/how-to/authentication/auth-flow-tab.md). Make sure that all domains used in your tab pages are listed in the `manifest.json` `validDomains` array.

- <script>

- app.initialize();

-|Stage View is useful when you have rich content to display to the users, such as a page, a dashboard, a file, and so on. It provides rich features that helps to render your content in the full-screen canvas.|[Task module](../task-modules-and-cards/task-modules/task-modules-tabs.md) is especially useful to display messages that require user attention, or collect information required to move to the next step.|

-To invoke the Stage View through deep link from your tab, you must wrap the deep link URL in the `microsoftTeams.executeDeeplink(url)` API. The deep link can also be passed through an `OpenURL` action in the card.

-Following is the deeplink syntax:

-<https://teams.microsoft.com/l/stage/{appId}/0?context>={"contentUrl":"contentUrl","websiteUrl":"websiteUrl","name":"Contoso"}

-<https://teams.microsoft.com/l/stage/be411542-2bd5-46fb-8deb-a3d5f85156f6/0?context>={"contentUrl":"https://teams-alb.wakelet.com/teams/collection/e4173826-5dae-4de0-b77d-bfabafd6f191","websiteUrl":"https://teams-alb.wakelet.com/teams/collection/e4173826-5dae-4de0-b77d-bfabafd6f191?standalone=true","title":"Quotes: Miscellaneous","threadId":"19:9UryYW9rjwnq-vwmBcexGjN1zQSNX0Y4oEAgtUC7WI81@thread.tacv2"}

-<https://teams.microsoft.com/l/stage/be411542-2bd5-46fb-8deb-a3d5f85156f6/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2Fteams-alb.wakelet.com%2Fteams%2Fcollection%2Fe4173826-5dae-4de0-b77d-bfabafd6f191%22%2C%22websiteUrl%22%3A%22https%3A%2F%2Fteams-alb.wakelet.com%2Fteams%2Fcollection%2Fe4173826-5dae-4de0-b77d-bfabafd6f191%3Fstandalone%3Dtrue%22%2C%22title%22%3A%22Quotes%3A%20Miscellaneous%22%2C%22threadId%22%3A%2219:9UryYW9rjwnq-vwmBcexGjN1zQSNX0Y4oEAgtUC7WI81@thread.tacv2%22%7D>

-<https://teams.microsoft.com/l/stage/43f56af0-8615-49e6-9635-7bea3b5802c2/0?context>={"contentUrl":"https://teams-alb.wakelet.com/teams/collection/e4173826-5dae-4de0-b77d-bfabafd6f191","websiteUrl":"https://teams-alb.wakelet.com/teams/collection/e4173826-5dae-4de0-b77d-bfabafd6f191?standalone=true","title":"Quotes: Miscellaneous"}

-<https://teams.microsoft.com/l/stage/43f56af0-8615-49e6-9635-7bea3b5802c2/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2Fteams-alb.wakelet.com%2Fteams%2Fcollection%2Fe4173826-5dae-4de0-b77d-bfabafd6f191%22%2C%22websiteUrl%22%3A%22https%3A%2F%2Fteams-alb.wakelet.com%2Fteams%2Fcollection%2Fe4173826-5dae-4de0-b77d-bfabafd6f191%3Fstandalone%3Dtrue%22%2C%22title%22%3A%22Quotes%3A%20Miscellaneous%22%7D>

-> All deeplinks must be encoded before pasting the URL. We don't support unencoded URLs.

-> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4OIzv]

-1. Initialize the SDK by calling `microsoftTeams.initialize()`.

-1. Call `microsoftTeams.settings.setValidityState(true)` to enable **Save**.

- > You must call `microsoftTeams.settings.setValidityState(true)` as a response to user selection or field update.

-1. Register `microsoftTeams.settings.registerOnSaveHandler()` event handler, which is called when the user selects **Save**.

-1. Call `microsoftTeams.settings.setSettings()` to save the connector settings. The saved settings are also shown in the configuration dialog if the user tries to update an existing configuration for your connector.

-1. Call `microsoftTeams.settings.getSettings()` to fetch webhook properties, including the URL.

- > You must call `microsoftTeams.settings.getSettings()` when your page is first loaded in case of reconfiguration.

-1. Register `microsoftTeams.settings.registerOnRemoveHandler()` event handler, which is called when the user removes connector.

-<script src="https://statics.teams.microsoft.com/sdk/v1.5.2/js/MicrosoftTeams.min.js" crossorigin="anonymous"></script>

-<script type="text/javascript">

- microsoftTeams.settings.setValidityState(true);

- microsoftTeams.initialize();

- microsoftTeams.settings.registerOnSaveHandler(function (saveEvent) {

- microsoftTeams.settings.setSettings({

- entityId: eventType,

- configName: eventType

- microsoftTeams.settings.getSettings(function (settings) {

- // We get the Webhook URL in settings.webhookUrl which needs to be saved.

- microsoftTeams.settings.registerOnRemoveHandler(function (removeEvent) {

-> Due to cross client compatibility reasons, your code must call `microsoftTeams.authentication.registerAuthenticationHandlers()` with the URL and success or failure callback methods before calling `authenticate()`.

-#### `GetSettings` response properties

->The parameters returned by the `getSettings` call are different when you invoke this method from a tab and differ from those documented in [js settings](/javascript/api/@microsoft/teams-js/microsoftteams.settings.settings).

-The following table provides the parameters and the details of `GetSetting` response properties:

-| `entityId` | The entity ID, as set by your code when calling `setSettings()`. |

-| `configName` | The configuration name, as set by your code when calling `setSettings()`. |

-| `contentUrl` | The URL of the configuration page, as set by your code when calling `setSettings()`. |

-Your code must handle users who return to edit an existing connector configuration. To do this, call `microsoftTeams.settings.setSettings()` during the initial configuration with the following parameters:

-This call is made as part of your save event handler. Then, when the `contentUrl` is loaded, your code must call `getSettings()` to pre populate any settings or forms in your configuration user interface.

-You can execute an event handler when the user removes an existing connector configuration. You register this handler by calling `microsoftTeams.settings.registerOnRemoveHandler()`. This handler is used to perform cleanup operations, such as removing entries from a database.

-Download the auto generated `Teams app manifest` from the portal. Perform the following steps, before testing or publishing the app:

-The following manifest.json file contains the elements needed to test and submit the app:

-1. Add a [configuration page](~/webhooks-and-connectors/how-to/connectors-creating.md?#integrate-the-configuration-experience) and publish your Incoming Webhook in a Office 365 Connector.

-## Microsoft Build 2022 :::image type="icon" source="assets/images/bullhorn.png"

-| Date | Feature | Find it here |

-| | | |

-| 05/24/2022| [*Developer preview*] <br> Enhanced collaboration with Live Share SDK | Build apps for Teams meetings > Enhanced collaboration with Live Share > [Overview](apps-in-teams-meetings/teams-live-share-overview.md) |

-|05/24/2022| Submit your Outlook- and Office-enabled apps to the Teams store | Extend your app across Microsoft 365 > [Overview](m365-apps/overview.md) |

-|05/24/2022| App guidance and what's new in TeamsJS version 2.0.0| Tools and SDKs > [Teams JavaScript client SDK](tabs/how-to/using-teams-client-sdk.md) |

-| 05/24/2022 | Teams Toolkit version 4.0.0 for Visual Studio Code is now GA | Tools and SDKs > Teams Toolkit for Visual Studio Code > <br> ΓÇó [Teams Toolkit Overview](toolkit/teams-toolkit-fundamentals.md) <br> ΓÇó [Build command bot with JavaScript](toolkit/add-capability.md) <br> ΓÇó [Build notification bot with JavaScript](toolkit/add-capability.md) <br> ΓÇó [Preview and customize Teams app manifest](toolkit/TeamsFx-preview-and-customize-app-manifest.md) <br> ΓÇó [Connect to existing APIs](toolkit/add-API-connection.md) <br> ΓÇó [Add capabilities to your Teams apps](toolkit/add-capability.md) <br> ΓÇó [Add single sign-on experience](toolkit/add-single-sign-on.md) <br> ΓÇó [Add cloud resources to Teams app](toolkit/add-resource.md) |

-| 05/24/2022 | Introduced app manifest version 1.13 | App manifest > [Manifest schema for Microsoft Teams](resources/schem) |

-| 05/24/2022 | Bots and Message extensions in GCC and GCCH | ΓÇó Plan your app > [Overview](concepts/app-fundamentals-overview.md#government-community-cloud) </br> ΓÇó Build bots > [Overview](bots/what-are-bots.md) </br> ΓÇó Build message extensions > [Overview](messaging-extensions/what-are-messaging-extensions.md) |