A secure data center glows with digital infrastructure and cloud-computing security icons.
Microsoft's Ignite 2026 Sovereign Private Cloud announcements are mostly about Azure Local. The company is trying to make Azure Local work as a complete platform for AI, databases, developer tools and migration inside customer-controlled datacenters. The list mixes generally available features, public previews, "coming soon" items and hardware promises. Anyone planning a deployment needs to keep those categories separate.

A secure data center glows with digital infrastructure and cloud-computing security icons. The big picture​

Microsoft's Azure Arc blog (post dated November 17, 2026) describes Sovereign Private Cloud as Azure infrastructure, services and AI capabilities running in customer-controlled environments, built on Azure Local. This follows the Frontier Tour announcements last month. The headline items are:

  • GA on Azure Local: Foundry Local, confidential VMs (AMD SEV-SNP), SQL Server, GitHub Enterprise Local and Trusted Launch VM migration.
  • Preview: the agent service, guardrails with a choice of guardrail model, Intel TDX confidential VMs, connected-to-disconnected transitions, DocumentDB and Blob Storage.
  • Later or limited: NVIDIA HGX B300 systems, multitenancy, a new VMware migration data plane, and private endpoints for migration.

Microsoft's own Learn documentation describes the architecture. Azure Local is the foundation. It provides the compute, storage, networking and lifecycle management layer that the sovereign solutions depend on. It runs workloads as VMs or on Arc-enabled AKS clusters.

Sovereign AI: Foundry Local goes GA​

Foundry Local on Azure Local is now generally available. It runs AI models near the data, with local inference in both connected and disconnected environments. Microsoft Learn describes the deployment model as Arc-enabled Kubernetes with OpenAI-compatible APIs, so data stays on-premises.

The release goes beyond plain inference:

  • Model catalog: a growing set of models run locally.
  • Agentic retrieval: local ingestion, indexing and search, plus agents, tool calling, an MCP server and a built-in chat experience.
  • Agent service (preview): build and orchestrate agents, including in fully disconnected environments.
  • Guardrails (preview): apply the guardrail model of your choice.

Ahead of Ignite, coverage of Microsoft's October 20 sovereign cloud update said the catalog would span Microsoft, partner, open-weight and open-source models.

Hardware: NVIDIA HGX B300​

Azure Local is expanding hardware support to NVIDIA HGX B300 systems. The target is large-scale multi-GPU inference and agentic workloads, including bring-your-own models. Dell, HPE and Lenovo will supply validated systems. Microsoft says details will come "as these systems become available." That is a roadmap commitment, not a purchase order you can place today.

A "disconnected" caution​

"Local" does not automatically mean "air-gapped on day one." The Foundry Local documentation has a separate disconnected-operations track, with its own preparation and deployment steps. Check that track before you promise anyone a fully isolated deployment.

Confidential VMs: GA, with caveats​

Confidential VMs using AMD SEV-SNP are generally available on supported AMD EPYC processors. They provide hardware-backed memory encryption and attestation. Intel TDX-based confidential VMs on Xeon are in preview.

Microsoft's Learn overview of confidential VMs, last updated November 2, 2026, shows what that means in practice:

  • They bring hardware-based memory encryption and attestation to customer-owned edge infrastructure.
  • The trust boundary excludes host administrators. That covers threats such as compromised host operating systems and malicious datacenter staff with console access.
  • TEEs such as SEV-SNP don't protect against sophisticated physical side-channel attacks. Microsoft recommends combining them with physical safeguards.

