Cerebrum City Insights
Field notes from two decades of running BizTalk Server in enterprise production — end-of-life planning, Azure migration patterns, EDI and HL7/FHIR interoperability, and the failure modes nobody documents. Written by the architects who do the work, not a content team.
The Cost of Staying on BizTalk and How to Fund the Move
Azure Migration · 1 minHL7 v2 to FHIR: What Actually Changes When You Leave BizTalk
There is a version of the healthcare integration conversation that goes: BizTalk is ending, FHIR is the future,…
HL7 & FHIR · 7 minLatest
Newest firstMoving EDI Off BizTalk Without Breaking Trading Partner Relationships
Ask an integration team what worries them about a BizTalk migration and the EDI answer comes back fast: "we have 140 trading partners." The…
Logic Apps Is the Right Destination for Most BizTalk Workloads. Here Is Where It Is Not.
Let us start by conceding the argument, because vendors in our position are usually suspected of the opposite. Azure Logic Apps is Microsoft's named…
Why BizTalk Migrations Stall: Five Failure Modes We See in Production
We have never seen a BizTalk migration fail on a Tuesday morning with a spectacular outage. That is not how these projects die. They…
Every BizTalk Artifact, and What It Becomes in Azure
The first real question in any BizTalk migration is not "which Azure service?" It is "what is this thing I am holding, and what…
Microsoft Has Confirmed It: BizTalk Server 2020 Is the Final Version
For years, "is BizTalk being discontinued?" was a question you could only answer by inference. Microsoft had shipped no successor to BizTalk Server 2020,…
Reading about the migration is step one. Scoping yours is step two.
BizTalk Server 2020 is the last version Microsoft will ship. Talk to an architect who has run BizTalk in production for two decades — not a generic cloud partner learning it on your estate.








