Skip to content
Let’s Talk(678) 203-0800 Partner ProgramDocumentationDocsBlogContact
For teams replacing or modernizing Microsoft BizTalk Server

BizTalk Alternative

Everything BizTalk does, cloud-native on Azure.

BizTalk Server 2020 is the final version, and its support has an end date. iQBus is the Azure-based alternative: schemas, maps, orchestrations, pipelines and adapters carry over, with live tracking built in. Built by the original BizTalk architects.

Trusted by enterprise integration teams

  • BlueCross
  • Humana
  • University of Utah Health
  • Bank of America
  • Citibank
  • IDB
  • Deloitte
  • JetBlue
  • U-Haul
  • Landstar
  • Vertellus
  • Ardent Mills
  • Glatfelter
  • Leupold
  • Novo Nordisk
  • NABP
  • deckCommerce
  • Kids2
The BizTalk challenge

BizTalk stopped at 2020. The clock is running.

Microsoft has confirmed that BizTalk Server 2020 is the last and final version. Nothing switches off when support ends, but the fixes and security updates stop, and the people who know your integrations get harder to find every year.

That makes this a planning question, not an emergency: decide your long-term integration strategy now, and move on your own timeline instead of a forced cutover later.

See how the transition works
  1. 2020
    Final major version
    No new BizTalk version
  2. 2028
    Mainstream support ends
    Apr 2028 — non-security updates and free support stop
  3. 2030
    Extended support ends
    Apr 2030 — no more paid hotfixes, fully unsupported
Why iQBus

The Azure-based alternative to BizTalk Server.

iQBus is an enterprise service bus that runs on Azure, in your own tenant, and keeps the BizTalk model. For a team evaluating a replacement, that means your existing work converts instead of being rewritten, and your people keep working with concepts they already know.

Key features and capabilities

  • Enterprise integration

    • The BizTalk constructs you already know: schemas, maps, orchestrations, pipelines, ports
    • XSD schemas carry over as they are; maps run on XSLT 3.0 with custom functions
    • EDI, HL7 and FHIR integrations, in production use today
  • Connectivity

    • Adapters for REST APIs, SFTP, file shares, Azure Blob Storage and SQL
    • Azure Service Bus, MQ Series, SAP, Salesforce and Microsoft 365 mail
    • AS2 for EDI trading partners; the adapter library grows every week
  • Messaging

    • Publish and subscribe routing on message type and promoted properties
    • Configurable retries on every send port
    • Suspended messages resume in one click, or terminate, from the tracking console
  • Workflow automation

    • Orchestrations become declarative itineraries
    • Scheduled runs with the Scheduler adapter, and email alerts when something fails
    • AI Accelerator drafts pipeline components, maps and custom functions for your review
  • Scalability

    • Serverless on Azure: scales with load and scales to zero when idle
    • No server farm, no host instances to size or patch
    • Configuration changes go live on save: no builds, no restarts
  • Security

    • Runs inside your own Azure tenant; messages and data never leave it
    • Microsoft Entra ID sign-in and OAuth 2.1
    • iQBus supports SOC 2 and HIPAA, with iQBus Auditing recording user and agent actions
  • Azure infrastructure

    • Built on Azure services, available through the Microsoft Marketplace
    • Azure usage is billed to your own subscription
    • MCP Server and AI Accelerator run in your tenant: AI fully in-tenant
  • Not sure it covers your estate?

    Bring your adapter list and message formats. Fifteen minutes with an integration architect will tell you.

    Book a Free 15-Minute IT-to-IT Consultation
From BizTalk to iQBus

Everything BizTalk does, and more.

Each BizTalk capability has an iQBus equivalent, so your team keeps working the way it knows. Then iQBus adds what BizTalk Server never had.

How each Microsoft BizTalk Server capability moves to iQBus, and what iQBus adds
Capability In BizTalk Server today becomes In iQBus
Carries overEverything you run in BizTalk today has an iQBus equivalent
Message schemas XSD schemasBuilt in a Visual Studio project XSD schemas, as they areManaged in the web console, no IDE
Transformation / mapping Maps (BTM)XSLT 3.0 and functoids iQBus MapsXSLT 3.0 with custom functions
Orchestrations OrchestrationsBuilt and compiled in Visual Studio Declarative itinerariesConfigured, not compiled
Message pipelines Custom pipelinesReceive and send pipeline components Custom pipelinesPipeline components in C#
Routing Publish and subscribeMessageBox and promoted properties Publish and subscribeSend-port subscriptions on message type and promoted values
Adapters / connectivity AdaptersAdapter pack AdaptersNew connectors every week
EDI, HL7 and FHIR EDI, HL7 and FHIREDI and HL7 accelerators EDI, HL7 and FHIRAS2 included with EDI
Message tracking Group Hub, tracking queries, BAMAdmin Console and separate BAM portal Built-in tracking dashboardEvery message, with one-click resume
Infrastructure monitoring Administration ConsoleServer health through SCOM or third-party tools Built-in infrastructure dashboardApp Service plans and SQL databases in one view
Security and identity Windows accounts and Enterprise SSO Microsoft Entra ID and OAuth 2.1Runs inside your own Azure tenant
Hosting Server farmHost instances on servers you run Serverless on AzureScales with load, and to zero when idle
Release steps Build and deployRestart host instances Configuration, live on saveNo builds, no restarts
New in iQBusWhat iQBus adds that BizTalk Server never had
AI and agents Not built in NewAI Accelerator and MCP ServerChoice of AI models, running fully inside your tenant
User and agent auditing Not built in NewiQBus AuditingEvery user and agent action recorded
Compliance Not built in NewSupports SOC 2, ISO 27001, HITRUST and HIPAAFollows NIST SP 800-63B
Product roadmap Final version: BizTalk Server 2020Support ends April 2030 NewRegular releasesIn production today; new adapters and features every week
Book a Free 15-Minute IT-to-IT Consultation

Comparison reflects generally available capabilities at the time of publication. Microsoft and BizTalk Server are trademarks of Microsoft Corporation.

The team behind iQBus

Real teams. Real systems in production.

iQBus is built by Cerebrum City's integration architects, the same people who deliver enterprise integrations for companies that run on them.

Cerebrum City architects delivering the KapStone EDI integration
EDI integrationKapStoneDelivered the company's complete EDI integration across its trading-partner network.
Cerebrum City architect presenting an integration flow at Glatfelter
EDI and SAPGlatfelterModernized legacy EDI and built new SAP integrations.
Cerebrum City developers who delivered the Multi-Fineline Electronix BizTalk upgrade
BizTalk ServerMulti-Fineline ElectronixUpgraded BizTalk Server from 2016 to 2020.
BizTalk alternatives compared

iQBus beside the other platforms teams evaluate.

Most teams replacing BizTalk Server look at more than one option. Here is how iQBus sits next to six platforms that often appear on the same shortlist, using what each vendor publishes about its own product.

Use the arrows, or scroll the table sideways, to see all seven platforms.

Capability iQBusCerebrum City MuleSoftSalesforce BoomiBoomi WorkatoWorkato Azure Logic AppsMicrosoft TIBCOCloud Software Group Oracle Service BusOracle
What it is Enterprise service bus (ESB) on Azure Integration and API platform (Anypoint) Low-code integration platform (iPaaS) Integration and automation platform (iPaaS) Workflow integration service on Azure Integration platform (BusinessWorks, Flogo) Enterprise service bus (Oracle SOA Suite)
Where it runs Inside your own Azure tenant MuleSoft cloud (CloudHub) or your own infrastructure Boomi cloud or your own infrastructure Workato cloud, with on-premises agents Inside your own Azure tenant TIBCO cloud or your own infrastructure Your own servers, or Oracle Cloud
Connectors Core enterprise adapters (APIs, SFTP, SQL, SAP, Salesforce, MQ, Service Bus); new connectors every week Hundreds of pre-built connectors 1,000+ pre-built connectors 1,200+ pre-built connectors 1,400+ pre-built connectors 300+ pre-built connectors Oracle Integration Adapters
B2B and EDI IncludedEDI with AS2, HL7 and FHIR Separate productAnypoint Partner Manager IncludedB2B/EDI Management Add-onWorkato EDI, powered by Orderful Separate resourceIntegration account: X12, EDIFACT, AS2 Separate productBusinessConnect Separate licenseOracle B2B
Message tracking IncludedEvery message, with one-click resume of suspended runs IncludedAnypoint Monitoring: logs, traces, alerts IncludedProcess Reporting: execution history and logs IncludedJob history for each recipe IncludedRun history for each workflow; Azure Monitor across workflows IncludedObservability dashboard in the Control Plane IncludedMessage reporting in the Service Bus console
Infrastructure monitoring IncludedDashboard for the Azure App Service plans and SQL databases it runs on IncludedCPU and memory for CloudHub and Runtime Fabric apps IncludedRuntime status in the Boomi platform Managed by vendorWorkato runs the platform; usage dashboard for customers IncludedAzure Monitor and Application Insights IncludedData plane monitoring in the Control Plane IncludedOracle Enterprise Manager Fusion Middleware Control
AI and agents IncludedAI Accelerator and MCP Server inside your tenant; choice of AI models IncludedAgent Fabric and AI gateway policies IncludedBoomi AI agents By editionAgent Studio and pre-built MCP servers IncludedAgentic workflows and MCP servers Not stated Not stated
Compliance Supports SOC 2, ISO 27001, HITRUST and HIPAA; follows NIST SP 800-63B SOC 2, ISO 27001 SOC 1, SOC 2, HIPAA, ISO 27001, PCI DSS, FedRAMP SOC 1, SOC 2, HIPAA, ISO 27001, PCI DSS SOC, HIPAA, ISO, PCI DSS (Azure) SOC 2, ISO 27001 Depends on where you host it
Coming from BizTalk ConvertsSchemas, maps, orchestrations and pipelines convert; typically 50–70% of artifacts carry forward Rebuild requiredIntegrations are redeveloped on its own model Rebuild requiredIntegrations are redeveloped on its own model Rebuild requiredIntegrations are redeveloped on its own model Rebuild requiredIntegrations are redeveloped as workflows, assisted by the Logic Apps Migration Agent Rebuild requiredIntegrations are redeveloped on its own model Rebuild requiredIntegrations are redeveloped on its own model
Published pricing Starter: no license fee (you pay only your Azure). Grow: $250/month. Enterprise: from $500/month From $2,000/month, billed annually Pay-as-you-go: $99/month + $0.05 per message Quote-based Per execution, or per hosting plan Quote-based Per processor or per user license

About this table. The information on MuleSoft, Boomi, Workato, Azure Logic Apps, TIBCO and Oracle Service Bus was taken from each vendor's own public website and documentation in November 2026. Products, packaging and prices change, so it may not reflect what they offer today. Please check with each vendor directly before you decide. “Not stated” means we did not find it on the vendor pages we reviewed, not that the product lacks it. This is a summary of published capabilities, not a ranking. All product names are trademarks of their respective owners.

Built-in tracking

Explore the tracking console.

This is the iQBus console, running with sample data. Follow a message through every port, map and pipeline, open a suspended run and resume it. No BAM, no add-ons.

The iQBus tracking console: message counts and a live flow of an order-intake integration
  • Switch between Flow and Table
  • Filter by time or message type
  • Play a scenario from Scenarios
Migration and modernization

Assess your BizTalk estate, then convert it.

It starts with an inventory of what you run today: applications, schemas, maps, orchestrations, pipelines, adapters and trading partners. The iQBus Migration AI then reads each artifact and generates the iQBus equivalent, reviewed by our architects before anything ships.

  1. 1

    Assess your estate

    Upload your solution or point at your repo. The AI inventories every artifact, so you see what you have before deciding anything.

  2. 2

    AI conversion

    Maps become XSLT 3.0 and orchestrations become itineraries, automatically.

  3. 3

    Architect review

    The original BizTalk architects validate the output. Nothing ships unreviewed.

  4. 4

    Go live in your tenant

    Approved configuration goes live in your own Azure tenant. No builds, no restarts, no downtime.

Built by the people who defined the category

We didn't just learn the rules of enterprise integration. We helped write them.

iQBus comes from Cerebrum City's integration architects, Microsoft V-TSPs for BizTalk Server with two decades running it in enterprise production.

20+
Years in enterprise middlewareBizTalk in production since the first releases
V-TSP
Microsoft V-TSP for BizTalk ServerThe original BizTalk architects
Microsoft Solutions PartnerCloud & AI Platforms · on Azure Marketplace
Customer story

Retiring BizTalk with zero downtime and 50–70% artifact reuse.

Cerebrum City moved Novelty, Inc.'s retail-partner EDI off end-of-life BizTalk Server to iQBus on Azure, carrying 50–70% of the existing artifacts forward with no downtime at cutover.

iQBus has been a real asset to the business. Its intuitive interface allowed us to implement EDI effortlessly, and the built-in transaction tracking gives us the visibility to manage operations with confidence.

Cheryl Patterson, Chief of Staff, CPA, Novelty Inc.
50–70%
of BizTalk artifacts reused
Zero
downtime at cutover
Hours
to onboard a partner, not weeks
Novelty, Inc.

Retail-partner EDI
BizTalk Server → iQBus on Azure

Integration for the work that can't stop

A clinical informatics nurse and a hospital IT analyst review a dashboard at a workstation beside a hospital corridor Healthcare & life sciences iQBus for healthcare Move HL7 messages between EHR, lab and payer systems, with every message traced end to end. iQBus supports HIPAA.
A payments operations analyst and a colleague review transaction screens on a bank operations floor Financial services iQBus for financial services Route payments, statements and partner files through a governed runtime in your own Azure tenant. iQBus supports SOC 2.
A distribution center supervisor with a tablet talks with a forklift operator near the loading docks Logistics & manufacturing iQBus for logistics and manufacturing Exchange EDI orders, ship notices and invoices with trading partners, and onboard a new partner in hours, not weeks.

Book a Free 15-Minute IT-to-IT Consultation

Talk directly with our technical team about your BizTalk environment, integration challenges and options for moving forward with iQBus.

  • Free, 15 minutes
  • IT to IT, no sales deck
  • Reply within one business day

You'll speak with a senior integration architect, not an SDR. We'll meet on Teams.

Common questions

BizTalk alternatives, answered.

Still weighing your options? Book a free 15-minute IT-to-IT consultation.

Is iQBus a genuine BizTalk replacement?

Yes. iQBus provides capability parity with every core BizTalk construct — schemas, maps, orchestrations, pipelines, and adapters — while running serverless on Microsoft Azure. It's built by the original Microsoft BizTalk Server architects at Cerebrum City as the cloud-native evolution of the platform.

How does the AI migration tool work?

The iQBus Migration AI inventories your BizTalk solution, then converts each artifact to its iQBus equivalent: XSD schemas migrate as-is, BizTalk Maps become XSLT 3.0 iQBus Maps, orchestrations become declarative itineraries, and pipelines are rebuilt on the deterministic iQBus pipeline. Every conversion is reviewed by a senior architect before it ships.

When does BizTalk Server support actually end?

BizTalk Server 2020 is the final major version. Mainstream support ends in April 2028, and paid extended support runs until April 2030 — after which it is fully unsupported. Microsoft points customers to Azure Logic Apps, which has no MessageBox, pipelines or BAM, so moving there means rebuilding rather than migrating. Planning now avoids a forced, rushed cutover later.

Do we have to migrate everything at once?

No. Migrations are phased, and many customers run BizTalk and iQBus side by side during transition. Cerebrum City can also support and extend an existing BizTalk estate — including end-of-life versions — until you're ready to move.

Where does iQBus run — and who can see our data?

iQBus runs inside your own Azure tenant with Entra ID integration, encryption, and audit controls. Your messages and data never leave your environment.

What are the main alternatives to BizTalk Server?

Teams replacing BizTalk usually weigh four routes: rebuilding on Azure Integration Services (Logic Apps, Service Bus, Functions, API Management), moving to a general-purpose iPaaS, adopting another ESB product, or moving to a platform built on the BizTalk model, such as iQBus. The deciding question is how much of your existing work carries over. iQBus keeps the BizTalk constructs, so schemas, maps, orchestrations, and pipelines convert rather than being rewritten, with 50-70% of artifacts typically reused.