+Anonymous users don't have an Azure Active Directory (Azure AD) identity and aren't federated with a tenant. The anonymous participants are like external users but their identity isn't shown in the meeting. An anonymous user can be a presenter or an attendee but can't be an organizer. You can build bots, messaging extensions, and cards and task modules in your app to engage with anonymous meeting participants.

+For anonymous users to interact with the apps in Teams meetings, ensure the following:

+1. Update your [app manifest](#app-manifest-update-for-anonymous-users).

+2. Enable the [anonymous user app interaction](#admin-setting-for-anonymous-user-app-interaction) in Teams admin center.

+## App manifest update for anonymous users

+To allow anonymous users to interact with the tab app, update the `supportsAnonymousGuestUsers` property to `true` in your app manifest schema v1.16 or later. Following is an example of the manifest:

+```json

+ "meetingExtensionDefinition": {

+ "supportsAnonymousGuestUsers": true

+ }

+```

+For more information, see [app manifest schema.](~/resources/schem#meetingextensiondefinition)

+## Anonymous user authentication flow

+Anonymous users can't be authenticated through Azure AD authentication or `getAuthToken` from the client SDK as they aren't Azure AD accounts. `getAuthToken` fails for anonymous users by returning the error `useGetAuthToken: Failed with error - User is not authenticated`. If you need to authenticate anonymous users, your app must identify anonymous users and provide an alternative authentication experience in the meetings. You can determine if a user is anonymous by validating [user's context](#in-meeting-getcontext-from-teams-client-library).

+Teams admins can use the Teams admin center to enable or disable anonymous user app interaction for the entire tenant. If your app needs to be accessed by anonymous users, ensure that the tenant admins enable the anonymous user app interaction. This setting is enabled by default. For more information, see [allow anonymous users to interact with apps in meetings](/microsoftteams/meeting-settings-in-teams).

+To test your apps experience for anonymous users, select the URL in the meeting invite and join the meeting from a private browser window.

+Apps receive the following information for an anonymous user when they call the `getContext` API from the [shared app stage](~/apps-in-teams-meetings/build-apps-for-teams-meeting-stage.md). You can recognize anonymous users by checking for a `userLicenseType` value of `Anonymous`.

+> [!NOTE]

+> The Live Share SDK isn't supported for anonymous users.

+# [JavaScript](#tab/javascript)

+```javascript

+microsoftTeams.app.getContext().then((context) => {

+ if (context.user.licenseType === "Anonymous")

+ {

+ // Add your custom logic here

+ }

+});

+```

+# [JSON](#tab/json)

+```json

+{

+ "app": {

+ "locale": "en-us",

+ "sessionId": "e0024c2a-067f-4f43-8423-6acac718b7a0",

+ "theme": "dark",

+ "parentMessageId": "",

+ "userClickTime": 1675776700117,

+ "host": {

+ "name": "Teams",

+ "clientType": "web",

+ "sessionId": "",

+ "ringId": "general"

+ }

+ },

+ "page": {

+ "frameContext": "meetingStage",

+ "subPageId": "",

+ "isMultiWindow": false,

+ "sourceOrigin": ""

+ },

+ "user": {

+ "id": "",

+ "licenseType": "Anonymous",

+ "loginHint": "",

+ "userPrincipalName": ""

+ },

+ "chat": {

+ "id": "19:meeting_ZmMyNWZjMzEtMWU0Mi00NDNmLWJhMmYtNjM4OTY0YmM0NWM2@thread.v2"

+ },

+ "meeting": {

+ "id": "MCMxOTptZWV0aW5nX1ptTXlOV1pqTXpFdE1XVTBNaTAwTkRObUxXSmhNbVl0TmpNNE9UWTBZbU0wTldNMkB0aHJlYWQudjIjMA=="

+ }

+}

+| `userObjectId` | Empty string for anonymous user. |

+| `userLicenseType` | `Anonymous` represents anonymous user. |

+| `loginHint` | Empty string for anonymous user. |

+| `userPrincipalName` | Empty string for anonymous user. |

+For more information on `getContext`, see [get context by using the Microsoft Teams JavaScript library.](~/tabs/how-to/access-teams-context.md#get-context-by-using-the-microsoft-teams-javascript-library)

+With a few differences, the activities sent to your bot and the responses that it receives from bot APIs are consistent between anonymous and non-anonymous meeting participants.

+}

+| `userRole` | `Anonymous` represents anonymous user. |

+`MembersAdded`

+protected override async Task OnTeamsMembersAddedAsync(IList<TeamsChannelAccount> membersAdded, TeamInfo teamInfo, ITurnContext<IConversationUpdateActivity> turnContext, CancellationToken cancellationToken)

+ {

+ foreach (var teamMember in membersAdded)

+ {

+ // If UserRole == "anonymous", it indicates an anonymous user

+ if (teamMember.UserRole == "anonymous" )

+ {

+ // Add your custom logic here

+ }

+ else

+ {

+ // Add your custom logic here

+ }

+ }

+ }

+`MembersRemoved`

+```csharp

+protected override async Task OnTeamsMembersRemovedAsync(IList<TeamsChannelAccount> membersRemoved, TeamInfo teamInfo, ITurnContext<IConversationUpdateActivity> turnContext, CancellationToken cancellationToken)

+ foreach (var member in membersRemoved)

+ {

+ // If AadObjectId is null, it indicates an anonymous user

+ if (member.AadObjectId == null)

+ {

+ // Add your custom logic here

+ }

+ else

+ {

+ // Add your custom logic here

+ }

+ }

+```

+> When an anonymous user joins or leaves a meeting, the `from` object in the payload always has the ID of the meeting organizer, even if the action was taken by someone else.

+Bots aren't allowed to initiate a one-on-one conversation with an anonymous user. If a bot calls the [Create Conversation API](/dotnet/api/microsoft.bot.builder.botframeworkadapter.createconversationasync) with the user ID of an anonymous user, it will receive a `400` Bad Request status code and the following error response:

+var conversationParameters = new ConversationParameters

+ {

+ IsGroup = false,

+ Bot = turnContext.Activity.Recipient,

+ Members = new ChannelAccount[] { teamMember },

+ TenantId = turnContext.Activity.Conversation.TenantId,

+ };

+

+ await ((CloudAdapter)turnContext.Adapter).CreateConversationAsync(

+ conversationParameters,

+ async (t1, c1) =>

+ {

+ conversationReference = t1.Activity.GetConversationReference();

+ await ((CloudAdapter)turnContext.Adapter).ContinueConversationAsync(

+ _appId,

+ conversationReference,

+ async (t2, c2) =>

+ {

+ await t2.SendActivityAsync(proactiveMessage, c2);

+ },

+ cancellationToken);

+ },

+cancellationToken);

+```

+```json

+### Adaptive Cards

+Anonymous users can view and interact with Adaptive Cards in the meeting chat. Adaptive Card actions behave the same way for anonymous and non-anonymous users. For more information, see [Card actions](/microsoftteams/platform/task-modules-and-cards/cards/cards-actions?tabs=json).

+* Anonymous users will see a generic app icon on bot messages and cards, instead of the app's actual icon.

+ :::image type="content" source="../assets/images/apps-in-meetings/app-icon.png" alt-text="Screenshot shows how the app icon displays for anonymous user.":::

+## Code sample

+|Sample name | Description | .NET | Manifest |

+|-|--|--|--|

+| Anonymous user support | Sample app to show anonymous user support in meeting apps. | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-anonymous-users/csharp) | [View](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/app-anonymous-users/csharp/demo-manifest) |

+|**callback**| String | Yes | Callback contains two parameters, error and result. The *error* can contain either an error of type *SdkError* or null when share is successful. The *result* can contain either a true value if there's a successful share or null when the share fails. |

+|**callback**| String | Yes | Callback contains two parameters, error and result. The *error* can contain either an error of type *SdkError* in case of an error or null when share is successful. The *result* can contain either an `IAppContentStageSharingState` object when share is successful or null in case of an error.|

+|**callback**| String | Yes | Callback contains two parameters, error and result. The *error* can contain either an error of type *SdkError* or null when share is successful. The result can contain either an `IAppContentStageSharingCapabilities` object, when share is successful or null in case of an error.|

+* Add documents to be reviewed during a meeting.

+* Share documents to be reviewed to main stage.

+* Sign documents using the signerΓÇÖs identity.

+| In-tenant | Presenter or organizer can start, view, and interact with the app in the meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with the app on meeting stage. <br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with the app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with the app on meeting stage.<br><br> Attendee can only view and interact. |

+| Guest | Presenter or organizer can start, view and interact with the app in the meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with the app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with the app on meeting stage.<br><br> Attendee can only view and interact. | Presenter or organizer can start, view, and interact with the app on meeting stage.<br><br> Attendee can only view and interact. |

+| Federated or External | Presenter can start, view, and interact with the app in the meeting stage.<br><br> Attendee can only view and interact. | Not available | Not available | Presenter can start, view, and interact with app on meeting stage.<br><br> Attendee can only view and interact. |

+| Anonymous |Presenter can start, view, and interact with the app on meeting stage.<br><br> Attendee can only view and interact. | Not available | Not available | Not available |

+| Federated, for more information, see [non-standard users](/microsoftteams/non-standard-users). |Can view messages, interact with the content, and invoke the bot. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. |

+| Anonymous | Can view and interact with the messages sent by the bot. Can't invoke the bot. | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from Adaptive Card are allowed. |

+Before creating a meeting tab, it's important to learn about the surfaces that are available to target the meeting chat view, meeting details view, meeting side panel view, and meeting stage view.

+ :::image type="content" source="~/assets/images/apps-in-meetings/pre-meeting-002.png" alt-text="This screenshot shows the pre-meeting app experience in Teams meeting.":::

+ :::image type="content" source="~/assets/images/apps-in-meetings/premeetingtab.png" alt-text="The screenshot shows desktop Teams tabs in the meeting details view in the Teams meeting.":::

+ :::image type="content" source="../assets/images/mobile-tab.png" alt-text="Screenshot shows mobile Teams tabs in the meeting details view in the Teams meeting.":::

+ :::image type="content" source="../assets/images/apps-in-meetings/add-app.png" alt-text="Screenshot shows how to add an app in Teams meeting window.":::

+ :::image type="content" source="../assets/images/side-panel-view.png" alt-text="Screenshot shows side panel view with the list of apps.":::

+Update your [app manifest](/microsoftteams/platform/resources/schema/manifest-schema) with relevant context property to configure the different tab views. The meetings app capabilities are declared in your app manifest using the scopes and context arrays under the `configurableTabs` section.

+| **meetingChatTab** | A tab in the header of a group chat between a set of users for a scheduled meeting. You can specify either `meetingChatTab` or `meetingDetailsTab` to ensure the apps work in mobile. |

+| **meetingDetailsTab** | A tab in the header of the meeting details view of the calendar. You can specify either `meetingChatTab` or `meetingDetailsTab` to ensure the apps work in mobile. |

+Apps in meetings can use the following contexts: `meetingChatTab`, `meetingDetailsTab`, `meetingSidePanel`, and `meetingStage`. After a meeting participant installs an app and configures the tab in meeting, all the targeted other contexts of the app for the given meeting starts to render the tab.

+TeamsJS is a rich library used to create Tabs using JavaScript. Use the latest TeamsJS (v2.0 or later) to work in Teams, Microsoft 365 app, and Outlook. For more information, see [Teams JavaScript client library](/microsoftteams/platform/tabs/how-to/using-teams-client-library).

+Microsoft Teams JavaScript library exposes the `frameContext` in which your meeting tab URL is loaded in the `getContext` API. The possible values of `frameContext` are content, task, setting, remove, sidePanel, and meetingStage. This allows you to build customized experiences based on where the app renders. For example, showing a specific collaboration focused UI when in the `meetingStage` and a different meeting preparation UI in the chat tab (`content`). For more information, see [getContext API](/microsoftteams/platform/tabs/how-to/access-teams-context?tabs=teamsjs-v2).

+| Guest | Can interact only | Can interact only | Can interact only | Can interact only |

+| Anonymous | Can interact only | Not available | Not available | Not available |

+| Anonymous | Available | Not available | Not available | Not available |

+description: Learn how apps works in Microsoft Teams meetings based on participant and user role and app extensibility.

+Meetings enable collaboration, partnership, informed communication, and shared feedback. The meeting space can deliver a user experience for each stage of the meeting lifecycle.

+* [**One-on-one calls**](https://support.microsoft.com/office/start-a-call-from-a-chat-in-teams-f5138c9d-df4c-43d8-9cf6-53400c1a7798): Calls initiated in a one-on-one chat.

+* [**Group calls**](https://support.microsoft.com/office/start-a-call-from-a-chat-in-teams-f5138c9d-df4c-43d8-9cf6-53400c1a7798): Calls initiated in a group chat.

+Learn more about [Teams meetings, expiration, and policies](/microsoftteams/meeting-expiration) and [meetings, webinars, and live events](/microsoftteams/quick-start-meetings-live-events).

+Teams supports user types, such as in-tenant, guest, federated or external, and anonymous users in a Teams meeting. Each user type can have one of the [user roles in Teams meeting](#user-roles-in-teams-meeting).

+> When a third person is added to a one-on-one call, the call is elevated to a group call , which starts a new session. Apps added to the one-on-one call aren't available in the group call. However, they can be added again.

+* **In-tenant**: In-tenant users belong to the organization and have credentials in Azure Active Directory (Azure AD) for the tenant. They're full-time, onsite, or remote employees and can be an organizer, presenter, or attendee.

+ > Teams users can add apps when they host meetings or chats with other organizations. When an external user shares an app to the meeting, all the users can access the app. The host organization's data policies and data sharing practices of the third-party apps shared by that user's organization will be in effect.

+* **Anonymous**: Anonymous users don't have an Azure AD identity and aren't federated with a tenant. The anonymous participants are like external users but their identity isn't shown in the meeting. Anonymous users can access apps in a meeting window. An anonymous user can be a presenter or an attendee but can't be an organizer.

+* **Presenter**: Presenters in a meeting have similar capabilities as the organizer, except for removing an organizer from the session and modifying meeting options for the session.

+> * A user who starts the group call from a chat is considered as an organizer.

+> * Currently, third-party apps are available in Government Community Cloud (GCC) but aren't available for GCC-High and Department of Defense (DOD) tenants.

+The Live Share SDK supports any [distributed data structure](https://fluidframework.com/docs/data-structures/overview/) included in Fluid Framework. These features serve as a set of primitives you can use to build robust collaborative scenarios, such as real-time updates of a task list or co-authoring text within an HTML `<textarea>`.

+Following are the different types of objects available:

+| [SharedString](https://fluidframework.com/docs/data-structures/string/) | Distributed-string sequence optimized for editing the text of documents or text areas. |

+The Live Share SDK includes a set of new distributed-data structures that extend Fluid's `SharedObject` class, providing new types of stateful and stateless objects. Unlike Fluid data structures, Live Share's `SharedObject` classes donΓÇÖt write changes to the Fluid container, enabling faster synchronization. Further, these classes were designed from the ground up for common meeting scenarios in Teams meetings. Common scenarios include synchronizing what content the presenter is viewing, displaying metadata for each user in the meeting, or displaying a countdown timer.

+| Live Object | Description |

+| -- | |

+| `LiveEvent` | Broadcast individual events with any custom data attributes in the payload. |

+| `LiveState` | Similar to SharedMap, a distributed key-value store that allows for restricted state changes based on role, for example, the presenter. |

+| `LiveTimer` | Synchronize a countdown timer for a given interval. |

+The `LivePresence` class makes tracking who is in the session easier than ever. When calling the `.initialize()` or `.updatePresence()` methods, you can assign custom metadata for that user, such as name, profile picture, or the identifier for content they are viewing. By listening to `presenceChanged` events, each client receives the latest `LivePresenceUser` object, collapsing all presence updates into a single record for each unique `userId`.

+The following are a few examples in which `LivePresence` can be used in your application:

+- Displaying profile pictures and names of each user connected to the session.

+- Synchronizing the coordinates in a 3D scene where each user's avatar is located.

+- Reporting each user's cursor position in a text document.

+- Posting each user's answer to an ice-breaker question during a group activity.

+`LiveEvent` is a great way to send simple events to other clients in a meeting that are only needed at the time of delivery. It's useful for scenarios like sending session notifications or implementing custom reactions.

+`LiveTimer` provides a simple countdown timer that is synchronized for everyone in a meeting. ItΓÇÖs useful for scenarios that have a time limit, such as a group meditation timer or a round timer for a game.

+### LiveState example

+The `LiveState` class enables synchronizing simple application state for everyone in a meeting. `LiveState` synchronizes two values: a `state` string and a corresponding `data` object, which allows you to build an ephemeral distributed-state machine.

+The following are a few examples in which `LiveState` can be used in your application:

+- Tracking the user identifier of the current presenter to build a **take control** feature.

+- Maintaining the content identifier that the current presenter is viewing. For example, an `taskId` on a task board.

+- Synchronizing the current step in a multi-round group activity. For example, the guessing phase during the Agile Poker game.

+> [!NOTE]

+> Unlike `SharedMap`, the `state` and `data` values in `LiveState` will be reset after all the users disconnect from a session.

+Example:

+# [JavaScript](#tab/javascript)

+```javascript

+import { LiveShareClient, LiveState } from "@microsoft/live-share";

+import { LiveShareHost } from "@microsoft/teams-js";

+// Join the Fluid container

+const host = LiveShareHost.create();

+const liveShare = new LiveShareClient(host);

+const schema = {

+ initialObjects: { appState: LiveState },

+};

+const { container } = await liveShare.joinContainer(schema);

+const { appState } = container.initialObjects;

+// Register listener for changes to state and corresponding custom data

+appState.on("stateChanged", (state, data, local) => {

+ if (state === "planet-viewer") {

+ const planetName = data?.planetName;

+ // Update app to display an image of the selected planet for the selected solar system

+ } else {

+ // No planet is yet selected

+ }

+});

+// Set roles who can change state and start listening for changes

+appState.initialize();

+function onSelectPlanet(planetName) {

+ appState.changeState("planet-viewer", {

+ planetName,

+ });

+}

+```

+# [TypeScript](#tab/typescript)

+```TypeScript

+import { LiveShareClient, LiveState } from "@microsoft/live-share";

+import { LiveShareHost } from "@microsoft/teams-js";

+enum PlanetName {

+ MERCURY = "Mercury",

+ VENUS = "Venus",

+ EARTH = "Earth",

+ MARS = "Mars",

+ JUPITER = "Jupiter",

+ SATURN = "Saturn",

+ URANUS = "Uranus",

+ NEPTUNE = "Neptune",

+}

+// Declare interface for type of custom data for user

+interface ICustomState {

+ planetName: PlanetName;

+}

+// Join the Fluid container

+const host = LiveShareHost.create();

+const liveShare = new LiveShareClient(host);

+const schema = {

+ initialObjects: {

+ appState: LiveState<ICustomState>,

+ },

+};

+const { container } = await liveShare.joinContainer(schema);

+const appState = container.initialObjects.appState as LiveState<ICustomState>;

+// Register listener for changes to state and corresponding custom data

+appState.on("stateChanged", (state: string, data: ICustomState | undefined, local: boolean) => {

+ if (state === "planet-viewer") {

+ const planetName = data?.planetName;

+ // Update app to display an image of the selected planet for the selected solar system

+ } else {

+ // No planet is yet selected

+ }

+});

+// Set roles who can change state and start listening for changes

+appState.initialize();

+function onSelectPlanet(planetName: PlanetName) {

+ appState.changeState("planet-viewer", {

+ planetName,

+ });

+}

+```

+Meetings in Teams include calls, all-hands meetings, and online classrooms. Meeting participants might span across organizations, have different privileges, or simply have different goals. Hence, itΓÇÖs important to respect the privileges of different user roles during meetings. Live objects are designed to support role verification, allowing you to define the roles that are allowed to send messages for each individual live object. For example, you could choose that only meeting presenters and organizers can control video playback, but still allow guests and attendees to request videos to watch next.

+In the following example where only presenters and organizers can take control, `LiveState` is used to synchronize which user is the active presenter.

+import {

+ LiveShareClient,

+ LiveState,

+ UserMeetingRole,

+} from "@microsoft/live-share";

+Scheduled meetings, one-on-one calls, group calls, meet now, and channel meetings are supported.

+You can embed the Share to Teams button on the web apps that allows users to share the content from the web apps to any chat, group chat, or channel in Teams, without switching the context.

+You can embed the Share to Teams button in the personal app or tab hosted inside Teams that allows users to share the content from the personal app or tab to any chat, group chat, or channel in Teams, without switching the context.

+[Integrate web apps](../../samples/integrate-web-apps-overview.md)

+# Update Apple App Store Connect Team ID

+The Microsoft Teams app manifest describes how your app integrates into the Microsoft Teams product. Your app manifest must conform to the schema hosted at [`https://developer.microsoft.com/json-schemas/teams/v1.16/MicrosoftTeams.schema.json`](https://developer.microsoft.com/json-schemas/teams/v1.16/MicrosoftTeams.schema.json). Previous versions 1.0, 1.1,...,1.15, and the current version is 1.16 are each supported (using "v1.x" in the URL).

+ "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",

+ "manifestVersion": "1.16",

+|`full`|100 characters|✔️|The full name of the app, used if the full app name exceeds 30 characters.|

+|`supportsAnonymousGuestUsers`|Boolean|||A value that indicates whether an app supports access for anonymous users. The default value is **false**.|

+With single sign-on (SSO) in Teams, app users have the advantage of using Teams to access tab apps. After logging in to Teams using Microsoft or Microsoft 365 account, app users can use your app without the need to sign in again. Your app is available to app users on any device with the access granted through Azure Active Directory (Azure AD).

+1. **SSO user experience**: Teams offers your app users a true SSO experience. The app users can use your app without signing in again.

+3. **Enable SSO for your tab app**: Implement the tasks involved to enable SSO in your tab app.

+The app users sign in to Teams using either personal Microsoft account or Microsoft 365 account. You can take advantage of this account and use SSO to authenticate and authorize the app users.

+- The app user needs to give consent to Teams for using the identity to access your tab app.

+- Teams gets the access token for the current app user from Azure AD. This interaction with Azure AD is invisible to the app user. It translates to get the app access without having to leave the Teams environment.

+ - Alternatively, the tenant administrator can grant consent on behalf of the app users. In this scenario, when the tenant administrator consents for the app users in the tenant, the app users don't need to be prompted for consent at all. It means that the app users don't see the consent dialogs and can access the app seamlessly.

+- The access token is pre-fetched by Teams to improve performance and load time of the app in the Teams environment.

+- The app users don't need to memorize or record several passwords to access and use apps in Teams environment.

+> App users can't give permission to some permission scopes, such as `Sites.ReadWrite.All`, which allows the app user to read and write to all SharePoint and OneDrive assets in the tenant. For such scopes, only the tenant administrator can grant consent on an app user's behalf.

+| 6 | Tab app (between client and server) | The tab app parses the access token using JavaScript to extract required information, such as the app user's email address. The token returned to the tab app is both an access token and an identity token. |

+>

+> - The `getAuthToken()` is valid only for consenting to a limited set of user-level APIs, such as email, profile, offline_access, and OpenId. It isn't used for other Graph scopes such as `User.Read` or `Mail.Read`. For suggested workarounds, see [Extend your app with Microsoft Graph permissions](tab-sso-graph-api.md).

+> - The `getAuthToken` fails for anonymous users as they aren't Azure AD accounts.

+Tabs are Teams-aware web pages. To enable SSO in a webpage hosted inside a tab app, add [Teams Javascript client library](/javascript/api/overview/msteams-client?) and call `microsoftTeams.initialize()`. After initialization, call `microsoftTeams.getAuthToken()` to get the access token for your app.

+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :::image type="content" source="../../../assets/images/authentication/teams-sso-tabs/enable-sso.png" alt-text="Screenshot shows the steps to enable SSO for tab." lightbox="../../../assets/images/authentication/teams-sso-tabs/enable-sso.png":::

+1. **Configure app with Azure AD**: Create an Azure AD app to generate an app ID and application ID URI. For generating access token, configure scopes and authorize trusted client applications.

+2. **Add code**: Add the code to handle access token, send this token to your app's server code in the Authorization header, and validate the access token when it's received.

+3. **Update Teams app manifest**: Update your Teams client app manifest with the app ID and application ID URI generated on Azure AD to allow Teams to request access tokens on behalf of your app.

+- **Don't store access token on client-side code**: DonΓÇÖt cache or store the access token in your app's client-side code. Teams client caches the access token (or request a new one if it expires). This ensures that there's no accidental leak of your token from your web app.

+- Multiple domains per app aren't supported. For more information, see [LOB apps](tab-sso-register-aad.md#before-you-configure-your-app).

+1. Open **Extensions** by selecting **View > Extensions** or **Ctrl+Shift+X**. You can also open extensions by selecting the extensions :::image type="icon" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/vsc-ext-icon.png" border="false"::: icon from the Visual Studio Code activity bar.

+ Teams Toolkit appears in the search result list.

+1. Select **Teams Toolkit**, and then from the Teams Toolkit extension page that appears in the right pane, select **Install**.

+ After successful installation of Teams Toolkit in Visual Studio Code, the Teams Toolkit icon appears in the Visual Studio Code activity bar.

+1. In the pop-up window that appears, select **Open**.

+ Visual Studio Code opens with the Teams Toolkit extension page.

+3. Select **Teams Toolkit**.

+4. On the **Teams Toolkit** page, select the dropdown next to the **Uninstall** button.

+ Teams Toolkit installs the version youΓÇÖve selected.

+ Visual Studio installer shows all workloads, whether installed or available for installation.

+ Select the following options to install Teams Toolkit:

+ 1. Select the **Workloads** tab, then select the **ASP.NET and web development** workload.

+ 1. On the right, select the **Microsoft Teams development tools** in the **Optional** section of the **Installation details** panel.

+ 1. Select **Install**.

+Teams Toolkit menu options are available in Visual Studio only when an app project created using Teams Toolkit is open.

+> [!NOTE]

+> Teams toolkit doesn't provide support to deploy resources to other cloud platforms except Azure, however, the user can deploy manually.

+* Ensure that the output of the auto-generated ARM template remains unchanged. You can add more outputs to the ARM template. The output is `.fx\states\state.{env}.json` and can be used in other features, such as deploy and validate manifest file.

+**2023 February**

+***February 09, 2023***: [Apps for Teams meetings support anonymous users.](apps-in-teams-meetings/build-apps-for-anonymous-user.md)

+<details>

+<summary><b>2023</b></summary>

+| **Date** | **Update** | **Find here** |

+| -- | | -|

+|31/01/2023| Introducing update and soft delete event notifications in bot | Build bots > Bot conversations > [Messages in bot conversations](bots/how-to/conversations/conversation-messages.md#update-message) |

+</details>

+</br>

+|31/01/2023| Introducing update and soft delete event notifications in bot | Build bots > Bot conversations > [Messages in bot conversations](bots/how-to/conversations/conversation-messages.md#update-message) |