On December 17, 2025, Microsoft published an announcement that ended twenty-five years of speculation about BizTalk Server's future. The statement was direct and unambiguous. BizTalk Server 2020 will be the final version of BizTalk Server. For the thousands of organisations worldwide running mission-critical integration workloads on BizTalk, this announcement transformed strategic uncertainty into a concrete planning timeline.

Microsoft positioned this announcement carefully. They opened by acknowledging that for more than twenty-five years, BizTalk Server has supported mission-critical integration workloads for organisations around the world. From business process automation and B2B messaging to connectivity across industries such as financial services, healthcare, manufacturing, and government, BizTalk Server has played a foundational role in enterprise integration strategies. This wasn't an abrupt discontinuation announcement. It was a lifecycle update with respect for the platform's history and the customers who depend on it.

The announcement's purpose is clear. Microsoft wants to help customers plan confidently for the future by sharing an update to the BizTalk Server product lifecycle and long-term support timelines. They explicitly state that this announcement does not change existing support commitments. Customers can continue to rely on BizTalk Server for many years ahead, with a clear and predictable runway to plan modernization at a pace that aligns with their business and regulatory needs.

For enterprise architects responsible for integration strategy, this clarity eliminates a significant planning constraint. You now know exactly how long BizTalk Server will receive support, what happens afterward, and what Microsoft recommends as the modernization path. The question shifts from whether to migrate to when and how. Let's examine what Microsoft actually announced, what the timeline means in practice, and what this signals about enterprise integration architecture over the next decade.

Understanding the Support Timeline Microsoft Published

Microsoft provided a detailed lifecycle table that removes ambiguity about support commitments. The table shows three distinct phases with specific end dates and support inclusions for each phase.
Mainstream support for BizTalk Server 2020 continues through April 11, 2028. During this phase, customers receive three key support elements. First, security updates that address vulnerabilities and ensure compliance with security standards. Second, non-security updates that fix bugs and improve functionality. Third, Customer Service and Support assistance through Microsoft's CSS organisation. This represents standard product support that BizTalk customers are accustomed to. Nothing changes immediately for organisations running BizTalk Server 2020 in production today.

Extended support becomes available from April 12, 2028 through April 9, 2030. This phase continues to provide CSS support and security updates. The critical distinction during extended support involves non-security updates. Microsoft will offer paid extended support for customers requiring hotfixes for non-security updates during this period. The CSS organisation will continue providing their typical support activities, but fixes for non-security issues will require payment beyond standard support agreements.
The end of support arrives on April 10, 2030. After this date, Microsoft will no longer provide updates or support of any kind. Security patches cease. Technical assistance ends. Compliance validation stops. Workloads will continue running if organisations choose to operate them, but they do so without vendor support, security patches, or any Microsoft assistance when issues arise. For regulated industries where vendor support and timely security updates are compliance requirements, this represents a hard deadline that cannot be extended through payment or negotiation.

The timeline provides organisations with more than four years from announcement to end of support. This represents Microsoft's recognition that BizTalk systems support highly customized and mission-critical business operations. Modernization requires time, planning, and precision. The runway Microsoft provides acknowledges this reality rather than forcing artificial urgency.

What This Means for Organisations Running Earlier BizTalk Versions

Microsoft's guidance becomes more direct when addressing organisations still running BizTalk Server 2016 or earlier versions. The announcement explicitly states that those versions are already out of mainstream support. The recommendation is clear and unambiguous. Microsoft strongly encourages moving directly to Logic Apps rather than upgrading to BizTalk Server 2020.

The logic behind this recommendation is straightforward. If your organisation is already running BizTalk on versions that have exited mainstream support, you're operating without non-security updates and facing the same modernization decision that BizTalk Server 2020 customers will face in several years. Upgrading from BizTalk 2016 to BizTalk 2020 requires significant effort including testing, redeployment, and validation. That effort delivers a few more years of supported runway, but ultimately delays rather than solves the modernization challenge.

