Start blog post for 2.1 preview by rido-min · Pull Request #2829 · microsoft/teams-sdk

rido-min · 2026-05-12T18:35:24Z

Summary

Consolidated the three separate blog posts (announcement, agentic identity, Bot Framework migration) into a single comprehensive announcement post
Added a "Migration from Teams SDK 2.0" section summarizing backward-compatible APIs, breaking changes, and removed packages
Fixed "Agents 365" → "Agent 365" naming and updated links to learn.microsoft.com/microsoft-agent-365/
Updated publish date to 5/19

Test plan

Verify the blog post renders correctly with npm start in the teams.md directory
Confirm all internal anchor links (#agentic-identity, #migration-from-bot-framework-v4, #migration-from-teams-sdk-20, etc.) resolve correctly
Verify the Tabs/TabItem MDX components render properly in the MSAL Authentication section
Confirm SVG diagrams display correctly in both light and dark themes

Stacked on top of #2829 (`rido/blog-21preview`). Reframes the agentic identity blog post so the concept lands before the code does. ## Summary - New lede frames the post as "bot acts as itself vs. bot acts on behalf of someone else" rather than jumping straight into definitions. - Pulls the **Agents vs. AI teammate** distinction from the [Agent 365 docs](https://learn.microsoft.com/en-us/microsoft-agent-365/developer/get-started) into a table with a concrete *Pat the onboarder* example, so the AI teammate isn't an abstraction. - Two inline SVG diagrams (no external assets, `currentColor` for light/dark theme): - **Scenarios diagram** — side-by-side rows contrasting the two message paths and the token type each uses. - **Data-flow diagram** — `activity.From` → SDK (`AgenticIdentity.FromAccount` + MSAL) → `context.Api.*` outbound call, with the three agentic fields visible inside the source box. - Unified on `GetAgenticIdentity()` extension method throughout; removed the confusing dual presentation of `AgenticIdentity.FromAccount` and the extension method. - Lede is framing-agnostic — covers both "AI teammate" and "delegating user" so we can sharpen one or the other later by editing two sentences. The tutorial section, "What the SDK Handles for You," and "Get Started" sections from #2829 are unchanged — they were already solid. ## Open question The post still describes both AI teammate and OBO-style delegation as "agentic" scenarios. If we want to tighten the focus to AI teammates specifically (matching the Agent 365 launch arc), the opening two paragraphs are where to do it. ## Test plan - [ ] Pull the branch, `cd teams.md && npm run start:simple`, open `/teams-sdk/blog/bring-agentic-identities-to-teams-sdk-dotnet-2-1` - [ ] Verify both SVGs render correctly in light and dark mode - [ ] Verify cross-post links to the announcement and BotBuilder posts still resolve - [ ] Sanity-check the Agent 365 doc links 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Stacked on top of #2829 (`rido/blog-21preview`). Rewrites the lede of the .NET 2.1 announcement post so the value lands before the reader has to scroll. ## Before The original opener said the release "brings deeper ASP.NET Core integration, a layered architecture, and first-class support for agentic identities" — a feature-bucket sentence that requires reading the whole post to figure out what changes for *you* the reader. ## After Adopts the Next.js-style version-announcement pattern: 1. One-sentence headline + install command up top 2. Four value-bullets, each a journey beat (what you can DO), each anchored to the section that proves the claim 3. Handoff line into the deep-dive sections Bullet 3 keeps the framing flexible (\"users — including AI teammates\") so we can sharpen the AI-teammate vs OBO emphasis later without rewriting the lede. ## Reference patterns reviewed - Next.js 15 — 1-line opener → upgrade command → bulleted what's-new with section anchors - Bun 1.0 — emotional hook + one-liner + scope (rejected: that pattern fits a brand launch, not an incremental version) - Vercel AI SDK 5 — narrative-heavy with social proof (rejected: not needed for a first-party Microsoft SDK) ## Test plan - [ ] Pull the branch, `cd teams.md && npm run start:simple`, open `/teams-sdk/blog/announcing-teams-sdk-dotnet-2-1-preview` - [ ] Verify the four anchor links resolve (`#native-aspnet-core-integration`, `#msal-authentication`, `/blog/bring-agentic-identities-to-teams-sdk-dotnet-2-1`, `#migration-from-bot-framework-v4`) - [ ] Sanity-check the install command at the top matches the one at the bottom of the post 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Merge agentic identity and Bot Framework migration posts into the main announcement post, add migration-from-2.0 section, fix Agent 365 links, and update publish date to 5/19. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…riptions and author details

… migration details

Copilot

Pull request overview

Adds a new Teams SDK for .NET 2.1 preview announcement blog post covering ASP.NET Core integration, agentic identity, OAuth/SSO, and migration guidance.

Changes:

Introduces a new dated local blog post with frontmatter and truncate marker.
Adds SDK usage examples, migration steps from Bot Framework v4 and Teams SDK 2.0.
Includes roadmap and supported scenario summary for the preview.

nickwalkmsft

Just a couple tiny nits, LGTM. Exciting stuff!

…ew/index.md Co-authored-by: Nick Walker <nickwalk@microsoft.com>

start blog posts for 2.1 preview

9648018