Edit

Azure IoT Operations in Azure Government (preview)

Azure Government is a dedicated cloud for US government agencies and their partners. Azure IoT Operations is available in preview in Azure Government.

This article describes Azure IoT Operations in Azure Government. It explains how Azure IoT Operations differs from global Azure, and how to deploy it. For everything not covered in this article, follow the rest of the Azure IoT Operations documentation.

Important

Azure IoT Operations in Azure Government is currently in preview. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability. Azure IoT Operations is generally available in global Azure. That general availability doesn't extend to Azure Government until this preview ends.

Supported region

Azure IoT Operations supports Arc-enabled clusters in the following Azure Government region:

Region CLI value
US Gov Virginia usgovvirginia

Connect your cluster to Azure Arc in this region. Create the Azure IoT Operations instance, Azure Device Registry namespace, and schema registry in this region.

Data flow destinations, like Azure Data Lake Storage or Azure Event Hubs, can be in any Azure Government region where that service is available. Azure IoT Operations in Azure Government can't use resources in global Azure.

Supported versions

Azure IoT Operations in Azure Government starts with the 2610 release (version 1.5.x). Earlier versions aren't available. Azure Government includes the features that are generally available in global Azure for each release.

Features that are in preview in global Azure aren't available in Azure Government. Azure Government receives new versions after they're released in global Azure, so the latest version in global Azure might not be available yet.

To check which versions you can deploy, run az iot ops get-versions after you connect to Azure Government.

Feature availability

All generally available Azure IoT Operations features in global Azure are also available in Azure Government, except for the features listed in the following table:

Feature Global Azure Azure Government
Azure portal experience for Azure IoT Operations, including deployment, instance management, and the Azure IoT Operations pages for devices, assets, and data flows Generally available Not available. Use the Azure CLI, ARM or Bicep templates, or the operations experience.
Azure IoT Operations features in preview in global Azure Preview Not available
Azure Device Registry features in preview in global Azure, including live data (observability sessions) for assets, and preview API versions such as 2026-11-02-preview Preview Not available
Assets and asset endpoint profiles that aren't in a namespace, and their discovered equivalents (Microsoft.DeviceRegistry/assets, assetEndpointProfiles, discoveredAssets, discoveredAssetEndpointProfiles). Azure IoT Operations versions earlier than 1.2 use these resources. Supported for existing deployments Not available. Use namespaced assets, devices, discovered assets, and discovered devices (Microsoft.DeviceRegistry/namespaces/*).
Azure Container Storage enabled by Azure Arc edge volumes, and the features that use them: local storage data flow endpoints that write to local shared or cloud ingest volumes, and media connector uploads of snapshots and clips to cloud storage Supported Not available. Local storage endpoints and media connector file output can still write to a persistent volume claim from another storage class, but the data isn't synchronized to the cloud.

You can still use the Azure Government portal (portal.azure.us) for the Azure resources that Azure IoT Operations uses, like resource groups, Arc-enabled clusters, key vaults, storage accounts, and managed identities.

When other Azure IoT Operations articles show steps in the Azure portal, use the Azure CLI or operations experience equivalent instead.

Supported API versions

If you use ARM or Bicep templates, or call the REST API directly, use these API versions in Azure Government:

Resource provider API version
Microsoft.IoTOperations 2026-10-01
Microsoft.DeviceRegistry (namespaces, devices, assets, discovered devices, discovered assets) 2026-04-01
Microsoft.DeviceRegistry (schema registries, schemas, schema versions) 2025-10-01

Dependencies

Azure IoT Operations in Azure Government uses the same dependencies as global Azure:

  • Azure Arc-enabled Kubernetes, with custom locations and workload identity
  • Azure Device Registry and schema registry
  • Azure Key Vault Secret Store extension
  • Azure Monitor pipeline

Azure Container Storage enabled by Azure Arc, an optional dependency in global Azure, isn't available in Azure Government. For the affected features, see Feature availability.

Connect to Azure Government

Before you run any Azure CLI commands in the Azure IoT Operations documentation, set the cloud to Azure Government and sign in:

az cloud set --name AzureUSGovernment
az login

To confirm the active cloud, run az cloud list --output table. The isActive column for AzureUSGovernment should be true. For more information, see Connect to Azure Government with Azure CLI.

Deploy Azure IoT Operations

The test and production deployment articles use the Azure portal to generate the deployment commands. Because the portal experience isn't available in Azure Government, run the commands yourself.

Prerequisites

Set variables

LOCATION="usgovvirginia"
RESOURCE_GROUP="<RESOURCE_GROUP>"
CLUSTER_NAME="<CLUSTER_NAME>"
INSTANCE_NAME="<INSTANCE_NAME>"
STORAGE_ACCOUNT="<STORAGE_ACCOUNT>"
SCHEMA_REGISTRY="<SCHEMA_REGISTRY>"
SCHEMA_REGISTRY_NAMESPACE="<SCHEMA_REGISTRY_NAMESPACE>"
ADR_NAMESPACE="<ADR_NAMESPACE>"

