Microsoft Sovereign Cloud Adds Disconnected Azure Local

Introduction: why this matters

Digital sovereignty requirements are increasingly colliding with modern operational needs—especially for governments, defense, critical infrastructure, and regulated industries that must operate in isolated or intermittently connected networks. Microsoft’s latest Sovereign Cloud updates aim to reduce the tradeoff between strict isolation and cloud-like governance, productivity, and AI capabilities by extending a full stack that can run even when completely disconnected.

What’s new

1) Azure Local: disconnected operations (now available)

Azure Local adds support for running mission-critical infrastructure with Azure governance and policy controls without cloud connectivity.

Key capabilities:

• Local management and policy enforcement that stays inside the customer-operated environment
• Azure-consistent operational model (familiar governance and control posture) applied to on-premises workloads
• Designed to scale from smaller footprints to data-intensive and AI-driven workloads

2) Microsoft 365 Local: disconnected (now available)

Microsoft 365 Local brings core productivity server workloads into the sovereign boundary, running on Azure Local:

• Exchange Server
• SharePoint Server
• Skype for Business Server

Microsoft notes these core server products are supported through at least 2035, enabling long-term planning for environments that cannot rely on cloud services.

3) Foundry Local: large model support for disconnected AI

Foundry Local expands to support large multimodal models running on customer-owned hardware inside sovereign environments. With modern infrastructure (including GPUs from partners like NVIDIA), customers can:

• Run local AI inferencing behind strict sovereign boundaries
• Use local APIs without data leaving the environment
• Receive Microsoft support for deployments, updates, and operational health

Impact for IT administrators

For admins managing high-assurance environments, the biggest shift is the ability to standardize governance and operations across connectivity modes:

• Consistent policy and governance patterns across connected, hybrid, intermittently connected, and fully disconnected deployments
• Improved business continuity for isolated networks where external dependencies are unacceptable
• A clearer path to deliver collaboration + infrastructure + AI as an integrated, locally operated stack
• Better alignment with sovereignty mandates by keeping data, identities, and operations within controlled boundaries

Action items / next steps

• Assess workload placement: identify which services must run fully disconnected vs. intermittently connected.
• Evaluate Azure Local disconnected operations for policy/governance requirements and operational continuity needs.
• Plan Microsoft 365 Local deployment if you need on-prem email, content, and collaboration in isolated environments.
• Engage Microsoft for Foundry Local if you have qualified requirements for large-model inferencing, and validate hardware (GPU) and capacity needs.

Azure Local disconnected operations and Microsoft 365 Local disconnected are available worldwide now, while large models on Foundry Local are available to qualified customers.