Azure Local & disconnected operations
Running Azure with a fully on-premises control plane — architecture, identity, PKI, and lifecycle for classified, regulated, and isolated environments.
Connected vs. disconnected is an architecture decision, not a toggle
Connected Azure Local still talks to Azure for management, policy and Arc services. Disconnected operations moves that control plane on-site: identity, policy enforcement, and the Arc resource bridge all run locally, and an Azure subscription stays in the picture only for billing and licensing. The hardware sizing, the identity design, and the update workflow are all different the moment you choose disconnected — it isn't a flag you flip later.
The Arc resource bridge is present either way — what changes is whether Azure also owns the management and policy plane.
Registering the cluster and the resource bridge
The structural pattern: an azurerm_stack_hci_cluster registration for the Azure Local cluster itself, and the Arc resource bridge that exposes Arc-enabled VMs and AKS from the local control plane. azurerm doesn't yet cover the resource bridge directly, so it goes through azapi. Check current resource provider API versions on Microsoft Learn before deploying — this stack moves fast.
resource "azurerm_stack_hci_cluster" "sovereign_cluster" {
name = "azlocal-sov-site01"
resource_group_name = azurerm_resource_group.edge.name
location = "westeurope"
client_id = azuread_application.hci_cluster.client_id
tenant_id = data.azurerm_client_config.current.tenant_id
}
# Arc resource bridge - the local control plane that lets Azure Local
# expose Arc-enabled VMs and AKS even when the site runs disconnected
resource "azapi_resource" "resource_bridge" {
type = "Microsoft.ResourceConnector/appliances@2024-02-01"
name = "arcbridge-sov-site01"
location = "westeurope"
parent_id = azurerm_resource_group.edge.id
body = {
properties = {
distro = "AKSEdge"
infrastructureConfig = {
provider = "HCI"
}
}
}
}
Bicep
resource sovereignCluster 'Microsoft.AzureStackHCI/clusters@2024-04-01' = {
name: 'azlocal-sov-site01'
location: 'westeurope'
properties: {
aadClientId: hciClusterAppId
aadTenantId: tenant().tenantId
}
}
resource resourceBridge 'Microsoft.ResourceConnector/appliances@2024-02-01' = {
name: 'arcbridge-sov-site01'
location: 'westeurope'
properties: {
distro: 'AKSEdge'
infrastructureConfig: {
provider: 'HCI'
}
}
}
Latest on Azure Local
Azure Just Set a Retirement Date for Arc's Key Vault Secrets Provider — Its Replacement Doesn't Support a Single Sovereign Cloud
Microsoft retires the Azure Key Vault Secrets Provider extension for Arc-enabled Kubernetes on October 9, 2027. Its recommended replacement, built for disconnected clusters, documents zero sovereign cloud support.
Read article →Azure Local 2608's Key Vault Split: A New BYOK Preview, and a KMS Warning Nobody's Enforcing
Multi-rack deployments can now supply their own key to encrypt secrets before Key Vault ever sees them — alongside an unresolved AKS Arc KMS v1 deprecation warning.
Read article →Rack-Aware Clustering: Azure Local's Answer to "We Can't Replicate Outside This Building"
Two racks, one storage pool, no second site required — here's what the second local availability zone architecture actually requires.
Read article →Azure Local 2608: The Portal Finally Manages the Fleet — But Not the Disconnected Half
Arc Site Manager, portal-driven node scale-out, and GPU management from Azure all assume a live connection — the exact half of the sovereignty story they don't touch.
Read article →