Create a schema registry and namespace

  1. Create a storage account with hierarchical namespace enabled, and a schema registry that uses it. This command requires Microsoft.Authorization/roleAssignments/write permission on the resource group.

    az storage account create --name $STORAGE_ACCOUNT --resource-group $RESOURCE_GROUP --location $LOCATION --sku Standard_LRS --kind StorageV2 --enable-hierarchical-namespace true
    
    az iot ops schema registry create --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP \
      --registry-namespace $SCHEMA_REGISTRY_NAMESPACE \
      --sa-resource-id $(az storage account show --name $STORAGE_ACCOUNT --resource-group $RESOURCE_GROUP -o tsv --query id)
    

    For storage account requirements, see Schema registry and storage.

  2. Create an Azure Device Registry namespace:

    az iot ops ns create --name $ADR_NAMESPACE --resource-group $RESOURCE_GROUP
    

Deploy

  1. Prepare the cluster. You only need to run this command once per cluster.

    az iot ops init --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP
    

    If you use your own certificate authority issuer, see Bring your own issuer first.

  2. Create the Azure IoT Operations instance:

    az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name $INSTANCE_NAME \
      --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP -o tsv --query id) \
      --ns-resource-id $(az iot ops ns show --name $ADR_NAMESPACE --resource-group $RESOURCE_GROUP -o tsv --query id)
    

    To configure broker cardinality, memory profile, the connector for OPC UA, or other options, add the parameters described in az iot ops create and Azure CLI support for advanced MQTT broker configuration.

At this point, the instance has test settings. For production, continue with the next section.

Enable secure settings

  1. Set variables for the key vault and the two user-assigned managed identities. Use one identity for secrets and a separate one for cloud connections.

    KEYVAULT_NAME="<KEYVAULT_NAME>"
    SECRETS_MI_NAME="<SECRETS_MI_NAME>"
    CLOUD_MI_NAME="<CLOUD_CONNECTIONS_MI_NAME>"
    
  2. Create a key vault that uses Azure role-based access control, and give your account permission to manage secrets:

    az keyvault create --name $KEYVAULT_NAME --resource-group $RESOURCE_GROUP --location $LOCATION --enable-rbac-authorization true
    
    az role assignment create --assignee $(az ad signed-in-user show --query id -o tsv) \
      --role "Key Vault Secrets Officer" \
      --scope $(az keyvault show --name $KEYVAULT_NAME --query id -o tsv)
    
  3. Create the managed identities:

    az identity create --name $SECRETS_MI_NAME --resource-group $RESOURCE_GROUP --location $LOCATION
    az identity create --name $CLOUD_MI_NAME --resource-group $RESOURCE_GROUP --location $LOCATION
    
  4. Enable secret sync:

    az iot ops secretsync enable --instance $INSTANCE_NAME --resource-group $RESOURCE_GROUP \
      --mi-user-assigned $(az identity show --name $SECRETS_MI_NAME --resource-group $RESOURCE_GROUP --query id -o tsv) \
      --kv-resource-id $(az keyvault show --name $KEYVAULT_NAME --query id -o tsv)
    
  5. Assign the cloud connections identity to the instance. If you plan to use data flow graphs, add --usage wasm-graph.

    az iot ops identity assign --name $INSTANCE_NAME --resource-group $RESOURCE_GROUP \
      --mi-user-assigned $(az identity show --name $CLOUD_MI_NAME --resource-group $RESOURCE_GROUP --query id -o tsv)
    
  6. Restart the schema registry pods to apply the new identity:

    kubectl rollout restart statefulset adr-schema-registry -n azure-iot-operations
    

For more about these steps, see Enable secure settings.

Verify the deployment

az iot ops check

For more about the output, see Verify deployment.

Operations experience

Use the operations experience web UI to manage sites, devices, assets, and data flows. In Azure Government, go to https://portal.iotoperations.azure.us and sign in with your Azure Government account.

For more information, see Use the operations experience web UI.

Endpoint differences

Azure Government uses different endpoints than global Azure. Where Azure IoT Operations articles show a global Azure host name or audience, use the Azure Government value:

Service Global Azure Azure Government Where Azure IoT Operations uses it
Azure Resource Manager management.azure.com management.usgovcloudapi.net REST calls, templates, the --audience value for registry endpoints
Microsoft Entra ID login.microsoftonline.com login.microsoftonline.us Sign-in and token requests
Azure Key Vault *.vault.azure.net *.vault.usgovcloudapi.net Secret sync
Azure Blob Storage *.blob.core.windows.net *.blob.core.usgovcloudapi.net Schema registry storage
Azure Data Lake Storage Gen2 *.dfs.core.windows.net *.dfs.core.usgovcloudapi.net Data flow endpoints
Azure Event Hubs (Kafka) *.servicebus.windows.net *.servicebus.usgovcloudapi.net Data flow endpoints
Azure Event Grid MQTT broker *.eventgrid.azure.net *.eventgrid.azure.us Data flow endpoints
Azure Data Explorer *.kusto.windows.net *.kusto.usgovcloudapi.net Data flow endpoints
Microsoft Fabric OneLake onelake.dfs.fabric.microsoft.com onelake.dfs.fabric.microsoft.us Data flow endpoints
Azure Container Registry *.azurecr.io *.azurecr.us Registry endpoints, private image mirrors
Operations experience iotoperations.azure.com portal.iotoperations.azure.us Operations experience web UI

For other services, run az cloud show --name AzureUSGovernment or see Azure Government guidance for developers.

Network requirements

If you use enterprise firewalls or proxies, allow the following endpoints before you deploy: