[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69B89DDTF9HYVQTA5RC7W1C":3,"skill-same:01M69B89DDTF9HYVQTA5RC7W1C":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M69B89DDTF9HYVQTA5RC7W1C","bf-to-agents-sdk-dotnet-migration",null,"Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.","microsoft\u002FAgents","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69B7CR81D1HSNV69XDT8KAR",1109,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-net\u002Fskills\u002Fbf-to-agents-sdk-dotnet-migration\u002FSKILL.md",[],[19,20,21,22,23,24,9,25,26],"agents sdk","sdk","dotnet","agents sdk dotnet","bf to agents sdk dotnet migration","bot","packages","core","2026-11-10 10:12:30",false,"---\nname: bf-to-agents-sdk-dotnet-migration\ndescription: >\n  Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK.\n  Triggered by projects that depend on packages: Microsoft.Bot.Builder or\n  Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.\n---\n\n# Bot Framework to Agents SDK Migration (.NET)\n\n## Overview\n\nMigrates a Bot Framework SDK bot to Microsoft 365 Agents SDK using the `ActivityHandler`\u002F`TeamsActivityHandler` compat layer — minimal code changes, original class names preserved.\n\n**This skill stops at the compat layer.** After completing this migration, ask the user whether to also convert to `AgentApplication` (see final step).\n\n**Agents DotNet SDK repository:** https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagents-for-net\n**Bot Framework DotNet SDK repository:** https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbotbuilder-dotnet\n\n---\n\n## Core Rules\n\n- **Retain the original bot class name.** Do not rename or create a new class — renaming breaks git history.\n- **Only change what is required for a clean migration.** Do not refactor, restructure, or improve beyond what is needed to compile and run on Agents SDK.\n\n---\n\n## Package Replacements\n\n**Version:** Always use the latest **stable** (non-beta) version of Agents SDK packages by default.\n\n| Remove (Bot Framework) | Add (Agents SDK) |\n|------------------------|------------------|\n| `Microsoft.Bot.Builder.Integration.AspNet.Core` | `Microsoft.Agents.Hosting.AspNetCore` |\n| `Microsoft.Bot.Builder` | `Microsoft.Agents.Builder` |\n| `Microsoft.Bot.Builder.Teams` | `Microsoft.Agents.Extensions.Teams` |\n| `Microsoft.Bot.Builder.Dialogs` | `Microsoft.Agents.Builder.Dialogs` |\n| `Microsoft.Bot.Connector` | `Microsoft.Agents.Connector` |\n| `Microsoft.Bot.Connector.Authentication` \u002F MSAL auth packages | `Microsoft.Agents.Authentication.Msal` |\n\n## Deprecated Packages — No Agents SDK Equivalent\n\nThe following Bot Framework packages have **no equivalent** in the Agents SDK and are not supported. There is no recommended replacement. Remove them from the `.csproj`, but **do not attempt to migrate the code that uses them** — it will cause build errors that cannot be resolved within the Agents SDK migration. Flag this to the customer.\n\n| Deprecated Package |\n|--------------------|\n| `Microsoft.Bot.Builder.AI.Luis` |\n| `Microsoft.Bot.Builder.AI.Orchestrator` |\n| `Microsoft.Bot.Builder.AI.QnA` |\n| `Microsoft.Bot.Builder.Azure.Queues` |\n| `Microsoft.Bot.Builder.Dialogs.Adaptive` |\n| `Microsoft.Bot.Builder.Dialogs.Adaptive.Runtime` |\n| `Microsoft.Bot.Builder.Dialogs.Adaptive.Testing` |\n| `Microsoft.Bot.Builder.Dialogs.Debugging` |\n| `Microsoft.Bot.Builder.LanguageGeneration` |\n| `Microsoft.Bot.Builder.TemplateManager` |\n| `Microsoft.Bot.Configuration` |\n| `Microsoft.Bot.Connector.Streaming` |\n| `Microsoft.Bot.Streaming` |\n| `Microsoft.Bot.Builder.Parsers.LU` |\n| `AdaptiveExpressions` |\n\n**Migration still proceeds** — complete all other migration steps. The build errors from unmigrated code must be communicated to the customer as out-of-scope blockers.\n\n---\n\n## Namespace Replacements\n\n| Old | New |\n|-----|-----|\n| `Microsoft.Bot.Builder` | `Microsoft.Agents.Builder` |\n| `Microsoft.Bot.Builder` (ActivityHandler) | `Microsoft.Agents.Builder.Compat` |\n| `Microsoft.Bot.Builder` (AutoSaveStateMiddleware) | `Microsoft.Agents.Builder.Compat` |\n| `Microsoft.Bot.Builder.Teams` (TeamsActivityHandler) | `Microsoft.Agents.Extensions.Teams.Compat` |\n| `Microsoft.Bot.Schema` | `Microsoft.Agents.Core.Models` |\n| `Microsoft.Bot.Schema.Teams` | `Microsoft.Agents.Extensions.Teams.Models` |\n| `Microsoft.Bot.Builder.Dialogs` | `Microsoft.Agents.Builder.Dialogs` |\n| `Microsoft.Bot.Builder.Dialogs` (PromptValidatorContext, PromptValidatorContext\\\u003CT\\>) | `Microsoft.Agents.Builder.Dialogs.Prompts` |\n| `Microsoft.Bot.Builder.Integration.AspNet.Core` | `Microsoft.Agents.Hosting.AspNetCore` |\n| `Microsoft.Bot.Builder.TraceExtensions` | *(remove)* — `TraceActivityAsync` is built into `ITurnContext` |\n\n---\n\n## Migration Steps\n\n### Step 1: Update packages and namespaces (see tables above)\n\n### Step 2: Keep bot class — retain original class name, only update `using` statements\n\n`ActivityHandler` and `TeamsActivityHandler` exist unchanged in the Compat namespace. All override methods keep the same signatures. **Do not rename the class.**\n\n```csharp\n\u002F\u002F Before\nusing Microsoft.Bot.Builder;\nusing Microsoft.Bot.Schema;\npublic class EchoBot : ActivityHandler { \u002F* unchanged *\u002F }\n\n\u002F\u002F After — only using directives change; class name stays EchoBot\nusing Microsoft.Agents.Builder;\nusing Microsoft.Agents.Builder.Compat;    \u002F\u002F ActivityHandler lives here\nusing Microsoft.Agents.Core.Models;        \u002F\u002F IMessageActivity, ChannelAccount, etc.\npublic class EchoBot : ActivityHandler { \u002F* unchanged *\u002F }\n```\n\nFor Teams:\n```csharp\n\u002F\u002F Before\nusing Microsoft.Bot.Builder.Teams;\nusing Microsoft.Bot.Schema.Teams;\npublic class MyBot : TeamsActivityHandler { \u002F* unchanged *\u002F }\n\n\u002F\u002F After — class name stays MyBot\nusing Microsoft.Agents.Extensions.Teams.Compat;   \u002F\u002F TeamsActivityHandler lives here\nusing Microsoft.Agents.Extensions.Teams.Models;    \u002F\u002F TeamsChannelAccount, TeamInfo, etc.\npublic class MyBot : TeamsActivityHandler { \u002F* unchanged *\u002F }\n```\n\n### Step 3: State management for dialog bots\n\nIf the bot overrides `OnTurnAsync` to call `SaveChangesAsync`, both patterns work — keep whichever the bot already uses:\n\n```csharp\n\u002F\u002F Option A: Keep existing pattern in OnTurnAsync (works as-is)\npublic override async Task OnTurnAsync(ITurnContext ctx, CancellationToken ct)\n{\n    await base.OnTurnAsync(ctx, ct);\n    await ConversationState.SaveChangesAsync(ctx, false, ct);\n    await UserState.SaveChangesAsync(ctx, false, ct);\n}\n\n\u002F\u002F Option B: Use AutoSaveStateMiddleware (register in adapter setup)\n\u002F\u002F adapter.Use(new AutoSaveStateMiddleware(conversationState, userState));\n```\n\n### Step 4: New Program.cs\n\nDelete `BotController.cs` and `AdapterWithErrorHandler.cs`. Create `Program.cs`:\n\n```csharp\nusing Microsoft.Agents.Hosting.AspNetCore;\nusing Microsoft.Agents.Storage;\nusing Microsoft.AspNetCore.Builder;\nusing Microsoft.Extensions.DependencyInjection;\nusing Microsoft.Extensions.Hosting;\n\nWebApplicationBuilder builder = WebApplication.CreateBuilder(args);\n\nbuilder.Services.AddHttpClient();\nbuilder.Services.AddControllers();\n\n\u002F\u002F Register bot — AddAgent works because ActivityHandler implements IAgent\n\u002F\u002F DO NOT call AddAgentApplicationOptions() — that is only for AgentApplication\nbuilder.AddAgent\u003CMyBot>();\n\n\u002F\u002F Storage — always required by the Agents SDK\nbuilder.Services.AddSingleton\u003CIStorage, MemoryStorage>();\n\n\u002F\u002F Preserve all customer-specific DI registrations:\n\u002F\u002F builder.Services.AddSingleton\u003CConversationState>();\n\u002F\u002F builder.Services.AddSingleton\u003CUserState>();\n\u002F\u002F builder.Services.AddSingleton\u003CMyDialog>();\n\u002F\u002F builder.Services.AddSingleton\u003CIMyService, MyService>();\n\n\u002F\u002F AddAgentAspNetAuthentication is defined in AspNetExtensions.cs — copy from any Agents SDK sample\nbuilder.Services.AddAgentAspNetAuthentication(builder.Configuration);\n\nWebApplication app = builder.Build();\n\napp.UseAuthentication();\napp.UseAuthorization();\napp.MapAgentRootEndpoint();\n\n\u002F\u002F ActivityHandler bots use MapAgentEndpoints — NOT MapAgentApplicationEndpoints\n\u002F\u002F MapAgentApplicationEndpoints only works for AgentApplication subclasses\napp.MapAgentEndpoints(requireAuth: !app.Environment.IsDevelopment());\n\nif (app.Environment.IsDevelopment())\n{\n    app.Urls.Add(\"http:\u002F\u002Flocalhost:3978\");\n}\n\napp.Run();\n```\n\n**If customer had custom logic in `BotController`**, preserve it using the process delegate:\n```csharp\napp.MapAgentEndpoints(\n    requireAuth: !app.Environment.IsDevelopment(),\n    process: async (request, response, adapter, agent, ct) =>\n    {\n        \u002F\u002F Custom controller logic here\n        await adapter.ProcessAsync(request, response, agent, ct);\n    });\n```\n\n### Step 5 or at the very end of the migration:  Ask user if they would like to write the learnings from this migration to a markdown file they could submit to use to help us improve the skill.\n\n---\n\n## appsettings.json Changes\n\nRemove Bot Framework auth config and add Agents SDK config. The shape of `Connections:ServiceConnection` depends on the value of `MicrosoftAppType` in the existing appsettings.\n\n**In all cases:** remove `MicrosoftAppId`, `MicrosoftAppPassword`, `MicrosoftAppType`, and `MicrosoftAppTenantId` — their values are carried forward into the new structure.\n\n---\n\n### Case 1: `MicrosoftAppType` = `\"SingleTenant\"`\n\n```json\n{\n  \"Connections\": {\n    \"ServiceConnection\": {\n      \"Settings\": {\n        \"AuthType\": \"ClientSecret\",\n        \"AuthorityEndpoint\": \"https:\u002F\u002Flogin.microsoftonline.com\u002F{MicrosoftAppTenantId}\",\n        \"ClientId\": \"{MicrosoftAppId}\",\n        \"ClientSecret\": \"{MicrosoftAppPassword}\",\n        \"Scopes\": [\"https:\u002F\u002Fapi.botframework.com\u002F.default\"]\n      }\n    }\n  },\n  \"ConnectionsMap\": [\n    {\n      \"ServiceUrl\": \"*\",\n      \"Connection\": \"ServiceConnection\"\n    }\n  ],\n  \"TokenValidation\": {\n    \"Enabled\": true,\n    \"Audiences\": [\"{MicrosoftAppId}\"],\n    \"TenantId\": \"{MicrosoftAppTenantId}\"\n  }\n}\n```\n\n---\n\n### Case 2: `MicrosoftAppType` = `\"UserAssignedMSI\"`\n\n```json\n{\n  \"Connections\": {\n    \"ServiceConnection\": {\n      \"Settings\": {\n        \"AuthType\": \"UserManagedIdentity\",\n        \"ClientId\": \"{MicrosoftAppId}\",\n        \"Scopes\": [\"https:\u002F\u002Fapi.botframework.com\u002F.default\"]\n      }\n    }\n  },\n  \"ConnectionsMap\": [\n    {\n      \"ServiceUrl\": \"*\",\n      \"Connection\": \"ServiceConnection\"\n    }\n  ],\n  \"TokenValidation\": {\n    \"Enabled\": true,\n    \"Audiences\": [\"{MicrosoftAppId}\"],\n    \"TenantId\": \"{MicrosoftAppTenantId}\"\n  }\n}\n```\n\n---\n\n### Case 3: `MicrosoftAppType` = `\"MultiTenant\"`, missing, or null\n\n```json\n{\n  \"Connections\": {\n    \"ServiceConnection\": {\n      \"Settings\": {\n        \"AuthType\": \"ClientSecret\",\n        \"AuthorityEndpoint\": \"https:\u002F\u002Flogin.microsoftonline.com\u002Fbotframework.com\",\n        \"ClientId\": \"{MicrosoftAppId}\",\n        \"TenantId\": \"{MicrosoftAppTenantId}\",\n        \"ClientSecret\": \"{MicrosoftAppPassword}\",\n        \"Scopes\": [\"https:\u002F\u002Fapi.botframework.com\u002F.default\"]\n      }\n    }\n  },\n  \"ConnectionsMap\": [\n    {\n      \"ServiceUrl\": \"*\",\n      \"Connection\": \"ServiceConnection\"\n    }\n  ],\n  \"TokenValidation\": {\n    \"Enabled\": true,\n    \"Audiences\": [\"{MicrosoftAppId}\"],\n    \"TenantId\": \"{MicrosoftAppTenantId}\"\n  }\n}\n```\n\n---\n\n### Case 4: Any other `MicrosoftAppType` value\n\nDo **not** generate `Connections:ServiceConnection`. Complete all other migration steps, then at the end inform the user:\n\n> \"The `MicrosoftAppType` value `{value}` is not a standard type recognized by this migration. The `Connections:ServiceConnection` block was not changed — additional manual configuration will be required. See: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fmicrosoft-365\u002Fagents-sdk\u002Fmicrosoft-authentication-library-configuration-options\"\n\n---\n\n## Custom BotAdapter\n\nIf the source bot subclasses `BotAdapter`, migrate it to `ChannelAdapter` (`Microsoft.Agents.Builder`).\n\n### Class hierarchy to choose from\n\n| Use when | Subclass |\n|----------|----------|\n| Custom transport \u002F non-Azure channel | `ChannelAdapter` (abstract, minimal pipeline) |\n| Azure Bot Service connectivity with custom behavior | `CloudAdapter` (`Microsoft.Agents.Hosting.AspNetCore`) |\n\nMost custom `BotAdapter` subclasses fall into the **CloudAdapter** case. Prefer that unless the adapter is implementing a completely custom transport.\n\n### API mapping\n\n| Bot Framework `BotAdapter` | Agents SDK |\n|---------------------------|------------|\n| `using Microsoft.Bot.Builder;` | `using Microsoft.Agents.Builder;` |\n| `: BotAdapter` | `: ChannelAdapter` or `: CloudAdapter` |\n| `Activity[]` in `SendActivitiesAsync` | `IActivity[]` in `SendActivitiesAsync` |\n| `BotCallbackHandler` callback delegate | `AgentCallbackHandler` |\n| `abstract UpdateActivityAsync(...)` | `virtual UpdateActivityAsync(...)` (throws `NotImplementedException` if not overridden) |\n| `abstract DeleteActivityAsync(...)` | `virtual DeleteActivityAsync(...)` (throws `NotImplementedException` if not overridden) |\n| `protected RunPipelineAsync(ctx, BotCallbackHandler, ct)` | `protected RunPipelineAsync(ctx, AgentCallbackHandler, ct)` |\n\n### Registration\n\nRegister the custom adapter via the two-type overload of `AddAgent`. Note `AddAgent\u003CTAgent, TAdapter>` requires `TAdapter : CloudAdapter`:\n\n```csharp\nbuilder.AddAgent\u003CMyBot, MyCustomAdapter>();\n```\n\nIf the custom adapter subclasses `ChannelAdapter` directly (not `CloudAdapter`), register manually:\n\n```csharp\nbuilder.AddAgentCore();  \u002F\u002F registers IConnections, IChannelServiceClientFactory\nbuilder.Services.AddSingleton\u003CIChannelAdapter, MyCustomAdapter>();\nbuilder.Services.AddSingleton\u003CIAgentHttpAdapter>(sp => (IAgentHttpAdapter)sp.GetRequiredService\u003CIChannelAdapter>());\nbuilder.Services.AddTransient\u003CIAgent, MyAgent>();\n```\n\n---\n\n## Custom IMiddleware\n\nIf the source bot implements `Microsoft.Bot.Builder.IMiddleware`, retain the class and update its namespaces:\n\n| Old | New |\n|-----|-----|\n| `Microsoft.Bot.Builder.IMiddleware` | `Microsoft.Agents.Builder.IMiddleware` |\n| `Microsoft.Bot.Builder.ITurnContext` | `Microsoft.Agents.Builder.ITurnContext` |\n| `Microsoft.Bot.Builder.NextDelegate` | `Microsoft.Agents.Builder.NextDelegate` |\n\nThe `OnTurnAsync(ITurnContext, NextDelegate, CancellationToken)` signature is unchanged.\n\nRegister custom middleware via a `CloudAdapter` subclass. Delete `AdapterWithErrorHandler.cs` only if it has no custom middleware — if it does, rename it or keep it as a custom adapter:\n\n```csharp\n\u002F\u002F CustomAdapter.cs\nusing Microsoft.Agents.Builder;\nusing Microsoft.Agents.Hosting.AspNetCore;\nusing Microsoft.Agents.Hosting.AspNetCore.BackgroundQueue;\nusing Microsoft.Extensions.Logging;\n\npublic class CustomAdapter : CloudAdapter\n{\n    public CustomAdapter(\n        IChannelServiceClientFactory channelServiceClientFactory,\n        IActivityTaskQueue activityTaskQueue,\n        ILogger\u003CCloudAdapter> logger = null)\n        : base(channelServiceClientFactory, activityTaskQueue, logger: logger)\n    {\n        Use(new MyCustomMiddleware());\n        \u002F\u002F Use(new AnotherMiddleware(...));\n    }\n}\n```\n\nRegister the custom adapter in `Program.cs`:\n\n```csharp\nbuilder.AddAgent\u003CMyBot, CustomAdapter>();\n```\n\n---\n\n## Files to Add\n\nEvery migrated project needs `AspNetExtensions.cs` — the `AddAgentAspNetAuthentication()` extension method is **not in any NuGet package**; it is a sample-provided file. Copy it from the Agents SDK shared samples (https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents-for-net\u002Fblob\u002Fmain\u002Fsrc\u002Fsamples\u002FShared\u002FAspNetExtensions.cs).\n\n---\n\n## Files to Delete\n\nAlways delete these from the source project:\n- `AdapterWithErrorHandler.cs` — delete if it only has `OnTurnError` logic (Agents SDK handles errors internally); **retain and rename** if it contains custom `Use()` middleware registrations (see Custom IMiddleware section above)\n- `BotController.cs` (unless it has custom logic — see preservation note above)\n- Any `Startup.cs` (merge into `Program.cs`)\n\n---\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Renamed the bot class or created a new class | Restore the original class name — renaming breaks git history |\n| Changed more than needed (refactored, restructured) | Revert — only change what is required to compile and run |\n| Called `AddAgentApplicationOptions()` for ActivityHandler bot | Remove — only for AgentApplication |\n| Used `MapAgentApplicationEndpoints()` for ActivityHandler bot | Use `MapAgentEndpoints()` — former only works for AgentApplication |\n| Left `services.AddTransient\u003CIBot, MyBot>()` | Replace with `builder.AddAgent\u003CMyBot>()` |\n| Left `services.AddSingleton\u003CIBotFrameworkHttpAdapter, AdapterWithErrorHandler>()` | Delete — handled by `AddAgent\u003C>()` |\n| Left `ConfigurationBotFrameworkAuthentication` | Delete — use `AddAgentAspNetAuthentication()` |\n| Missing `IStorage` registration | Add `builder.Services.AddSingleton\u003CIStorage, MemoryStorage>();` — always required, not just for dialog bots |\n| Left old Bot Framework appsettings (`MicrosoftAppId` etc.) | Replace with `Connections` + `TokenValidation` — shape depends on `MicrosoftAppType` (see appsettings.json Changes section) |\n| Used the wrong `Connections:ServiceConnection` shape | Check `MicrosoftAppType`: `SingleTenant`→ClientSecret+tenant authority; `UserAssignedMSI`→UserManagedIdentity (no secret); `MultiTenant`\u002Fmissing→ClientSecret+botframework.com authority |\n| Left `BotAdapter` as base class of custom adapter | Change to `ChannelAdapter` or `CloudAdapter`; update `Activity[]` → `IActivity[]`, `BotCallbackHandler` → `AgentCallbackHandler` |\n| Deleted `AdapterWithErrorHandler.cs` that contained custom `Use()` calls | Retain it (renamed if needed) as a `CloudAdapter` subclass; register via `builder.AddAgent\u003CTBot, TAdapter>()` |\n| Left `Microsoft.Bot.Builder.IMiddleware` namespace in custom middleware | Update to `Microsoft.Agents.Builder.IMiddleware` |\n| Attempted to migrate code using a deprecated package (Luis, QnA, Adaptive, etc.) | Stop — no Agents SDK equivalent exists. Remove the package reference, leave the code in place, and flag build errors to the customer |\n| Forgot to add `AspNetExtensions.cs` | Copy from any Agents SDK sample — `AddAgentAspNetAuthentication` is not in any NuGet package |\n| Left `conversationState.DeleteAsync(...)` in adapter | Rename to `conversationState.DeleteStateAsync(...)` — method was renamed in Agents SDK |\n| New `Program.cs` fails to compile (WebApplication, AddSingleton, IsDevelopment not found) | BF projects don't have `\u003CImplicitUsings>enable\u003C\u002FImplicitUsings>` — add explicit `using` for `Microsoft.AspNetCore.Builder`, `Microsoft.Extensions.DependencyInjection`, `Microsoft.Extensions.Hosting` |\n\n---\n\n## After Migration: Optional AgentApplication Upgrade\n\nOnce the compat-layer migration is complete and the build is clean, ask the user:\n\n> \"The bot is now running on Agents SDK using the ActivityHandler compat layer. Would you like to also migrate to the modern `AgentApplication` routing pattern? This involves converting the bot class to subclass `AgentApplication` and updating Program.cs — it is handled by the `agents-sdk-dotnet-activityhandler-migration` skill.\"\n\nIf yes, invoke `agents-sdk-dotnet-activityhandler-migration`.\nIf no, migration is complete.\n","# Bot Framework to Agents SDK Migration (.NET)\n\n## Overview\n\nMigrates a Bot Framework SDK bot to Microsoft 365 Agents SDK using the `ActivityHandler`\u002F`TeamsActivityHandler` compat layer — minimal code changes, original class names preserved.\n\n**This skill stops at the compat layer.** After completing this migration, ask the user whether to also convert to `AgentApplication` (see final step).\n\n**Agents DotNet SDK repository:** https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagents-for-net\n**Bot Framework DotNet SDK repository:** https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fbotbuilder-dotnet\n\n---\n\n## Core Rules\n\n- **Retain the original bot class name.** Do not rename or create a new class — renaming breaks git history.\n- **Only change what is required for a clean migration.** Do not refactor, restructure, or improve beyond what is needed to compile and run on Agents SDK.\n\n---\n\n## Package Replacements\n\n**Version:** Always use the latest **stable** (non-beta) version of Agents SDK packages by default.\n\n| Remove (Bot Framework) | Add (Agents SDK) |\n|------------------------|------------------|\n| `Microsoft.Bot.Builder.Integration.AspNet.Core` | `Microsoft.Agents.Hosting.AspNetCore` |\n| `Microsoft.Bot.Builder` | `Microsoft.Agents.Builder` |\n| `Microsoft.Bot.Builder.Teams` | `Microsoft.Agents.Extensions.Teams` |\n| `Microsoft.Bot.Builder.Dialogs` | `Microsoft.Agents.Builder.Dialogs` |\n| `Microsoft.Bot.Connector` | `Microsoft.Agents.Connector` |\n| `Microsoft.Bot.Connector.Authentication` \u002F MSAL auth packages | `Microsoft.Agents.Authentication.Msal` |\n\n## Deprecated Packages — No Agents SDK Equivalent\n\nThe following Bot Framework packages have **no equivalent** in the Agents SDK and are not supported. There is no recommended replacement. Remove them from the `.csproj`, but **do not attempt to migrate the code that uses them** — it will cause build errors that cannot be resolved within the Agents SDK migration. Flag this to the customer.\n\n| Deprecated Package |\n|--------------------|\n| `Microsoft.Bot.Builder.AI.Luis` |\n| `Microsoft.Bot.Builder.AI.Orchestrator` |\n| `Microsoft.Bot.Builder.AI.QnA` |\n| `Microsoft.Bot.Builder.Azure.Queues` |\n| `Microsoft.Bot.Builder.Dialogs.Adaptive` |\n| `Microsoft.Bot.Builder.Dialogs.Adaptive.Runtime` |\n| `Microsoft.Bot.Builder.Dialogs.Adaptive.Testing` |\n| `Microsoft.Bot.Builder.Dialogs.Debugging` |\n| `Microsoft.Bot.Builder.LanguageGeneration` |\n| `Microsoft.Bot.Builder.TemplateManager` |\n| `Microsoft.Bot.Configuration` |\n| `Microsoft.Bot.Connector.Streaming` |\n| `Microsoft.Bot.Streaming` |\n| `Microsoft.Bot.Builder.Parsers.LU` |\n| `AdaptiveExpressions` |\n\n**Migration still proceeds** — complete all other migration steps. The build errors from unmigrated code must be communicated to the customer as out-of-scope blockers.\n\n---\n\n## Namespace Replacements\n\n| Old | New |\n|-----|-----|\n| `Microsoft.Bot.Builder` | `Microsoft.Agents.Builder` |\n| `Microsoft.Bot.Builder` (ActivityHandler) | `Microsoft.Agents.Builder.Compat` |\n| `Microsoft.Bot.Builder` (AutoSaveStateMiddleware) | `Microsoft.Agents.Builder.Compat` |\n| `Microsoft.Bot.Builder.Teams` (TeamsActivityHandler) | `Microsoft.Agents.Extensions.Teams.Compat` |\n| `Microsoft.Bot.Schema` | `Microsoft.Agents.Core.Models` |\n| `Microsoft.Bot.Schema.Teams` | `Microsoft.Agents.Extensions.Teams.Models` |\n| `Microsoft.Bot.Builder.Dialogs` | `Microsoft.Agents.Builder.Dialogs` |\n| `Microsoft.Bot.Builder.Dialogs` (PromptValidatorContext, PromptValidatorContext\\\u003CT\\>) | `Microsoft.Agents.Builder.Dialogs.Prompts` |\n| `Microsoft.Bot.Builder.Integration.AspNet.Core` | `Microsoft.Agents.Hosting.AspNetCore` |\n| `Microsoft.Bot.Builder.TraceExtensions` | *(remove)* — `TraceActivityAsync` is built into `ITurnContext` |\n\n---\n\n## Migration Steps\n\n### Step 1: Update packages and namespaces (see tables above)\n\n### Step 2: Keep bot class — retain original class name, only update `using` statements\n\n`ActivityHandler` and `TeamsActivityHandler` exist unchanged in the Compat namespace. All override methods keep the same signatures. **Do not rename the class.**\n\n```csharp\n\u002F\u002F Before\nusing Microsoft.Bot.Builder;\nusing Microsoft.Bot.Schema;\npublic class EchoBot : ActivityHandler { \u002F* unchanged *\u002F }\n\n\u002F\u002F After — only using directives change; class name stays EchoBot\nusing Microsoft.Agents.Builder;\nusing Microsoft.Agents.Builder.Compat;    \u002F\u002F ActivityHandler lives here\nusing Microsoft.Agents.Core.Models;        \u002F\u002F IMessageActivity, ChannelAccount, etc.\npublic class EchoBot : ActivityHandler { \u002F* unchanged *\u002F }\n```\n\nFor Teams:\n```csharp\n\u002F\u002F Before\nusing Microsoft.Bot.Builder.Teams;\nusing Microsoft.Bot.Schema.Teams;\npublic class MyBot : TeamsActivityHandler { \u002F* unchanged *\u002F }\n\n\u002F\u002F After — class name stays MyBot\nusing Microsoft.Agents.Extensions.Teams.Compat;   \u002F\u002F TeamsActivityHandler lives here\nusing Microsoft.Agents.Extensions.Teams.Models;    \u002F\u002F TeamsChannelAccount, TeamInfo, etc.\npublic class MyBot : TeamsActivityHandler { \u002F* unchanged *\u002F }\n```\n\n### Step 3: State management for dialog bots\n\nIf the bot overrides `OnTurnAsync` to call `SaveChangesAsync`, both patterns work — keep whichever the bot already uses:\n\n```csharp\n\u002F\u002F Option A: Keep existing pattern in OnTurnAsync (works as-is)\npublic override async Task OnTurnAsync(ITurnContext ctx, CancellationToken ct)\n{\n    await base.OnTurnAsync(ctx, ct);\n    await ConversationState.SaveChangesAsync(ctx, false, ct);\n    await UserState.SaveChangesAsync(ctx, false, ct);\n}\n\n\u002F\u002F Option B: Use AutoSaveStateMiddleware (register in adapter setup)\n\u002F\u002F adapter.Use(new AutoSaveStateMiddleware(conversationState, userState));\n```\n\n### Step 4: New Program.cs\n\nDelete `BotController.cs` and `AdapterWithErrorHandler.cs`. Create `Program.cs`:\n\n```csharp\nusing Microsoft.Agents.Hosting.AspNetCore;\nusing Microsoft.Agents.Storage;\nusing Microsoft.AspNetCore.Builder;\nusing Microsoft.Extensions.DependencyInjection;\nusing Microsoft.Extensions.Hosting;\n\nWebApplicationBuilder builder = WebApplication.CreateBuilder(args);\n\nbuilder.Services.AddHttpClient();\nbuilder.Services.AddControllers();\n\n\u002F\u002F Register bot — AddAgent works because ActivityHandler implements IAgent\n\u002F\u002F DO NOT call AddAgentApplicationOptions() — that is only for AgentApplication\nbuilder.AddAgent\u003CMyBot>();\n\n\u002F\u002F Storage — always required by the Agents SDK\nbuilder.Services.AddSingleton\u003CIStorage, MemoryStorage>();\n\n\u002F\u002F Preserve all customer-specific DI registrations:\n\u002F\u002F builder.Services.AddSingleton\u003CConversationState>();\n\u002F\u002F builder.Services.AddSingleton\u003CUserState>();\n\u002F\u002F builder.Services.AddSingleton\u003CMyDialog>();\n\u002F\u002F builder.Services.AddSingleton\u003CIMyService, MyService>();\n\n\u002F\u002F AddAgentAspNetAuthentication is defined in AspNetExtensions.cs — copy from any Agents SDK sample\nbuilder.Services.AddAgentAspNetAuthentication(builder.Configuration);\n\nWebApplication app = builder.Build();\n\napp.UseAuthentication();\napp.UseAuthorization();\napp.MapAgentRootEndpoint();\n\n\u002F\u002F ActivityHandler bots use MapAgentEndpoints — NOT MapAgentApplicationEndpoints\n\u002F\u002F MapAgentApplicationEndpoints only works for AgentApplication subclasses\napp.MapAgentEndpoints(requireAuth: !app.Environment.IsDevelopment());\n\nif (app.Environment.IsDevelopment())\n{\n    app.Urls.Add(\"http:\u002F\u002Flocalhost:3978\");\n}\n\napp.Run();\n```\n\n**If customer had custom logic in `BotController`**, preserve it using the process delegate:\n```csharp\napp.MapAgentEndpoints(\n    requireAuth: !app.Environment.IsDevelopment(),\n    process: async (request, response, adapter, agent, ct) =>\n    {\n        \u002F\u002F Custom controller logic here\n        await adapter.ProcessAsync(request, response, agent, ct);\n    });\n```\n\n### Step 5 or at the very end of the migration:  Ask user if they would like to write the learnings from this migration to a markdown file they could submit to use to help us improve the skill.\n\n---\n\n## appsettings.json Changes\n\nRemove Bot Framework auth config and add Agents SDK config. The shape of `Connections:ServiceConnection` depends on the value of `MicrosoftAppType` in the existing appsettings.\n\n**In all cases:** remove `MicrosoftAppId`, `MicrosoftAppPassword`, `MicrosoftAppType`, and `MicrosoftAppTenantId` — their values are carried forward into the new structure.\n\n---\n\n### Case 1: `MicrosoftAppType` = `\"SingleTenant\"`\n\n```json\n{\n  \"Connections\": {\n    \"ServiceConnection\": {\n      \"Settings\": {\n        \"AuthType\": \"ClientSecret\",\n        \"AuthorityEndpoint\": \"https:\u002F\u002Flogin.microsoftonline.com\u002F{MicrosoftAppTenantId}\",\n        \"ClientId\": \"{MicrosoftAppId}\",\n        \"ClientSecret\": \"{MicrosoftAppPassword}\",\n        \"Scopes\": [\"https:\u002F\u002Fapi.botframework.com\u002F.default\"]\n      }\n    }\n  },\n  \"ConnectionsMap\": [\n    {\n      \"ServiceUrl\": \"*\",\n      \"Connection\": \"ServiceConnection\"\n    }\n  ],\n  \"TokenValidation\": {\n    \"Enabled\": true,\n    \"Audiences\": [\"{MicrosoftAppId}\"],\n    \"TenantId\": \"{MicrosoftAppTenantId}\"\n  }\n}\n```\n\n---\n\n### Case 2: `MicrosoftAppType` = `\"UserAssignedMSI\"`\n\n```json\n{\n  \"Connections\": {\n    \"ServiceConnection\": {\n      \"Settings\": {\n        \"AuthType\": \"UserManagedIdentity\",\n        \"ClientId\": \"{MicrosoftAppId}\",\n        \"Scopes\": [\"https:\u002F\u002Fapi.botframework.com\u002F.default\"]\n      }\n    }\n  },\n  \"ConnectionsMap\": [\n    {\n      \"ServiceUrl\": \"*\",\n      \"Connection\": \"ServiceConnection\"\n    }\n  ],\n  \"TokenValidation\": {\n    \"Enabled\": true,\n    \"Audiences\": [\"{MicrosoftAppId}\"],\n    \"TenantId\": \"{MicrosoftAppTenantId}\"\n  }\n}\n```\n\n---\n\n### Case 3: `MicrosoftAppType` = `\"MultiTenant\"`, missing, or null\n\n```json\n{\n  \"Connections\": {\n    \"ServiceConnection\": {\n      \"Settings\": {\n        \"AuthType\": \"ClientSecret\",\n        \"AuthorityEndpoint\": \"https:\u002F\u002Flogin.microsoftonline.com\u002Fbotframework.com\",\n        \"ClientId\": \"{MicrosoftAppId}\",\n        \"TenantId\": \"{MicrosoftAppTenantId}\",\n        \"ClientSecret\": \"{MicrosoftAppPassword}\",\n        \"Scopes\": [\"https:\u002F\u002Fapi.botframework.com\u002F.default\"]\n      }\n    }\n  },\n  \"ConnectionsMap\": [\n    {\n      \"ServiceUrl\": \"*\",\n      \"Connection\": \"ServiceConnection\"\n    }\n  ],\n  \"TokenValidation\": {\n    \"Enabled\": true,\n    \"Audiences\": [\"{MicrosoftAppId}\"],\n    \"TenantId\": \"{MicrosoftAppTenantId}\"\n  }\n}\n```\n\n---\n\n### Case 4: Any other `MicrosoftAppType` value\n\nDo **not** generate `Connections:ServiceConnection`. Complete all other migration steps, then at the end inform the user:\n\n> \"The `MicrosoftAppType` value `{value}` is not a standard type recognized by this migration. The `Connections:ServiceConnection` block was not changed — additional manual configuration will be required. See: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fmicrosoft-365\u002Fagents-sdk\u002Fmicrosoft-authentication-library-configuration-options\"\n\n---\n\n## Custom BotAdapter\n\nIf the source bot subclasses `BotAdapter`, migrate it to `ChannelAdapter` (`Microsoft.Agents.Builder`).\n\n### Class hierarchy to choose from\n\n| Use when | Subclass |\n|----------|----------|\n| Custom transport \u002F non-Azure channel | `ChannelAdapter` (abstract, minimal pipeline) |\n| Azure Bot Service connectivity with custom behavior | `CloudAdapter` (`Microsoft.Agents.Hosting.AspNetCore`) |\n\nMost custom `BotAdapter` subclasses fall into the **CloudAdapter** case. Prefer that unless the adapter is implementing a completely custom transport.\n\n### API mapping\n\n| Bot Framework `BotAdapter` | Agents SDK |\n|---------------------------|------------|\n| `using Microsoft.Bot.Builder;` | `using Microsoft.Agents.Builder;` |\n| `: BotAdapter` | `: ChannelAdapter` or `: CloudAdapter` |\n| `Activity[]` in `SendActivitiesAsync` | `IActivity[]` in `SendActivitiesAsync` |\n| `BotCallbackHandler` callback delegate | `AgentCallbackHandler` |\n| `abstract UpdateActivityAsync(...)` | `virtual UpdateActivityAsync(...)` (throws `NotImplementedException` if not overridden) |\n| `abstract DeleteActivityAsync(...)` | `virtual DeleteActivityAsync(...)` (throws `NotImplementedException` if not overridden) |\n| `protected RunPipelineAsync(ctx, BotCallbackHandler, ct)` | `protected RunPipelineAsync(ctx, AgentCallbackHandler, ct)` |\n\n### Registration\n\nRegister the custom adapter via the two-type overload of `AddAgent`. Note `AddAgent\u003CTAgent, TAdapter>` requires `TAdapter : CloudAdapter`:\n\n```csharp\nbuilder.AddAgent\u003CMyBot, MyCustomAdapter>();\n```\n\nIf the custom adapter subclasses `ChannelAdapter` directly (not `CloudAdapter`), register manually:\n\n```csharp\nbuilder.AddAgentCore();  \u002F\u002F registers IConnections, IChannelServiceClientFactory\nbuilder.Services.AddSingleton\u003CIChannelAdapter, MyCustomAdapter>();\nbuilder.Services.AddSingleton\u003CIAgentHttpAdapter>(sp => (IAgentHttpAdapter)sp.GetRequiredService\u003CIChannelAdapter>());\nbuilder.Services.AddTransient\u003CIAgent, MyAgent>();\n```\n\n---\n\n## Custom IMiddleware\n\nIf the source bot implements `Microsoft.Bot.Builder.IMiddleware`, retain the class and update its namespaces:\n\n| Old | New |\n|-----|-----|\n| `Microsoft.Bot.Builder.IMiddleware` | `Microsoft.Agents.Builder.IMiddleware` |\n| `Microsoft.Bot.Builder.ITurnContext` | `Microsoft.Agents.Builder.ITurnContext` |\n| `Microsoft.Bot.Builder.NextDelegate` | `Microsoft.Agents.Builder.NextDelegate` |\n\nThe `OnTurnAsync(ITurnContext, NextDelegate, CancellationToken)` signature is unchanged.\n\nRegister custom middleware via a `CloudAdapter` subclass. Delete `AdapterWithErrorHandler.cs` only if it has no custom middleware — if it does, rename it or keep it as a custom adapter:\n\n```csharp\n\u002F\u002F CustomAdapter.cs\nusing Microsoft.Agents.Builder;\nusing Microsoft.Agents.Hosting.AspNetCore;\nusing Microsoft.Agents.Hosting.AspNetCore.BackgroundQueue;\nusing Microsoft.Extensions.Logging;\n\npublic class CustomAdapter : CloudAdapter\n{\n    public CustomAdapter(\n        IChannelServiceClientFactory channelServiceClientFactory,\n        IActivityTaskQueue activityTaskQueue,\n        ILogger\u003CCloudAdapter> logger = null)\n        : base(channelServiceClientFactory, activityTaskQueue, logger: logger)\n    {\n        Use(new MyCustomMiddleware());\n        \u002F\u002F Use(new AnotherMiddleware(...));\n    }\n}\n```\n\nRegister the custom adapter in `Program.cs`:\n\n```csharp\nbuilder.AddAgent\u003CMyBot, CustomAdapter>();\n```\n\n---\n\n## Files to Add\n\nEvery migrated project needs `AspNetExtensions.cs` — the `AddAgentAspNetAuthentication()` extension method is **not in any NuGet package**; it is a sample-provided file. Copy it from the Agents SDK shared samples (https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents-for-net\u002Fblob\u002Fmain\u002Fsrc\u002Fsamples\u002FShared\u002FAspNetExtensions.cs).\n\n---\n\n## Files to Delete\n\nAlways delete these from the source project:\n- `AdapterWithErrorHandler.cs` — delete if it only has `OnTurnError` logic (Agents SDK handles errors internally); **retain and rename** if it contains custom `Use()` middleware registrations (see Custom IMiddleware section above)\n- `BotController.cs` (unless it has custom logic — see preservation note above)\n- Any `Startup.cs` (merge into `Program.cs`)\n\n---\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Renamed the bot class or created a new class | Restore the original class name — renaming breaks git history |\n| Changed more than needed (refactored, restructured) | Revert — only change what is required to compile and run |\n| Called `AddAgentApplicationOptions()` for ActivityHandler bot | Remove — only for AgentApplication |\n| Used `MapAgentApplicationEndpoints()` for ActivityHandler bot | Use `MapAgentEndpoints()` — former only works for AgentApplication |\n| Left `services.AddTransient\u003CIBot, MyBot>()` | Replace with `builder.AddAgent\u003CMyBot>()` |\n| Left `services.AddSingleton\u003CIBotFrameworkHttpAdapter, AdapterWithErrorHandler>()` | Delete — handled by `AddAgent\u003C>()` |\n| Left `ConfigurationBotFrameworkAuthentication` | Delete — use `AddAgentAspNetAuthentication()` |\n| Missing `IStorage` registration | Add `builder.Services.AddSingleton\u003CIStorage, MemoryStorage>();` — always required, not just for dialog bots |\n| Left old Bot Framework appsettings (`MicrosoftAppId` etc.) | Replace with `Connections` + `TokenValidation` — shape depends on `MicrosoftAppType` (see appsettings.json Changes section) |\n| Used the wrong `Connections:ServiceConnection` shape | Check `MicrosoftAppType`: `SingleTenant`→ClientSecret+tenant authority; `UserAssignedMSI`→UserManagedIdentity (no secret); `MultiTenant`\u002Fmissing→ClientSecret+botframework.com authority |\n| Left `BotAdapter` as base class of custom adapter | Change to `ChannelAdapter` or `CloudAdapter`; update `Activity[]` → `IActivity[]`, `BotCallbackHandler` → `AgentCallbackHandler` |\n| Deleted `AdapterWithErrorHandler.cs` that contained custom `Use()` calls | Retain it (renamed if needed) as a `CloudAdapter` subclass; register via `builder.AddAgent\u003CTBot, TAdapter>()` |\n| Left `Microsoft.Bot.Builder.IMiddleware` namespace in custom middleware | Update to `Microsoft.Agents.Builder.IMiddleware` |\n| Attempted to migrate code using a deprecated package (Luis, QnA, Adaptive, etc.) | Stop — no Agents SDK equivalent exists. Remove the package reference, leave the code in place, and flag build errors to the customer |\n| Forgot to add `AspNetExtensions.cs` | Copy from any Agents SDK sample — `AddAgentAspNetAuthentication` is not in any NuGet package |\n| Left `conversationState.DeleteAsync(...)` in adapter | Rename to `conversationState.DeleteStateAsync(...)` — method was renamed in Agents SDK |\n| New `Program.cs` fails to compile (WebApplication, AddSingleton, IsDevelopment not found) | BF projects don't have `\u003CImplicitUsings>enable\u003C\u002FImplicitUsings>` — add explicit `using` for `Microsoft.AspNetCore.Builder`, `Microsoft.Extensions.DependencyInjection`, `Microsoft.Extensions.Hosting` |\n\n---\n\n## After Migration: Optional AgentApplication Upgrade\n\nOnce the compat-layer migration is complete and the build is clean, ask the user:\n\n> \"The bot is now running on Agents SDK using the ActivityHandler compat layer. Would you like to also migrate to the modern `AgentApplication` routing pattern? This involves converting the bot class to subclass `AgentApplication` and updating Program.cs — it is handled by the `agents-sdk-dotnet-activityhandler-migration` skill.\"\n\nIf yes, invoke `agents-sdk-dotnet-activityhandler-migration`.\nIf no, migration is complete.\n",{"name":5,"description":7},"main","8171bc7e0ca3b8defd578a6bb317367c2901983f","agent-plugins\u002Fagents-for-net\u002Fskills\u002Fbf-to-agents-sdk-dotnet-migration",346,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents","https:\u002F\u002Faka.ms\u002Fagentsdkdocs","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 08:54:12",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add microsoft\u002FAgents --skill bf-to-agents-sdk-dotnet-migration",{"tool":48,"command":49},"bunx","bunx skills add microsoft\u002FAgents --skill bf-to-agents-sdk-dotnet-migration",{"tool":51,"command":52},"pnpm","pnpm dlx skills add microsoft\u002FAgents --skill bf-to-agents-sdk-dotnet-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-net\u002Fskills\u002Fbf-to-agents-sdk-dotnet-migration\u002FSKILL.md",true,[],[57,75,94,109,121,130],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":27},"01M6PJCYCYJQDX318SQN3EBF0E","sync-teams-samples-to-agents-sdk","CI instructions for a bounded Teams SDK to Agents SDK sample synchronization using the selected language profile.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fautomation\u002Fteams-sample-sync\u002Fskills\u002Fsync-teams-samples-to-agents-sdk\u002FSKILL.md",[],[19,20,64,65,66,67,68,69,70,71,72,73,74],"sync","teams","sync teams samples to agents sdk","ci","synchronization","instructions","profile","language","sample","for","bounded",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":27},"01M6PJCFNGCX555YERYQ459JFE","teams-sdk-to-agents-sdk-typescript-migration","Migrate a JavaScript or TypeScript application using the Microsoft Teams SDK App runtime to Microsoft 365 Agents SDK while preserving its Teams behaviors. Use for Teams SDK migrations, including automated sample synchronization; use the separate Bot Framework migration skill for botbuilder applications.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-js\u002Fskills\u002Fteams-sdk-to-agents-sdk-typescript-migration\u002FSKILL.md",[],[65,82,19,20,83,84,85,86,87,88,89,72,90,91,68,92,73,24,93,9],"typescript","agents sdk typescript","migration","teams sdk to agents sdk typescript migration","microsoft teams","applications","app","runtime","migrations","use","migrate","javascript",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":27},"01M69B8QV24JVPXH25EH77X0SZ","teams-app-manifest","Create or audit a Microsoft Teams app manifest for an existing Microsoft 365 Agents SDK application by mapping declared intent and source-code evidence to released manifest capabilities. Use when manifest.json is missing, incomplete, or must be checked against implemented Teams features. Does not configure Microsoft Entra, Azure Bot, Developer Portal, or deployment unless separately requested.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-sdk-common\u002Fskills\u002Fteams-app-manifest\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[65,106,20,24,19,9,107,108],"teams app manifest","azure","deployment",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":27},"01M69B8MN62NBY93YTJAQG2Y81","agents-sdk-provision","Use when provisioning Azure resources for a Microsoft Agents SDK application — including creating an Azure Bot Service resource, setting up Entra app registrations, configuring identity credentials (UserManagedIdentity, FederatedCredentials, or ClientSecret), adding a Teams channel, running Bicep deployments for SSO, or setting up OAuth user sign-in connections via az CLI. Trigger even if the user doesn't say \"provision\" — use on requests like \"set up my bot on Azure\", \"deploy my bot\", \"configure Azure for my bot\", or \"get Teams SSO working.\" Applies to all languages (dotnet, Node.js, Python).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-sdk-common\u002Fskills\u002Fagents-sdk-provision\u002FSKILL.md",[],[19,20,116,24,117,118,9,21,119,120,107,65],"agents sdk provision","cli","python","identity","deploy",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":27},"01M69B8HFZ45NQGWQQD483TWPB","agents-sdk-to-prod","Assess, create, harden, deploy, or review production readiness of Python Microsoft 365 Agents SDK agents and their direct hosting\u002Foperations files. Use only for Agents SDK scenarios, not unrelated application hardening.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-python\u002Fskills\u002Fagents-sdk-to-prod\u002FSKILL.md",[],[128,20,19,9,118,129,120],"agents sdk to prod","review",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":144,"publishedAt":27},"01M69B8ENJGC9NPQBZAYAN4706","agents-sdk-python-otel","Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in Python. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed tracing, custom tracers or meters, span sampling, or observing microsoft_agents SDK signals.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FAgents\u002Fblob\u002Fmain\u002Fagent-plugins\u002Fagents-for-python\u002Fskills\u002Fagents-sdk-python-otel\u002FSKILL.md",[136,141],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":142,"categoryName":143,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000033","数据分析师",[19,118,145,20,146,147,107,148,9,149,150,151,152],"otel","agents sdk python otel","aspire","telemetry","dashboard","distributed","aspire dashboard","monitor"]