Microsoft's position is that if you're facing a major migration effort anyway, direct migration to the strategic platform makes more business sense than intermediate migration to a platform with known end-of-life. The effort required to upgrade from BizTalk 2016 to 2020 could instead be invested in migrating to Logic Apps, which positions the organisation for long-term integration capabilities rather than extending legacy platform life by several years.

This creates a decision point for BizTalk Server 2016 customers. Some organisations may conclude that upgrading to BizTalk 2020 provides valuable runway that aligns better with current organisational capacity and priorities. Others may view the 2016 end-of-support as the catalyst for immediate modernization rather than delaying several more years. Neither choice is inherently wrong. What matters is making the decision deliberately based on organisational context rather than defaulting to status quo because change is difficult.

The Successor Platform: Azure Logic Apps as Official Direction

Microsoft doesn't simply announce BizTalk's end-of-life and leave customers to determine next steps independently. They explicitly position Azure Logic Apps as the successor to BizTalk Server. The announcement states clearly that Azure Logic Apps, part of Azure Integration Services, is the modern integration platform that carries forward what customers value in BizTalk while unlocking new innovation, scale, and intelligence.

The announcement highlights specific capabilities designed to address migration concerns. Logic Apps provides more than fourteen hundred out-of-box connectors supporting enterprise systems, SaaS applications, legacy platforms, and mainframe systems. This connector ecosystem addresses the reality that enterprise integration spans diverse technology landscapes. Organisations don't integrate only with modern cloud applications. They integrate with systems spanning decades of technology evolution, and the integration platform must support that reality.

Microsoft emphasizes artifact reuse capabilities that preserve BizTalk investments. Organisations can reuse existing BizTalk maps, schemas, rules, and custom code to accelerate modernization while preserving prior investments. This includes support for B2B and EDI transactions, which are critical for organisations in industries like manufacturing, logistics, and retail where electronic data interchange with partners remains fundamental to business operations. Healthcare transactions that rely on HL7 and other healthcare-specific standards are also explicitly mentioned as supported patterns.

The platform delivers elastic scalability without requiring organisations to manage infrastructure. This represents a fundamental operational shift from BizTalk's on-premises model where organisations provision, maintain, and scale infrastructure based on anticipated capacity needs. Logic Apps scales automatically based on actual demand, eliminating the need for capacity planning exercises and infrastructure refresh cycles.

Enterprise-grade security and compliance certifications address governance concerns that enterprises face when evaluating cloud platforms. Built-in cost efficiency comes from consumption-based pricing where organisations pay for actual usage rather than provisioned capacity. Modern DevOps tooling including Visual Studio Code support and infrastructure-as-code capabilities through ARM templates and Bicep enable development and deployment practices that BizTalk's architecture couldn't support.
Perhaps most significantly, Microsoft positions Logic Apps as enabling agentic business processes. The announcement specifically mentions AI-driven routing, predictive insights, and context-aware automation without requiring organisations to redesign existing integrations. This represents the forward-looking aspect of the modernization path. Migrating to Logic Apps isn't just replacing BizTalk. It's positioning integration architecture for AI capabilities that will increasingly define competitive advantage in enterprise operations.

The Hybrid Deployment Reality Microsoft Acknowledges

One of the most significant aspects of Microsoft's announcement involves acknowledgment that not all organisations can or will move integration workloads to public cloud. Logic Apps supports multiple deployment models that accommodate diverse organisational constraints.
The announcement explicitly states that Logic Apps adapts to business and regulatory needs through multiple deployment options. Organisations can run Logic Apps fully managed in Azure, which is the deployment model Microsoft promotes most heavily and where platform capabilities reach their fullest expression. This model provides automatic scaling, managed infrastructure, and consumption-based economics.

For organisations with requirements that prevent full cloud deployment, Logic Apps supports hybrid deployment via Arc-enabled Kubernetes. This allows Logic Apps to run on infrastructure that organisations control, whether on-premises, in private cloud, or at edge locations. The runtime environment remains consistent with Azure-hosted Logic Apps, meaning workflows developed and tested in Azure deploy to Arc-enabled infrastructure without modification.

