Microsoft expands sovereign cloud plans for local AI and operational control

Microsoft on October 20 outlined an expansion of its sovereign cloud portfolio, including plans to make Foundry Local and GitHub Enterprise Local generally available at Microsoft Ignite. Foundry Local will support connected and disconnected operations on Azure Local with a broader model catalog. GitHub Enterprise Local will be a validated GitHub Enterprise Server appliance on that infrastructure, keeping repositories and development artifacts within environments operated by customers.

The company also announced public previews for DocumentDB and Blob Storage on Azure Local and for moving workloads from connected to disconnected operation. A Sovereign Control Panel will enter public preview at Ignite. Microsoft said external key management with Azure Managed HSM is now generally available, allowing the root encryption key to remain on hardware operated by customers or a trusted third party. These releases have different schedules: the Ignite milestones remain forthcoming, while the announcement describes the external key capability as already available.

The portfolio dates to June 2025, when Microsoft introduced its broader sovereign cloud offering for European organizations. Its architecture combined public cloud controls, customer-operated private infrastructure and independently operated national partner clouds. Data Guardian, external key management and Microsoft 365 Local were among the capabilities announced then. The public cloud approach extended the earlier Microsoft Cloud for Sovereignty, while the private option used Azure Local to bring infrastructure and productivity server workloads into customer-controlled locations. The October announcement therefore advances an existing platform rather than introducing sovereign cloud or local AI for the first time.

Disconnected deployment also predates the latest update. In February, Microsoft made Azure Local disconnected operations and Microsoft 365 Local disconnected available worldwide, with large models on Foundry Local available to qualified customers. Azure Local placed management, policy enforcement and workload execution inside the customer environment, reducing dependence on a continuous public cloud connection. The productivity component brought Exchange Server, SharePoint Server and Skype for Business Server into that operational boundary. Microsoft described local multimodal inference using modern partner hardware, including NVIDIA infrastructure. That earlier release established the offline foundation that the newly announced transition capability builds upon.

Microsoft enlarged the underlying infrastructure in April, announcing support for deployments of up to thousands of servers inside one sovereign environment. The expansion targeted larger datacenters, industrial sites and edge deployments handling demanding AI and data workloads. GPU support allowed inference and analytics to run within customer-controlled infrastructure while retaining access management, auditing and compliance controls locally. Expanded fault domains and infrastructure pools were intended to contain the impact of hardware failures. That scale announcement addressed the capacity of private deployments, a separate consideration from the application and control features detailed this week.

The operational emphasis also follows Microsoft's European resilience commitments. In an April progress report, the company said it had completed the EU Data Boundary and extended European processing commitments to AI productivity services. It also reported making its Digital Resilience Commitment legally binding in contracts with European national governments and the European Commission, including a promise to challenge government orders to halt European cloud operations in court. Those measures concern data processing and service continuity alongside the technical deployment choices.

Microsoft's documentation describes Sovereign Control Panel as the successor to Regulated Environment Management. The console gathers sovereignty information across Azure resources, combining Azure Policy evaluations with direct checks of resource configurations. Its intended functions include measuring residency, confidentiality, operational control and continuity, applying organizational requirements, and identifying resources that drift from the expected state. The new preview milestone concerns access to that unified oversight experience.