The Platforms We Support: Microsoft BizTalk Server and Azure Logic Apps

integration-platform-success-biztal-logic-apps-blog-1260x630

This is the second article in our Integration Platform Success series. The articles will cover the benefits, use cases, and sometimes challenges of the platforms we support.

The series will share tips to help organizations using or considering these platforms get the most ROI from their investments. Today’s article focuses on Microsoft BizTalk Server and Azure Logic Apps.

Future articles will cover integration solutions from TrueCommerce, SPS Commerce, Boomi, IBM, Cleo, SEEBURGER, 1 EDI Source, OpenText, as well as custom-developed solutions. At the end of the article, you can find a link to the first blog in the series.

Now, on to BizTalk.

For years, organizations have relied on Microsoft BizTalk Server as the backbone of their EDI and integration environments. And no wonder. BizTalk excels at keeping costs down and production up by orchestrating supply chains and operations. But all good things eventually come to an end.

BizTalk Server 2020 will be the final version of BizTalk, and while it remains supported for several years, its lifecycle milestones are now clearly defined. Mainstream support ends in April 2028, followed by extended support through April 2030.

For organizations currently running BizTalk Server, the migration conversation is shifting from “should we do this” to “what needs to happen to ensure we do this safely, and when do we need to start?”

In short, with the sunset for BizTalk 2020 on the horizon, the time has arrived for users making the move to Azure Logic Apps to plan their journey.

The practical migration path from BizTalk 2020 to Azure Logic Apps is a phased approach and is the safest strategy for most operations teams. Below, we’ll discuss how you can begin preparing for migration without disrupting business-critical integrations.

biztalk-excerpt.1-800x215

And we want to be clear that in the interim, there are proven strategies to optimize your existing BizTalk environment and reduce the demand on support resources.

Lastly, toward the end of this article, we address why Microsoft is advocating Logic Apps as the natural successor to BizTalk.

What Do BizTalk Lifecycle Milestones Mean for Integration Teams?

Microsoft’s lifecycle announcement should not inspire panic. Many BizTalk environments will continue operating successfully for several years. However, lifecycle milestones inevitably influence operational planning in several ways.

First, support timelines affect upgrade and security planning. As products approach the end of mainstream support, organizations may find fewer updates, fewer enhancements, and increasing pressure to maintain environments on aging infrastructure.

Second, lifecycle changes may constrain staffing and expertise availability. As the industry gradually shifts toward cloud integration, recruiting or retaining engineers with deep BizTalk operational experience could become more competitive.

Finally, lifecycle transitions tend to coincide with other major initiatives. These include ERP upgrades, digital transformation programs, supply chain modernization, or new partner onboarding efforts.

biztalk-exceprt.2-800x215

When these occur, organizations often evaluate whether continuing to invest in BizTalk makes long-term sense. Often, timing considerations drive such decisions.

For example, during a recent project, we advised a customer who was on the fence about upgrading from BizTalk 2016 to 2020 that doing so was in their best interest.

They saw the logic (pardon the pun) in not running a version of BizTalk that would become unsupported before they could fully implement their migration to Logic Apps.

For most organizations, the play at this stage of the BizTalk lifecycle isn’t to replace BizTalk overnight. Instead, it makes more sense to develop a realistic and responsible modernization roadmap, one that minimizes risk and operational disruption.

The Practical Migration Path from BizTalk Server to Azure Logic Apps

BizTalk migration doesn’t require a full “rip and replace.” In fact, Microsoft recommends a phased migration approach.

Such an approach gives organizations the breathing room to gradually transition workloads to Azure Logic Apps while BizTalk continues operating during the transition period. Migrating in phases delivers other benefits as well.

Most importantly, it significantly reduces risk of operational disruption. Just as valuable, the approach lets teams build experience with the new platform before moving their most complex integrations.

Why is Phased Migration Safer Than a “Big Bang” Replacement?

The idea of a “big bang” or direct cutover migration can appear attractive in theory. In practice, it’s usually unwise.

That’s because of the maze of discrete yet intertwined workflows that make up the typical BizTalk integration environment, such as:

Hundreds of partner agreements
Dozens to hundreds of maps and transformations
Complex orchestration logic
Multiple application dependencies
Certificates, security rules, and partner communication protocols

Trying to replace all of these elements simultaneously creates the perfect scenario for unexpected disruptions. In contrast, phased migration allows teams to:

Validate architecture and governance decisions early
Develop operational experience with Logic Apps
Establish monitoring and alerting standards
Confirm partner testing procedures
Reduce risk by migrating lower-complexity integrations first

A well-planned migration journey builds stakeholder confidence and preserves operational stability along the way. What does that look like?

Step 1: Inventory and Discovery Your Existing Environment