Microsoft is also evaluating Logic Apps for air-gapped environments. These scenarios, common in government, defense, and critical infrastructure sectors, involve complete disconnection from external networks for security reasons. While not generally available today, Microsoft's explicit mention that they're evaluating these scenarios signals recognition that pure cloud deployment doesn't serve all enterprise requirements.

The hybrid deployment capability addresses one of the most common objections to cloud integration platforms. Organisations with data sovereignty requirements, regulatory constraints preventing cloud deployment, or legacy systems that cannot move to cloud can still modernize integration architecture. They gain access to modern development capabilities, contemporary integration patterns, and AI-enabled features while maintaining infrastructure control where business or regulatory requirements demand it.

Host Integration Server: Mainframe Connectivity Continuity

Microsoft's announcement includes important clarification about mainframe and midrange connectivity. Host Integration Server has long provided essential connectivity for organisations with mainframe and midrange systems. Rather than ending HIS support alongside BizTalk Server, Microsoft is releasing Host Integration Server 2028 as a standalone product with its own lifecycle, decoupled from BizTalk Server.
This decoupling matters significantly for organisations with mainframe dependencies. Many BizTalk installations include HIS for connectivity to IBM mainframes or AS/400 midrange platforms. The typical integration pattern involves BizTalk orchestrations calling HIS to interact with mainframe applications, submit batch jobs, or access mainframe data. With HIS receiving its own lifecycle separate from BizTalk, organisations can maintain mainframe connectivity through HIS while migrating orchestration logic to Logic Apps.

Microsoft also acknowledges that mainframe modernization often means integrating with mainframes differently rather than eliminating mainframe systems entirely. The announcement notes that Logic Apps provides connectors for mainframe and midrange systems, and Microsoft is keen on adding more connectors in this space. They invite customers to communicate HIS plans and specific features needed for mainframe and midrange integration from Logic Apps through a dedicated feedback link.

The combination of HIS 2028 with extended lifecycle and expanding Logic Apps mainframe connectivity provides multiple paths forward for organisations with mainframe dependencies. They aren't forced into single approach. They can continue using HIS for direct mainframe connectivity. They can leverage Logic Apps mainframe connectors for specific scenarios. They can use both in combination depending on integration requirements and organisational preferences. The flexibility acknowledges that mainframe integration remains reality for many enterprises and the integration platform must accommodate that reality.

Microsoft's Commitment to Supporting Customer Transition

The announcement emphasizes that Microsoft remains fully committed to supporting customers through this transition. They explicitly recognize that BizTalk systems support highly customized and mission-critical business operations. Modernization requires time, planning, and precision. This isn't lip service. It's acknowledgment of operational reality that shapes how Microsoft is approaching this transition.

Microsoft outlines specific support commitments they're making available. They provide proven guidance and recommended design patterns drawn from organisations that have already completed BizTalk to Logic Apps migrations. A growing ecosystem of tooling supports artifact reuse, allowing organisations to leverage BizTalk investments rather than starting from zero. Unified Support engagements offer deep migration assistance for organisations facing complex modernization scenarios.

A strong partner ecosystem specializing in BizTalk modernization provides additional resources. Microsoft partners have developed migration methodologies, assessment tools, and specialized expertise in particular industry domains or BizTalk capabilities. Organisations can engage partners for migration planning, execution assistance, or full migration outsourcing depending on internal capability and capacity.

Microsoft also mentions potential incentive programs to help facilitate migration for eligible customers, with details forthcoming. While specifics aren't provided in the announcement, this signals Microsoft's recognition that migration investment represents significant undertaking and they're exploring ways to reduce financial barriers for customers making this transition.

The announcement emphasizes that customers can take a phased approach, starting with new workloads while incrementally modernizing existing BizTalk deployments. This acknowledges that simultaneous cutover of all integrations isn't realistic or advisable for most organisations. Phased migration spreads effort and risk across time while allowing organisations to build capability and confidence through progressive migration waves.

The Migration Resources Microsoft Makes Available Today

Microsoft doesn't just announce BizTalk's future and leave customers to determine migration approach independently. They provide specific resources available immediately for organisations beginning modernization planning.

