If your business still runs on BizTalk Server, the support dates are now close enough to plan around. Here's what they mean and a practical way to move without a risky big-bang weekend.
The dates that matter
According to Microsoft's lifecycle page for BizTalk Server 2020:
- Mainstream support ends in April 2028. After that, there are no new fixes or feature changes.
- Extended support ends in April 2030. After that, security updates stop.
Older versions have shorter support windows, so check the lifecycle page for the exact version you run.
Why start now
Teams usually underestimate how long a migration takes. The work is rarely the code itself. It's finding every interface, every partner and every undocumented rule that someone added years ago. A medium-sized estate can take a year or more once testing and partner sign-off are included.
Starting early means you can move in small, calm waves instead of rushing before a deadline.
A five-step plan
- Inventory everything. List every application, receive and send port, orchestration, map, schema, custom pipeline component and trading partner. Note message volumes and which business process each one supports.
- Group interfaces into waves. Put simple, low-risk interfaces first and complex, high-volume ones later. Each wave should be small enough to test properly.
- Build the Azure foundation once. Networking, security, Key Vault, monitoring and CI/CD pipelines are set up as infrastructure as code, so every wave reuses them.
- Run a pilot. Move one real interface end to end to Logic Apps and Service Bus. This proves the approach, the cost model and the testing process before you commit to the full program.
- Migrate, test in parallel, then cut over. Run BizTalk and Azure side by side, compare results, and switch each interface only when the business signs off.
What carries over
Many BizTalk assets have a direct home in Azure Integration Services:
- Orchestrations become Logic Apps workflows.
- The MessageBox is replaced by Service Bus topics and Event Grid.
- XSD schemas and XSLT maps can often be reused in Logic Apps.
- EDI and AS2 partners move to an Integration Account.
- Custom pipeline components usually become Azure Functions or built-in actions.
Where to start this month
Pick one interface that is simple, well understood and not business-critical. Use it as your pilot. You'll learn more from one real migration than from months of planning documents.
If you'd like a second opinion on your estate, try the migration estimator for a first idea, or book a free call.