microsoft/Agents.

agents-sdk-dotnet

>

agents-sdk-dotnet-activityhandler-migration

Use when migrating a Microsoft 365 Agents SDK agent that uses ActivityHandler or TeamsActivityHandler to AgentApplication. This is ONLY for DotNet projects that uses `Microsoft.Agents.*` packages. Triggered by Agents SDK bots that subclass ActivityHandler or TeamsActivityHandler that need to be modernized to AgentApplication routing.

agents-sdk-dotnet-debugging

>

agents-sdk-dotnet-otel

>

agents-sdk-provision

>

agents-sdk-python-otel

>

agents-sdk-typescript

>

agents-sdk-typescript-debugging

>

agents-sdk-typescript-otel

>

bf-to-agents-sdk-dotnet-migration

>

bf-to-agents-sdk-typescript-migration

Assess and migrate JavaScript or TypeScript bots from BotBuilder/Bot Framework SDK to Microsoft 365 Agents SDK with AgentApplication. Use to produce a migration report and plan before editing code, map BotBuilder packages and APIs, identify unsupported features, and implement only the supported plan items selected by the user.

sync-teams-dotnet-samples-to-agents-sdk

CI instructions for a bounded Teams SDK .NET to Agents SDK sample synchronization.

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.

teams-sdk-to-agents-sdk-dotnet-migration

Use when migrating a customer's Teams SDK (teams.net) bot to the Microsoft 365 Agents SDK in .NET. Triggered by projects that depend on Microsoft.Teams.Plugins.AspNetCore, Microsoft.Teams.Apps, or Microsoft.Teams.Api and call builder.AddTeams() / app.UseTeams().