The migration overview is available at a dedicated URL providing high-level understanding of migration approaches and considerations. Best practices documentation addresses common scenarios and challenges that organisations encounter during migration. These best practices reflect accumulated learning from organisations that have already completed BizTalk to Logic Apps migrations.

A video series walks through migration processes with concrete examples and demonstrations. Video format provides accessible learning for teams beginning to understand what Logic Apps migration involves. The Reactor session on modernizing BizTalk and accelerating migration with Logic Apps offers deeper technical content from Microsoft engineers familiar with migration patterns and challenges.

• Overview: https://aka.ms/btmig
• Best practices: https://aka.ms/BizTalkServerMigrationResources
• Video series: https://aka.ms/btmigvideo
• Feature request survey: https://aka.ms/logicappsneeds
• Reactor session: Modernizing BizTalk: Accelerate Migration with Logic Apps – YouTube

Microsoft invites customers to submit feature requests through a dedicated survey. This signals ongoing investment in Logic Apps capabilities based on customer migration needs. If BizTalk capabilities that organisations depend on don't yet exist in Logic Apps, Microsoft wants to know about them. The survey provides channel for customers to influence Logic Apps roadmap based on real migration requirements.
Microsoft encourages customers to engage their Microsoft account teams early to assess readiness, identify modernization opportunities, and explore assistance programs. Account teams can connect customers with technical resources, migration specialists, and program information that might not be publicly documented. Early engagement allows Microsoft to understand customer-specific challenges and provide targeted assistance.

What the Announcement Signals About Integration Platform Direction

Beyond the specific BizTalk lifecycle details, this announcement signals Microsoft's broader integration platform strategy for the next decade. Cloud-native architecture represents the foundation rather than optional deployment model. API-first design patterns position integration for consumption by diverse clients including AI agents. Event-driven capabilities support real-time integration patterns that batch-oriented architectures cannot deliver.

AI-enabled automation capabilities will increasingly differentiate integration platforms. Microsoft's mention of agentic business processes, AI-driven routing, and context-aware automation signals where integration platform investment is headed. Organisations building integration architecture today need to consider not just current requirements but how AI adoption will change integration patterns over the next five years.

Hybrid deployment flexibility addresses real-world enterprise constraints rather than forcing pure cloud adoption. Microsoft's explicit support for Arc-enabled Kubernetes deployment and evaluation of air-gapped scenarios acknowledges that enterprises operate under diverse constraints. The integration platform must accommodate that diversity rather than dictating single deployment model.
The emphasis on artifact reuse and phased migration reflects understanding of how enterprises actually operate. Organisations don't shut down production systems for extended periods to complete major technology transitions. They migrate incrementally while maintaining business operations. The integration platform and migration approach must support this operational reality.

Conclusion

Microsoft's announcement that BizTalk Server 2020 is the final version eliminates strategic uncertainty about the platform's future. Organisations now have a clear timeline with mainstream support through April 2028, extended support available through April 2030, and end of support on April 10, 2030. Azure Logic Apps is explicitly positioned as the successor platform with specific capabilities designed to facilitate migration.

The announcement provides detailed support commitments, migration resources, and acknowledgment of the complexity involved in modernizing mission-critical integration systems. Microsoft isn't forcing artificial urgency or abandoning customers. They're providing a clear runway and committed support for organisations navigating this transition over the next several years.

For enterprise architects responsible for integration strategy, this announcement transforms the conversation from whether to migrate to how and when. The platform direction is set. The support timeline is published. The migration resources exist. What remains is organisational execution informed by business priorities, regulatory requirements, and operational realities.

The organisations that navigate this transition successfully will be those that start planning now, engage with Microsoft resources early, and approach migration as a phased journey rather than one-time cutover event. The timeline is clear. The path is defined. The next move is yours.

BizTalk Server 2020, BizTalk end of life, BizTalk migration, Azure Logic Apps, enterprise integration modernization, BizTalk lifecycle, integration platform migration, BizTalk to Logic Apps, April 2030 deadline, BizTalk support timeline, hybrid integration, mainframe integration, Host Integration Server, Arc-enabled Kubernetes, B2B EDI integration, BizTalk artifact reuse