We built Connext on AWS. Today, we’re expanding to Microsoft Azure, giving every enterprise the freedom to deploy their integration platform on the cloud that fits their strategy.
When we launched Connext, the cloud landscape looked different. Amazon Web Services dominated enterprise infrastructure conversations, and building on a single, battle-tested platform made every kind of sense. We invested deeply in that foundation and it has served our customers well. But enterprise cloud strategy has evolved, and so have we. Today, we’re proud to announce that Connext is now a multicloud iPaaS, with full support for deploying on Microsoft Azure, in addition to our existing AWS offering.
“Your integration platform should serve your cloud strategy, not dictate it.”
What This Means In Practice
Azure support is not a limited preview or a feature subset. You can deploy the complete Connext platform, integration runtimes, databases, userstores, idenity providers, API gateways and all associated services, natively on Azure infrastructure. Everything you rely on today is available, in full, on Azure.
This includes the same product portfolio, the same Connext development/monitoring experience, the same SLAs, and the same enterprise security posture that Connext customers already depend on. The cloud you run on is a deployment choice. It doesn’t change your iPaaS experience or your support model.
| Then: AWS only | Now: AWS + Azure |
|---|---|
| Single cloud infrastructure | Two major cloud platforms |
| AWS-aligned procurement only | AWS & Microsoft EA support |
| Azure-first enterprises excluded | AWS & Azure based enterprises reachable |
| One cloud deployment target | Your cloud, your choice |
Why We Built This
The simplest answer: our customers asked for it, and the market demanded it. A large and growing segment of the enterprise world has standardised on Azure, whether by strategic choice, through regulatory requirements, or via Microsoft Enterprise Agreement procurement. For those organisations, introducing a separate cloud just to run their integration platform was a non-starter.
We also saw a broader shift. Enterprises are no longer building on one cloud and staying there. Post-acquisition scenarios, geographic expansion, regulatory data residency requirements, and evolving vendor relationships mean that multicloud is now the operating reality for most large organisations. An iPaaS that only lives on one cloud is, increasingly, a constraint.
Connext’s job is to be the connective tissue of your enterprise architecture. That job is hard to do well when we’re tied to a single infra provider. Azure support changes that.
Who Benefits
| Azure-first enterprises | Regulated industries |
| Organisations standardised on Microsoft infrastructure can now adopt Connext without introducing AWS. | Financial services, healthcare, and public sector customers with Azure approval requirements can finally qualify Connext. |
| Microsoft EA holders | Multicloud & hybrid orgs |
| Enterprises with committed Azure spend can procure Connext through Azure Marketplace, drawing down existing commitments. | Organisations spanning multiple clouds can deploy Connext environments across both AWS and Azure from a single platform. |
Connext Deployment Models On Azure
Because enterprise cloud governance varies significantly, we’ve built Azure deployments around two distinct ownership models. Giving organisations the flexibility to choose the approach that fits their structure.
In the first model, the customer or a third party provides the Azure Landing Zone. The enterprise retains full ownership of the Azure subscription, billing, and governance controls. Connext deploys within that landing zone, respecting whatever boundaries and policies the customer has established. This is the right choice for organisations that have invested in a corporate Azure foundation and want to keep centralised control over what runs where.
In the second model, Connext provides and fully manages the Azure subscriptions for underlying platform. The same fully managed model that has always been available on AWS. The customer gets a complete, production-ready Connext platform with no infrastructure management required. This remains the simplest and fastest path to azure deployments.
What Stays Exactly The Same
We want to be clear about this: Azure support is additive. Nothing about your existing Connext platform changes. If you’re on AWS or requires AWS based platform, you stay on AWS. Your integrations, your workflows, your SLAs, and your support experience are unaffected.
For new Azure deployments, customers will find the same portal, the same Connext workflows and the same support channels they’d expect from Connext on AWS. The team that supports your platform has been trained and certified on Azure operations. Monitoring, alerting and incident response cover both cloud platforms.
Looking Ahead
This release represents something larger than a single cloud provider addition. It reflects a commitment to meeting customers wherever their infrastructure lives, and to building an integration platform that outlasts any single vendor relationship.
Multicloud is not a trend we’re chasing. It is the operational reality of enterprise IT in 2026, and Connext is built to serve it. We’re excited about what this opens up for existing customers expanding their cloud footprint, and for the organisations that can now consider Connext for the first time.
But this is also, deliberately, a first step. Multicloud flexibility is the foundation on which we’re building something more ambitious: Sovereign cloud solution for Connext. We know that for some of our customers, particularly those operating in heavily regulated sectors, national government, or jurisdictions with strict data sovereignty requirements, neither a hyperscaler-hosted nor a standard managed cloud deployments fully meets their needs. They need control that goes deeper: over where data lives, who can access infrastructure, and how the platform is operated at every layer.
Near Future: Connext On Sovereign Cloud
A dedicated deployment model designed for organisations with the most demanding data residency, jurisdictional, and operational sovereignty requirements. Built on the multicloud foundation we’re establishing today. More details coming soon.
The work we’re doing now, proving out flexible cloud deployment, building support for customer-provided landing zones, and expanding our infrastructure reach is the groundwork that makes sovereign cloud possible. Today’s announcement and tomorrow’s sovereign offering are part of the same direction of travel. Connext Azure based platforms are available now. If sovereign cloud is on your radar, we’d welcome a conversation about your requirements and timeline.
Ready To Explore Connext On Azure?
Talk to our team about your deployment options, or dig into the documentation to get started.
