BizTalk End of Support: Your EDI Is the Part That Breaks First

When is BizTalk end of support for each version?

Sources: the BizTalk Server 2020, 2016 and 2013 R2 lifecycle pages, and Microsoft's end-of-sale announcement.

Nothing switches off in 2028. Microsoft's end-of-sale post says the end-of-sale date "does not require customers to stop running licensed deployments", and its December 2025 FAQ answered "Do I need to migrate now?" with a plain "No", pointing to "a long and predictable runway to plan your transition". When extended support ends, security updates and technical assistance stop. The workloads keep running without Microsoft servicing. No Microsoft page we have read describes support beyond 10 April 2030.

Why the dates differ by a day

The lifecycle update Microsoft posted in December 2025, and a note on the BizTalk 2020 lifecycle page, put the end of mainstream support at 11 April 2028. The lifecycle table and the August 2026 end-of-sale post say 12 April 2028. Extended support ends on 9 April 2030 in the December post and on 10 April 2030 in the lifecycle table. The table stamps each date at 6:59:59 AM and states that dates are shown in Pacific Time, which is the likely cause of the one-day shifts. No Microsoft page explains it. Plan to the earlier date.

What are your options when BizTalk goes?

There are four realistic routes for an EDI estate. None of them is free of work.

Microsoft's own advice is to treat additional support coverage as contingency time rather than the default destination. The offering "remains subject to final eligibility, coverage, pricing, and purchasing terms". Year 1 is expected to run from 13 April 2028 to 13 April 2029, and customers are expected to buy it by 11 April 2028 to stay eligible for Year 2.

What does BizTalk do in your EDI estate?

In an EDI estate, BizTalk is the trading-partner engine. Each partner is set up as a business profile, and the way each pair of profiles exchanges messages is set in a trading partner agreement.

Agreement properties decide EDI envelope processing and generation, acknowledgement handling, validation of incoming and outgoing messages, batching and status reporting. AS2 is the protocol that sends EDI messages securely between partners. The AS2 agreement and the EDI messaging agreement between the same profiles are specified separately, and both ends of each partnership need compatible settings.

On receipt, BizTalk picks the right agreement by matching the sender's and receiver's identifiers, falling back to a default when no match is found. One receive pipeline handles both the AS2 and the EDI processing. AS2 settings cover signing, compression, encryption, MDN requests and non-repudiation storage. An MDN (Message Disposition Notification) is the receipt returned to the sender. Then come the schemas and maps that turn a retailer's order into something your ERP can read.

Ask who in your team could rebuild one partner's agreement, certificate and map from scratch today, and how long it would take.

What has to be rebuilt in any BizTalk migration?

Microsoft's migration guidance is direct: "Migration isn't a lift-and-shift process."

Logic Apps Standard can reuse or adapt many BizTalk schemas and maps, and the December 2025 lifecycle update says most artefacts "can be reused with minimal effort using Microsoft and partner migration tooling". Microsoft's Migration Agent can parse BizTalk 2016 and 2020 source files, including maps, schemas, pipelines and bindings.

The Learn guidance then draws a line. For EDI and B2B, the assessment is to review partners, agreements, certificates, schemas and protocol requirements. Then the verifying falls to the customer. Contracts, mappings, rules, routing, ordering, retries and error behaviour all have to behave as they did before, edge cases included. The customer also coordinates partners, reconciles in-flight work and defines rollback. BizTalk is switched off only after validation. The agent speeds up analysis, and Microsoft says it does not replace architectural review or testing.

We agree with that caution. AI speeds up work on clean data. It should not map core formats like EDIFACT unchecked, because one wrong character breaks validation. Microsoft's cost guidance names two more lines to budget for: integration accounts, and running BizTalk and the new platform in parallel.

Why is EDI the part that breaks first?

An internal workflow that fails in testing is your problem, and you can fix it on your own schedule. A partner flow that fails lands on someone else's dock. Knowing a lorry is ten minutes away is useless if its ASN failed a validation rule and the gates reject it.

That is why the partner layer carries the risk. In BizTalk and in Logic Apps alike, every partner needs a defined profile, an agreement and settings that match on both sides. Microsoft's own Logic Apps B2B example needs two trading partners with the same business identity qualifier, plus an AS2 agreement and an X12 agreement between them, before a single message moves.

For some EDI estates, the sharpest signal is in Microsoft's expected exclusions. Industry accelerators (SWIFT, HL7 and RosettaNet), which provide schemas, pipelines and validation, "will not receive servicing, schema updates, or support under extended support". Microsoft adds that excluded BizTalk capabilities "may require architectural redesign or manual implementation outside the agent". If your partner flows rely on one of them, the paid bridge does not cover the part you need most.

We have written about what happens when in-house EDI misses a retailer's rule change at peak, and why native EDI built into the ERP quietly fails. The pattern is the same: the plumbing is rebuilt, and the partner rules are assumed.

What should EDI owners do now?

1. Confirm your version. BizTalk 2013 R2 is already out of support and 2016 extended support ends on 12 January 2027. For 2016, Microsoft strongly encourages moving directly to Logic Apps rather than upgrading to BizTalk Server 2020.
2. List every trading partner with its AS2 agreement, EDI agreement, identifiers, qualifiers, certificates and MDN settings.
3. List every schema and map by partner and document type, and name an owner for each.
4. Check for expected exclusions: the RosettaNet, SWIFT and HL7 accelerators, the ESB Toolkit, Business Activity Monitoring and legacy enterprise adapters.
5. If you use the Service Bus adapter, check you have Microsoft's AMQP hotfix (KB5091379). Azure Service Bus retired SBMP support on 30 September 2026.
6. Buy any extra BizTalk 2020 licences you need before sales are expected to end on 31 March 2027.
7. Diary the paid-bridge decision. Microsoft expects Year 1 to be bought by 11 April 2028 for Year 2 eligibility.
8. Plan cutover partner by partner, with rollback. Microsoft's guidance says: "For most BizTalk estates, migrate in waves rather than using a single big-bang release".

Our guide to keeping business as usual when switching EDI covers the partner side of that plan.

Where does a managed EDI network fit?

If most of your BizTalk estate is partner EDI, the real choice is whether to rebuild that layer on a new platform or move it to a network that already runs it. Transalis is a managed outcomes provider for B2B integration, EDI and eInvoicing. You connect once to the Transalis Trading Network, and each new partner or message type joins the same connection instead of a new custom build. A switch runs as a managed migration programme: Transalis assesses your existing EDI environment, recreates the connections, mappings and integrations, and tests them before any production traffic moves.

The largest retail hubs run on EDI and will not rebuild core infrastructure for their suppliers because APIs are fashionable, so we run EDI and API side by side rather than asking you to rip out working foundations. Argos, AS Watson and Superdrug moved from in-house EDI teams to a managed service and scaled from one major retailer to thousands of trading partners without adding headcount.

Transalis already connects to Microsoft BizTalk Server, so BizTalk does not have to disappear on the day the network arrives. The same connection can later carry eInvoicing, which the UK government has announced as mandatory for VAT invoices from 2029, with Peppol as the core network.

You have time. Use it on the partner layer first. Talk to a migration specialist about your BizTalk partners.