BizTalk to Azure Integration Services: The Complete Migration Playbook

Why Migrate from BizTalk?

Microsoft BizTalk Server has powered enterprise integration for over two decades. But as support timelines shorten and cloud adoption accelerates, organisations running BizTalk 2013, 2016, or 2020 face a strategic decision: modernise or maintain technical debt.

Azure Integration Services — comprising Logic Apps, API Management, Service Bus, Event Grid, and Durable Functions — offers a cloud-native alternative that eliminates infrastructure overhead, scales automatically, and integrates natively with the rest of the Azure ecosystem.

Phase 1: Inventory and Assessment

Before writing a single line of code, you need a complete inventory of your BizTalk environment. This includes:

• All orchestrations — count, complexity, dependencies
• All schemas and maps — XSLT complexity, custom functoids
• All send and receive ports — adapters in use (FILE, FTP, HTTP, SAP, SQL, etc.)
• All EDI agreements — X12, EDIFACT, AS2 trading partners
• BAM tracking requirements — which processes need audit trails
• Custom pipeline components — any C# code that needs porting
• Business rules (BRE) — rule sets that may move to Azure Logic Apps or custom APIs

Assessment scoring matrix

Score each orchestration from 1 (simple, low risk) to 5 (complex, high risk) across: number of shapes, external system dependencies, error handling complexity, and transaction requirements. This gives you a migration priority matrix.

Phase 2: Architecture Decision

Not every BizTalk pattern has a 1:1 Azure equivalent. Here are the key mappings:

• Orchestrations → Azure Logic Apps Standard (stateful workflows) or Durable Functions
• MessageBox pub/sub → Azure Service Bus topics and subscriptions
• Receive locations → Logic Apps triggers or Azure Functions
• ESB Toolkit itineraries → Logic Apps routing with dynamic expressions
• EDI pipelines → Logic Apps B2B / Azure APIM + custom
• BAM tracking → Azure Monitor + Log Analytics + Application Insights
• BRE rules → Azure Logic Apps conditions, or custom Rules Engine API

Phase 3: Migration Execution

We recommend a parallel-run approach: keep BizTalk live and migrate individual integrations one at a time, routing traffic progressively. This eliminates big-bang cutover risk.

• Start with stateless, low-risk file/FTP integrations
• Progress to HTTP/REST integrations
• Tackle EDI and SAP last — highest complexity
• Decommission BizTalk hosts one by one as workloads migrate

Phase 4: Testing and Validation

Every migrated integration needs: unit tests on transforms, integration tests with real endpoints (using test environments), performance tests for throughput-sensitive flows, and regression tests comparing BizTalk vs Azure output payloads byte-for-byte.

Phase 5: DevOps and Operations

Azure Logic Apps Standard supports slot-based deployment — blue/green zero-downtime releases. Establish Azure DevOps pipelines with parameter promotion across Dev → Test → Prod environments using Variable Groups. Monitor with Application Insights and set alert rules on failed run rates.