Azure Local disconnected operations runs Azure on your own hardware with no connection to the public cloud. What you get, what it takes, and how Splitbrain gets you there.
Updated November 2026
Azure Local disconnected operations runs the Azure portal, Azure Resource Manager, and your workloads on your own hardware, with no connection to the Azure public cloud. It has been available since Azure Local 2602. Splitbrain designs, deploys, and manages these environments.
When Microsoft announced it, I had a flashback to 2017. Back then we ran Azure Stack, later Azure Stack Hub, in Disconnected Mode: Azure fully off the grid. The idea is the same today. The execution is a lot better.

You need it when a connection to Azure is impossible or not allowed:
If you have connectivity, you probably don't need it. Regular Azure Local keeps running for up to 30 days without contact with Azure, and you keep the full set of Azure services. Disconnected is for when you need it, not for when it feels safer.
Not sure which side you're on? Ask us. It's usually clear after one conversation.
Azure Stack Hub had the right idea at the wrong time. We ran it for customers and needed a near-dedicated support channel with Microsoft just to keep it going. Three things held it back:
Microsoft learned from it. Azure Local replaces those 20+ VMs with one appliance that runs the control plane in containers. And one control plane now manages many clusters across many locations.
| What you get | What you give up | What it takes |
|---|---|---|
| The Azure portal, Azure Resource Manager, RBAC, Azure Policy, Key Vault, and Container Registry, all running locally | Azure Monitor. You monitor with System Center Operations Manager, Prometheus, and Grafana | A dedicated three-node management cluster, with 24 cores and at least 128 GB of memory per node |
| Windows and Linux virtual machines and AKS clusters | Microsoft Entra ID. Identity runs on Active Directory and AD FS | Your own internal certificate authority |
| One control plane for all your clusters, sized for 100+ or 1,000+ nodes | Automatic updates. Fully air-gapped, you import them yourself | Approval from Microsoft: an eligible agreement and a valid reason to run disconnected |
| AI, productivity, and development on top: Foundry Local, Microsoft 365 Local, and GitHub Enterprise Local | Cloud-only services such as Defender for Cloud | A licence per physical core, on an annual term |
You can also choose a middle road. In limited connectivity mode the appliance may reach Azure for updates and support, while your workloads and data stay local.
Microsoft keeps building on it. Multi-tenancy has been announced, which matters most to service providers, and Microsoft has published guides for NATO Unclassified, Restricted, and Secret environments (Microsoft, November 2026).
Disconnected operations isn't something you download and install. Microsoft approves each organisation, and the design choices you make up front (management cluster, identity, certificates, update route) are hard to change later.
Splitbrain has done this before:
We help you decide whether you need disconnected at all, get you through Microsoft's approval, design and deploy the environment, and keep it running with managed services if you want us to.
Planning a disconnected or sovereign environment? Talk to Splitbrain. Tell us about your locations and requirements, and we'll tell you whether you need disconnected operations or whether connected Azure Local will do.
It's a version of Azure Local that runs the Azure control plane (portal, Azure Resource Manager, RBAC, Policy, and Key Vault) on your own hardware. Nothing connects to the Azure public cloud. It has been available since Azure Local 2602.
Yes. Regular Azure Local runs for up to 30 days without contact with Azure. With disconnected operations it runs offline permanently.
In practice, yes. It covers the same fully offline scenario with a much smaller control plane, and one control plane manages many clusters.
A dedicated management cluster of three nodes, each with 24 physical cores and at least 128 GB of memory, on validated Azure Local hardware. Your workloads run on separate clusters.
Yes. Foundry Local runs AI models on your own hardware without a cloud connection.
Microsoft approves each organisation. You need an eligible agreement, a support plan, and a valid reason to run disconnected. Splitbrain prepares that request with you.
Splitbrain can. Splitbrain has done more than 100 Azure Local deployments, has two Microsoft MVPs, and has run disconnected Azure environments since Azure Stack Hub. Get in touch to discuss your environment.
One conversation is usually enough to see where the value is for your organization, whether that’s in cost, risk, or everyday management. No slides required.
