The Microsoft Bot Framework played an important role in the growth of conversational applications, especially for developers building bots for Microsoft Teams, websites, enterprise workflows, and other channels. In 2026, however, it should be viewed primarily as a legacy technology for existing solutions rather than the default starting point for a new Microsoft conversational-agent project.
Microsoft has archived the Bot Framework SDK and Bot Framework Emulator. Support tickets for the Bot Framework SDK stopped being serviced after December 31, 2025. Microsoft now directs developers who need a modern agent foundation toward the Microsoft 365 Agents SDK, with migration guidance available for existing Bot Framework applications.
Older Bot Framework applications do not automatically stop functioning simply because the SDK has been archived. The important change is that the SDK itself is no longer being actively updated or maintained. That affects how teams should think about long-term maintenance, security, compatibility, new feature development, and technical support.
The Bot Framework SDK is archived: New feature development and routine maintenance of the SDK have ended.
The Bot Framework Emulator is also archived: Teams relying on the emulator should factor its legacy status into their development and testing plans.
Official SDK support has ended: Microsoft states that Bot Framework SDK support tickets are no longer serviced after December 31, 2025.
Migration is the strategic path: Microsoft recommends evaluating the Microsoft 365 Agents SDK for new agent development and for modernization of suitable existing bots.
Migration is not always a simple package replacement: Existing applications may depend on Bot Framework patterns or capabilities that need redesign or an alternative implementation.
Understanding the original architecture is still useful for teams maintaining an established deployment. The Bot Framework combined SDKs, Azure-hosted resources, conversational state, dialogs, channel connectivity, and integrations with other Microsoft services to create bots that could receive user messages, execute application logic, and return structured responses.
These concepts remain valuable, but developers should avoid treating old Bot Framework tutorials as automatically current. Product names, SDK packages, authentication patterns, channel requirements, and recommended Microsoft architectures can change.
Microsoft positions the Microsoft 365 Agents SDK as a current option for developers who want to build agents while choosing their own AI services, orchestration approach, and knowledge sources. Microsoft documents language support for C#, JavaScript, and Python.
The move from a traditional bot framework toward an agents-oriented SDK also reflects a broader change in conversational software. Modern agents may combine deterministic application logic with large language models, retrieval, external tools, business data, and human escalation rather than depending entirely on intent-and-dialog structures.
For an actively used production bot, the answer depends on business value and technical risk. A stable bot does not necessarily require an emergency rewrite, but relying indefinitely on an archived SDK can increase maintenance risk. A planned modernization assessment is usually more sensible than waiting for an operating-system, dependency, security, or channel change to force the issue.
Inventory the application: Document SDK versions, dependencies, channels, integrations, storage, authentication, and custom middleware.
Identify business-critical flows: Separate essential customer or employee workflows from rarely used features.
Review Microsoft's migration guidance: Compare the current Agents SDK architecture with the application's actual requirements.
Prototype before replacing: Rebuild a representative workflow first and validate functionality, latency, security, and channel behavior.
Plan for unsupported differences: Some legacy functionality may require redesign rather than direct migration.
Migrate in controlled stages: Use testing, observability, and rollback procedures instead of performing a blind production cutover.
For a new Microsoft-centered conversational project in 2026, starting directly with the archived Bot Framework SDK would generally create unnecessary technical debt. A better approach is to evaluate Microsoft's currently supported agent tooling and then select an architecture based on the application's actual needs.
That evaluation should include more than the chatbot interface. Consider where the agent will obtain trusted information, what actions it is allowed to perform, how identities and permissions are enforced, how potentially incorrect generative responses are controlled, and when a conversation should be transferred to a person.
The shift toward generative AI does not make structured conversational design obsolete. Deterministic workflows remain valuable when a user is changing an account setting, submitting a form, making a purchase, requesting support, or performing another action where predictable behavior matters.
For many production systems, the strongest design is a hybrid: generative capabilities for flexible language and knowledge-oriented interaction, combined with validated business logic for transactions and high-consequence actions.
Modern conversational agents may have access to business data and tools, so developers should design explicit permission boundaries. Protect secrets, validate user identity, restrict tool access, log important actions, minimize sensitive-data exposure, and test how the agent behaves when instructions are ambiguous or malicious.
Generative AI also introduces a distinction between a fluent response and a verified answer. For customer-facing or operational workflows, use authoritative data sources and deterministic checks where accuracy is important.
The Microsoft Bot Framework remains historically important and may continue to power existing applications, but its role has changed. In 2026, the SDK and Emulator are archived, official SDK support has ended, and Microsoft's forward-looking guidance points developers toward the Microsoft 365 Agents SDK.
If you maintain a Bot Framework application, treat modernization as a planned engineering project: understand what you already have, identify unsupported differences, prototype the new architecture, and migrate when the operational case is clear. If you are starting from scratch, evaluate Microsoft's current agent tooling rather than basing a new production system on an archived SDK.