Your BizTalk environment has likely evolved over many years, and across multiple teams or implementation partners. Also likely is incomplete or outdated documentation. This means you’ll want to kick off your migration plan with a discovery phase to identify and capture:

Active integrations and workflows
Partner agreements and EDI relationships
Message schemas, maps, and transformations
Custom pipelines or assemblies
Certificates and security configurations
System dependencies and upstream/downstream applications
Operational SLAs and business impact

Step 2: Defining the Target Architecture in Azure

Azure Logic Apps is often deployed alongside other Azure services that handle messaging, security, and API management. So you will need to define how Azure Logic Apps will fit within your broader integration architecture.

Specifically this includes defining:

Integration workflow patterns
Monitoring and logging strategy
Identity and security management
Network connectivity between cloud and on-premises systems
Governance and deployment processes
Cost management and usage monitoring

Establishing this architecture early ensures that migrated integrations follow consistent standards and avoid creating fragmented workflows across the environment.

biztalk-exceprt.3-800x215

This process helps the team untangle which integrations are mission-critical, which are relatively simple, and which may no longer be necessary. Conducting a thorough inventory is essential to provide the foundation for planning migration waves.

Step 3: Prioritizing Integrations for Migration Waves

The beauty of migration waves is how they group integrations into manageable sets. From here, they can be migrated sequentially.

Starting with lower complexity integrations will allow your team to gain experience with the new platform while minimizing operational risk.

For example, they might begin with:

Simple file-based integrations
Internal application integrations
Low-volume partner exchanges

As their confidence grows, subsequent waves can include:

Higher-volume integrations
More complex orchestration logic
Large partner ecosystems

This wave-based approach enables your team to protect operations while they are finding their migration process groove.

Step 4: Build, Test, and Validate Integrations in Logic Apps

For each migration wave, you want to recreate or redesign integrations within Azure Logic Apps.

During this stage, teams typically perform several key activities:

Implement workflow logic in Logic Apps
Recreate schemas and message transformations
Configure connectors and partner communication protocols
Establish monitoring and alerting rules
Perform functional testing
Conduct partner validation testing where required

We always recommend organizations temporarily run parallel environments, where BizTalk and Logic Apps process the same transactions during testing.

Parallel validation significantly reduces the risk of production disruptions during cutover and helps ensure a smooth go-live.

Step 5: Controlled Cutover and Gradual Decommissioning

As the team completes testing for the integrations in each migration wave, they can transition production traffic from BizTalk to Logic Apps.

Cutover punch lists typically include:

Final partner communication and validation
Operational readiness checks
Monitoring of transaction flows during initial production runs
Clear rollback procedures in case unexpected issues arise

After successfully migrating, the BizTalk components supporting those integrations can be gradually retired. Additional migration waves continue until the entire BizTalk environment can be safely decommissioned.

biztalk-exceprt.4-800x215

Why is Azure Logic Apps the Strategic Direction for Microsoft?

While we’ve been focusing on BizTalk migration planning, we should touch on why Microsoft is positioning Azure Logic Apps as the future of integration workloads.

Logic Apps is designed as a cloud-native integration platform built within Microsoft Azure. This enables organizations to build automated workflows that connect applications, data, and services across cloud and on-premises environments.

Several characteristics make it attractive for modern integration architectures.

Cloud-Native Integration and Automation

As a cloud-native integration platform, Logic Apps allows integration workflows to run as managed services within Azure. Traditional server infrastructure comes with the cost and burden of maintaining servers, patching operating systems, and struggling to scale infrastructure.

With Logic Apps, integration teams can focus on priorities that add long-term value like workflow design and partner onboarding, not platform maintenance.

Extensive Connectivity Across Applications and Services

Azure Logic Apps includes a large ecosystem of connectors designed to integrate with Microsoft services, enterprise systems, and many popular SaaS applications. Its connector-driven model lets teams more rapidly connect systems.

Support for B2B and EDI Workflows

Logic Apps also includes capabilities for handling common B2B protocols such as AS2, X12, and EDIFACT. If your team is experienced with BizTalk-based EDI environments, they can use these features to manage partner exchanges and automate document processing.

How Can Remedi Support BizTalk (and Logic Apps) Users?

If BizTalk’s looming end of lifecycle is on your radar, you’re already being proactive. But in an era of leaner teams and larger workloads, a consulting partner with BizTalk expertise can help you chart a path to the future of your integration environment.

Remedi can work with you to:

Help evaluate your BizTalk environment and assess operational health
Identify optimization opportunities to improve performance pre-migration
Develop a phased migration roadmap to Azure Logic Apps
Support your EDI and integration teams during modernization initiatives

We also support customers already operating within Azure and the Logic Apps ecosystem.

In the meantime, if you’d like to discuss potential migration paths from your current BizTalk environment, reach out here to connect.