The same page documents limits that may or may not have changed with the GA announcement:

  • The current release supports Linux guests only (Ubuntu 24.04 using Microsoft's integrity-protected script). Windows CVM guest support isn't available.
  • Validated hardware is listed as the Lenovo ThinkAgile MX455 V3 Edge PR and the HPE ProLiant DL145 Gen11, on AMD Gen 4 EPYC.
  • Cloud connectivity is required for Azure Attestation and secure key release through Azure Key Vault.
  • Running CVMs can't be migrated, and guest management isn't supported.
  • Windows Update isn't a supported update path.

The page also notes the feature is available only in Azure Local 2607 or later. I couldn't confirm whether the GA announcement relaxed any of these limits, so verify against current deployment documentation. The attestation dependency matters most for the "even when fully disconnected" pitch.

Operations: moving the control plane​

Microsoft says Azure Local customers can move their management control plane without redeploying infrastructure, migrating data or interrupting running workloads. VMs, AKS clusters, applications and storage stay in place. A related preview lets existing Azure-connected deployments move to locally managed, disconnected operation. This is a management-plane change. It does not mean every Azure-dependent integration keeps working unchanged once you disconnect.

Data services​

  • SQL Server on Azure Local: generally available, in connected and disconnected environments.
  • DocumentDB: preview, for document-oriented applications. Microsoft's German TechWiese blog describes it as a MongoDB-compatible open-source document database for JSON workloads.
  • Blob Storage: preview, for cloud-native object storage that keeps unstructured data local.

The announcement doesn't give preview enrollment conditions or hardware requirements for these.

GitHub Enterprise Local: GA claim, stale docs​

Microsoft says GitHub Enterprise Local is generally available. It brings GitHub Enterprise Server to Azure Local as a prebuilt virtual appliance. Repositories, CI/CD and artifacts stay inside the customer's boundary. In connected environments, developers can use GitHub Copilot with locally hosted repositories. In disconnected ones, Foundry Local provides AI assistance with locally hosted models.

There is a discrepancy to be aware of. The Microsoft Learn overview page I reviewed, last updated June 2, 2026, still labels the feature as preview. That page likely predates the GA announcement, and I couldn't confirm an update. Treat the Ignite blog as Microsoft's current statement and check the live docs before you commit.

The Learn page also gives useful planning details:

  • It provides source management, pull requests, GitHub Actions through self-hosted runners, Packages and Advanced Security.
  • Actions logs and artifacts need external object storage, such as Azure Blob Storage or an S3-compatible endpoint.
  • Billing has three separate parts: seat-based GitHub Enterprise licensing, per-physical-core Azure Local billing, and separate pricing for AI services such as Copilot and Foundry.

Migration to Azure Local​

Azure Local migrations now live in the unified Azure Catalyst experience (formerly Azure Migrate to Azure Local). It handles discovery, replication and tracking for VMware and Hyper-V migrations. Other changes:

  • New VMware data plane (preview by year-end): built on VMware SCSI HotAdd, it removes the VDDK dependency for supported scenarios. Existing VDDK-based projects remain supported.
  • Arc resource preservation: supported migrations keep Arc-enabled server resources, including RBAC assignments, policies, tags, monitoring configurations and extensions.
  • Private endpoints: GA is targeted for Q1 CY2027. That is a target, not a date.
  • Trusted Launch VM migration: generally available for eligible workloads.

Multitenancy and partners​

Multitenancy on Azure Local is "coming soon." It offers logical isolation so enterprises and service providers can share infrastructure while separating tenants, teams and workloads. Initial access is limited to qualified customers, and no GA date or isolation details were given. If you were considering Azure Local for a managed-service offering, this is not yet something to build on.

Microsoft also launched an Azure Local for Hybrid and Sovereign Private Cloud specialization in the Cloud Partner Program. The ten initial partners are abtis, Acuutech, Dell, HCLTech, Impresoft 4ward, kloud klickers, Lenovo, NTT DATA, PulsivIT and Twoday. Microsoft is also working with ISVs and global systems integrators on validated applications, but it didn't name any.

What admins should do​

  1. Sort every feature into GA, preview or planned. Only build production plans on the GA items.
  2. Check hardware. Confidential VMs list specific validated servers, and HGX B300 systems aren't yet available.
  3. Map connectivity dependencies. Attestation and key release for confidential VMs need cloud connectivity, per the current documentation.
  4. Confirm the GitHub Enterprise Local status in live docs and licensing.
  5. Pilot the previews (agent service, DocumentDB, Blob Storage, connected-to-disconnected transition) in non-production first.

Analysis​

This is a coherent push. Microsoft is answering demand for data and AI control by making Azure Local a platform that covers inference, data, developer tooling and migration. The caveat is that much of the source material is vendor messaging. It tends to say "even when fully disconnected" while the documentation still lists connectivity prerequisites. The sensible reading is that the stack is maturing quickly but is uneven, so test it against your own sovereignty requirements.

 

References

  1. What's new with Sovereign Private Cloud at Microsoft Ignite 2026 Azure Arc Blog 2026-11-17T18:46:55+00:00
  2. What's new with Sovereign Private Cloud at Microsoft Ignite 2026 | Microsoft Community Hub techcommunity.microsoft.com
  3. What is Sovereign Private Cloud? | Microsoft Learn learn.microsoft.com