Microsoft brings Foundry Local and GitHub to disconnected sovereign clouds

What Microsoft announced

Microsoft has laid out the next stage of Microsoft Sovereign Cloud, its offering for governments, critical infrastructure and regulated industries that want tighter control over where their systems run and who can touch them. In a 20 October 2026 post on the Official Microsoft Blog, Douglas Phillips, who leads engineering for Microsoft's specialized, sovereign and private clouds, described new controls across the public cloud, customer-run data centres and partner-operated clouds.

The AI pieces stand out. Microsoft says Foundry Local, its system for running AI models on customer hardware, will become generally available at its Ignite conference for both connected and fully disconnected operation on Azure Local. GitHub Enterprise Local, a validated GitHub Enterprise Server appliance on the same platform, will reach general availability at Ignite too, and developers will be able to use GitHub Copilot with locally hosted models.

Azure Local is Microsoft's software for running Azure services on servers a customer owns and operates. Together, the announcements mean an organisation could keep its code, its data, its AI models and the assistant that writes code inside its own walls, even with no link to Microsoft's public cloud.

AI models that never leave the building

Microsoft frames sovereignty around individual workloads. A public-facing service may be fine in the public cloud, Phillips writes, while an AI workload handling highly sensitive data may need models, data and processing to stay inside a customer-controlled environment.

Foundry Local is aimed at that second case. At general availability it will come with what Microsoft calls an expanded model catalogue, including Microsoft, partner, open-weight and open-source models. Microsoft did not list which models will be available or how large they can be.

The company also promises local inference and agentic retrieval, so users can ask questions in plain language about local enterprise data and get answers grounded in that data. An integration with Microsoft 365 Local, in preview for approved customers, extends this to locally operated SharePoint and Exchange servers.

That is the scenario many European governments have been asking about: a chatbot over internal documents with no data leaving the country or the building. Open models built for that market, such as Aleph Alpha's German-English Kolibri, are the kind of software such a catalogue could carry, though Microsoft named no partners for it.

GitHub and Copilot without the public cloud

GitHub Enterprise Local is meant to keep repositories, code and build artefacts under local control. Microsoft describes it as a validated GitHub Enterprise Server appliance running on Azure Local, so customers get a tested combination rather than assembling it themselves.

The more notable line is about Copilot. Microsoft says developers can use GitHub Copilot with locally hosted models for inference, bringing AI-assisted coding closer to their code and data. GitHub has been adding controls of this kind for enterprises, including local sandboxing for Copilot agents. Running the model itself on premises goes a step further for organisations that cannot send source code to any outside service.

The post does not say which models Copilot can use locally, how features compare with the cloud version, or whether any part of Copilot still needs a connection to GitHub's service. Those details will decide whether this suits a defence contractor's air-gapped network or only a bank's private data centre.

More control in Microsoft's own cloud

Not every customer wants to leave the public cloud, and many of the announcements are for them. A Sovereign Control Panel, entering public preview at Ignite, will show an organisation's sovereignty posture in the Azure portal, help apply and manage controls, flag gaps and assess how portable workloads are.

For customers in the European Union and the European Free Trade Association, Microsoft is rolling out Data Guardian, which adds oversight by a trusted EU partner, staffed by European residents, when Microsoft engineers remotely access in-scope production systems. A companion Production Touch Ledger, also in phased rollout in the EU and EFTA, keeps tamper-evident records of that access and what was done.

Encryption keys get a new option. External key management with Azure Managed HSM is now generally available, letting customers keep the root key in hardware they own on premises or with a trusted third party. Azure Confidential Clean Rooms, in limited preview, let several parties analyse shared sensitive data inside hardware-protected environments without exposing the raw data to each other.

Running when the connection drops

Resilience is the other theme. Microsoft is publishing sovereign business-continuity guidance and architecture patterns, and the ability to move workloads from connected to disconnected operation on its private cloud is entering public preview. The point is to keep critical services running if network, security or geopolitical conditions change.

The local data layer is filling out. SQL Server on Azure Local is already generally available for connected and disconnected use, while DocumentDB and Blob Storage on Azure Local enter public preview. Confidential virtual machines on Azure Local, with hardware-encrypted memory and attestation before keys are released, are now generally available.

Azure Local will also support multitenancy, so one set of servers can host separate tenants with their own resources and governance. Microsoft says that opens the door for local operators and service providers to sell their own sovereign cloud services on its infrastructure.

Partners, national clouds and the politics

The third layer is partners. National Partner Clouds, including Bleu in France, offer environments operated independently of Microsoft for customers that need a different ownership model. A graphic in Microsoft's post lists partners across the ecosystem, among them Mistral, NVIDIA, Dell, HPE, Intel, AMD, Accenture and Tata Consultancy Services.

The push comes as European regulators look harder at Microsoft's position. In the UK, the competition authority has proposed strategic market status for Microsoft's business software and Copilot. Offering customers more control and portability is partly a commercial answer to concerns about dependence on US cloud providers.

Phillips ties the AI angle to security, writing that as AI systems and agents interact with sensitive data and essential infrastructure, organisations need clear control over where they run, who operates them and what actions they can take. Microsoft has been building that kind of oversight elsewhere, including Guardian Agents in Project Perception.

What is still missing

Much of the announcement is a roadmap. Foundry Local, GitHub Enterprise Local and the Sovereign Control Panel arrive at Ignite rather than today, and Microsoft gave no prices, hardware requirements or exact dates.

The model catalogue is the biggest unknown for AI buyers. Running open-weight models locally is useful only if the catalogue includes capable models, if they fit on the hardware customers can buy, and if updates can be delivered to sites with no connection. Microsoft did not address any of those points.

Some controls are also regional. Data Guardian and the Production Touch Ledger are for the EU and EFTA, and Microsoft 365 Local is limited to approved customers. Buyers elsewhere will want to know whether those protections follow.

Even so, the direction is clear. Microsoft wants its AI tools, not just its servers, to run wherever a regulator or a security team says they must, including places with no internet at all.