Start blog posts for 2.1 preview#2829
Draft
rido-min wants to merge 1 commit into
Draft
Conversation
umangsehgal
reviewed
May 12, 2026
| description: Build bots that act on behalf of users with agentic identities in Teams SDK for .NET 2.1 preview — user-delegated tokens with zero manual plumbing. | ||
| --- | ||
|
|
||
| Your bot can now act on behalf of users, not just as itself. [Teams SDK for .NET 2.1 preview](/blog/announcing-teams-sdk-dotnet-2-1-preview) has built-in support for agentic identities, enabling bots to acquire user-delegated tokens and perform actions with the user's permissions. The SDK handles identity extraction and token acquisition transparently — you focus on what your bot does, not on token plumbing. |
Contributor
There was a problem hiding this comment.
"can now act on" -> "can today act on"
umangsehgal
reviewed
May 12, 2026
|
|
||
| Your bot can now act on behalf of users, not just as itself. [Teams SDK for .NET 2.1 preview](/blog/announcing-teams-sdk-dotnet-2-1-preview) has built-in support for agentic identities, enabling bots to acquire user-delegated tokens and perform actions with the user's permissions. The SDK handles identity extraction and token acquisition transparently — you focus on what your bot does, not on token plumbing. | ||
|
|
||
| For the full conceptual background on agentic identities and Agents 365, see the [Agents 365 documentation](https://learn.microsoft.com/agents-365). |
Contributor
There was a problem hiding this comment.
Comes in abstract, right after the OBO intro. Not rightly placed
umangsehgal
reviewed
May 12, 2026
| ## What Is an Agentic Identity? | ||
|
|
||
| Traditional bots authenticate as themselves using app-only tokens. They can send messages and call APIs, but only with the permissions granted to the app registration. An agentic identity changes this: the bot acts **on behalf of a specific user**, using that user's permissions and identity. | ||
|
|
Contributor
There was a problem hiding this comment.
does the agentic identity uses the user's permissions and identity? I am a little confused here
umangsehgal
reviewed
May 12, 2026
|
|
||
| For a deeper explanation of how agentic identities work in the Agents 365 ecosystem, see the [Agents 365 identity documentation](https://learn.microsoft.com/agents-365/identity). | ||
|
|
||
| ## How It Works in the SDK |
Contributor
There was a problem hiding this comment.
Lead the paragraphs prior to this with outcomes. Inviting people to read further about it in the SDK. The starting sections are not clear enough and we jump too soon into the SDK details
umangsehgal
reviewed
May 12, 2026
|
|
||
| Every API client in the SDK — `ActivityClient`, `ReactionClient`, `MemberClient`, `MeetingClient`, `TeamClient` — accepts an `AgenticIdentity` and threads it through to MSAL for token acquisition. When you use `context.Api` in a handler, this happens automatically. | ||
|
|
||
| ## Tutorial: Build a Bot That Acts on Behalf of an Agentic User |
Contributor
There was a problem hiding this comment.
This title is very confusing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds two new blog posts announcing and explaining major new features in the Teams SDK for .NET 2.1 preview. The first post introduces the overall SDK update, highlighting its native ASP.NET Core integration, typed activity routing, layered architecture, and agentic identity support. The second post provides a deep dive into agentic identities, showing how bots can act on behalf of users using user-delegated tokens with minimal manual setup. Together, these posts serve as both an announcement and practical guide for developers adopting the new SDK.
New blog posts and documentation:
Teams SDK for .NET 2.1 Preview Announcement:
Agentic Identity Support Overview: