<appsInfo> // let's connect
Azure Integration Services

Connect every system. Move off BizTalk with confidence.

We design, build and run integrations on Azure (APIs, workflows, EDI and events) and migrate BizTalk Server estates to Azure Integration Services step by step, without disrupting the business.

BizTalk Server 2020 support

The clock is running.

Mainstream support endsApril 2028. No new fixes or features after this.
Extended support endsApril 2030. Security updates stop.

Source: Microsoft Lifecycle, BizTalk Server 2020. Large estates often take 12–24 months to migrate.

The Azure integration toolkit

Six building blocks, one modern platform.

Azure Integration Services is a family of managed services that together cover everything BizTalk did, with cloud scale, pay-as-you-go pricing and modern DevOps.

Logic Apps

Workflows that orchestrate processes, transform XML and JSON, apply business rules and connect to hundreds of systems.

Service Bus

Enterprise messaging with queues and topics: guaranteed delivery, retries and publish/subscribe. The modern MessageBox.

API Management

One secure front door for all your APIs: authentication, rate limits, versioning, analytics and a partner portal.

Event Grid

Real-time event routing. React the moment a file lands, an order is placed or a record changes.

Azure Functions

Serverless C# for the custom logic BizTalk handled in pipeline components and helper classes.

Integration Account

B2B and EDI for trading partners (X12, EDIFACT and AS2), with partners, agreements, schemas and maps in one place.

Reference architecture

How it fits together.

Messages come in through APIs or events, Logic Apps orchestrate and transform them, Service Bus delivers them reliably, and everything is secured and monitored centrally.

BizTalk to Azure

Every BizTalk feature has a modern home.

We map each BizTalk component to its Azure equivalent and reuse what we can. XSD schemas and XSLT maps often carry over directly.

BizTalk ServerAzure Integration Services
Receive ports & locationsLogic Apps triggers and API Management
Send portsLogic Apps actions and connectors
OrchestrationsLogic Apps workflows (Standard)
MessageBox (publish / subscribe)Azure Service Bus topics and Event Grid
Maps (XSLT)Logic Apps XML transforms and Data Mapper
Schemas (XSD)Reused in Logic Apps or an Integration Account
Pipelines & custom componentsBuilt-in XML operations and Azure Functions
Business Rules EngineAzure Logic Apps Rules Engine
Adapters (SQL, SAP, FTP, File, MQ)Built-in and managed connectors, on-premises data gateway
Trading partners, EDI & AS2Integration Account (B2B: X12, EDIFACT, AS2)
BAM & message trackingAzure Monitor and Application Insights
SSO database (credentials)Azure Key Vault and managed identities

How we work

A proven six-step migration path.

BizTalk and Azure run side by side the whole way. We move interfaces in small, tested waves, so there is never a risky big-bang weekend.

  1. 1Assess
  2. 2Plan
  3. 3Build the foundation
  4. 4Migrate in waves
  5. 5Test in parallel
  6. 6Cut over & support
01

Assess

We inventory every BizTalk application (ports, orchestrations, maps, schemas, adapters and custom code) plus message volumes and dependencies.

You getAssessment report and migration backlog
02

Plan

We group interfaces into waves by risk and value, choose rebuild or re-platform for each, and design the target architecture.

You getTarget architecture and roadmap
03

Build the foundation

Networking, security, Key Vault, monitoring and CI/CD pipelines, set up as infrastructure as code with Bicep or Terraform.

You getA production-ready Azure landing zone
04

Migrate in waves

We start with a low-risk pilot, then move interfaces wave by wave, reusing schemas and maps wherever possible.

You getWorking interfaces every sprint
05

Test in parallel

Automated tests plus side-by-side runs against BizTalk prove each interface produces the same results before the switch.

You getTest evidence and business sign-off
06

Cut over & support

We switch traffic, provide hypercare, decommission BizTalk servers and train your team to run the new platform.

You getRunbooks, dashboards and handover

Migration estimator

How big is your BizTalk migration?

Move the sliders to match your BizTalk estate. You'll get a rough size, timeline and wave plan in seconds.

40
15
5
0
Uses the Business Rules Engine?
BizTalk version
Medium estate
Estimated timeline5–8 months
Suggested waves
    A rough planning estimate based on typical projects, not a quote. Book a free assessment for a costed plan. Get a free assessment

    Ways to start

    Start small. Scale when you're ready.

    BizTalk assessment

    A full inventory of your BizTalk estate, its risks and a costed migration roadmap.

    Fixed quote
    Best first step

    Pilot migration

    One real interface moved end to end to Azure, to prove the approach before you commit.

    Fixed quote

    Full migration program

    Every interface migrated in planned waves, with testing, cutover and decommissioning.

    Custom quote

    Managed integration

    We monitor, support and improve your Azure integrations every month after go-live.

    Monthly quote

    Why move now

    More than beating a deadline.

    No servers to patch

    Managed services replace the BizTalk servers, SQL clusters and host instances you maintain today.

    Pay for what you use

    Consumption and flexible plans instead of large up-front licence and hardware costs.

    Scale automatically

    Handle seasonal peaks and new partners without buying capacity in advance.

    Modern DevOps

    Infrastructure as code, automated deployments and full monitoring from day one.

    Connect to the cloud

    Hundreds of ready-made connectors, plus a data gateway for on-premises systems.

    Ready for AI

    Once your data flows through Azure, adding AI steps to workflows is straightforward.

    Common questions

    Do we have to migrate everything at once?

    No. BizTalk and Azure run side by side while we move interfaces in waves, starting with a low-risk pilot.

    Can we reuse our maps and schemas?

    Often, yes. XSD schemas and XSLT maps can usually be reused in Logic Apps. Custom code is reviewed case by case.

    What about on-premises systems?

    They stay connected. The on-premises data gateway lets Azure workflows securely reach SQL, files, SAP and more.

    How long does a migration take?

    It depends on the number of interfaces, orchestrations and custom components. Small estates can move in a few months; large ones take a year or more. Try the estimator above for a first idea.

    Can you support our BizTalk environment while we migrate?

    Yes. We can monitor and fix the existing BizTalk setup during the migration, so the business keeps running until each interface is switched.

    Will our running costs go up on Azure?

    Not necessarily. Many teams save by retiring servers and licences. We model the expected Azure cost in the assessment, before you commit.

    Still running BizTalk? Let's map your way out.

    Book a free 30-minute call. We'll review your setup and outline a realistic migration path.

    Get a free assessment
    Book a free call