Microsoft offers two very different routes to a "sovereign" Azure: Azure Government, a physically isolated US cloud with its own identity authority and endpoints, and Sovereign Public Cloud in Europe, which adds the EU Data Boundary, operational controls and customer-held keys to the ordinary Azure regions. Teams that confuse the two end up with tenants that cannot collaborate, applications registered in the wrong directory, and sensitive data leaking through resource names that sit outside the compliance boundary. This guide covers how identity works in each environment, who should hold privileged roles, the service principals and keys involved, Customer Lockbox and other access controls over Microsoft personnel, logging, and a hardening baseline. It is for cloud architects, identity engineers and compliance leads in US public sector, defence supply chains and European regulated sectors. The wider legal picture is in the Data Sovereignty and Residency Guide; product facts here are from Microsoft Learn and Microsoft's published documentation sources as checked in October 2026.
This is an independent guide from NHI Mgmt Group, based on Microsoft's public documentation as of November 2026. It is not sponsored or reviewed by Microsoft. Product features change, so confirm settings against Microsoft's current documentation.
Key takeaways
- Azure Government is a separate cloud, not a region. It runs in physically isolated US datacentres and networks, limits potential access to systems processing customer data to screened US persons, and uses its own endpoints such as
portal.azure.us,management.usgovcloudapi.netandlogin.microsoftonline.us. Eligibility is validated. - The EU route keeps public Azure and adds controls. The EU Data Boundary commits Microsoft to store and process customer data and personal data for in-scope services within the EU and EFTA, subject to limited documented transfers; Sovereign Public Cloud adds sovereignty guardrails, Data Guardian logs, customer-controlled keys and the Sovereign Landing Zone.
- Choose the identity authority before you build. Azure Government subscriptions trust a Microsoft Entra Government tenant, but applications can authenticate users from Entra Public or Entra Government; register the app in the tenant whose users will sign in.
- Resource names are not protected data. Microsoft states that subscription, resource group, resource and tag names may be stored or accessed outside the compliance boundary for support, so never put ITAR, IL5 or CUI details in metadata.
- Microsoft access to your data is a governed path. Customer Lockbox requests wait up to four days for an approver with Owner, Azure Customer Lockbox Approver for Subscription or Global Administrator rights, and are logged in the Activity Log or Entra audit log.
How identity and access work in Azure Government and sovereign Azure
| Option | What it is | Identity plane | Typical fit |
|---|---|---|---|
| Azure Government | Physically isolated US cloud; FedRAMP High P-ATO and DoD SRG IL4 and IL5 provisional authorisations per Microsoft; regions US Gov Arizona, Texas and Virginia, plus US DoD regions | Microsoft Entra Government (login.microsoftonline.us), or Entra Public for some applications | US federal, state, local and tribal agencies and partners; ITAR, CJIS, IL4 and IL5 workloads |
| Azure Government Secret and Top Secret | Air-gapped clouds for classified workloads | Separate; not covered by the public comparison tables | Classified missions, through the account team |
| Global Azure with EU Data Boundary | Public Azure regions with residency commitments for in-scope regional services in EU Data Boundary regions | Microsoft Entra ID (public) | EU and EFTA organisations needing residency for customer data and pseudonymised logs |
| Sovereign Public Cloud | Public Azure plus sovereignty guardrails, operational transparency (EU-resident controlled access, Data Guardian logs) and customer-controlled keys | Microsoft Entra ID (public) | European governments and regulated industries |
| Sovereign Private Cloud and National Partner Clouds | Customer-run Azure Local infrastructure, or clouds operated by national partners | Depends on deployment | Disconnected or partner-operated requirements |
Azure Government is reached through its own endpoints. The authority is login.microsoftonline.us (with certauth.login.microsoftonline.us for certificate authentication), Azure Resource Manager is management.usgovcloudapi.net, Key Vault is vault.usgovcloudapi.net, Managed HSM is managedhsm.usgovcloudapi.net, and storage uses core.usgovcloudapi.net. Tools must be pointed at the right environment: the Azure CLI uses the AzureUSGovernment cloud and Azure PowerShell the AzureUSGovernment environment, and the Entra pass-through authentication agent and private network connector installers take ENVIRONMENTNAME="AzureUSGovernment". Code samples written for global Azure fail or, worse, authenticate against the wrong cloud if these are hard-coded.
- Identity authority choice: Microsoft's guidance is that an Azure Government application can use Entra Government identities (common where the organisation runs Microsoft 365 GCC High or DoD) or Entra Public identities (common with Microsoft 365 commercial or GCC). If you choose Entra Public users, register the app in the Entra Public tenant; registering it in the Government directory that the subscription trusts means the intended users cannot sign in.
- Feature differences: Azure AD B2C is not available in Azure Government, and MFA Trusted IPs is not supported; use Conditional Access named locations instead. See the Conditional Access Guide.
- B2B across clouds: B2B collaboration is not enabled by default across national cloud boundaries. Both tenants must enable the other cloud in Microsoft cloud settings and then configure inbound and outbound cross-tenant access. A US Government tenant's OpenID configuration shows
"tenant_region_scope":"USGOV"when B2B is supported and"USG"when it is not. See the Entra ID Cross-Tenant Access and B2B Guest Governance Guide. - Legacy authentication: lift-and-shift applications using Kerberos or NTLM need Active Directory domain controllers in Azure IaaS; Microsoft recommends read-only domain controllers where applications only need read access.
- EU residency and identity: for Azure, regional services deployed in EU Data Boundary regions are in scope, but non-regional services need separate configuration, and Azure Resource Manager must be configured if Professional Services Data is to stay in the boundary. Customer data excludes configuration information such as technical settings and resource names.
Admin roles and privileged access
Privileged access works as in global Azure (Entra roles, Azure RBAC, Privileged Identity Management), but two things change: the roles that approve Microsoft access to your data, and the separation between identities in different clouds.
| Role | Sovereignty relevance | Guidance |
|---|---|---|
| Global Administrator | Enables Customer Lockbox; approves tenant-scoped Lockbox requests | Two to four named accounts, phishing-resistant MFA, PIM activation, break-glass accounts per cloud |
| Subscription Owner | Approves subscription-scoped Lockbox requests | Avoid standing Owner; note that PIM-eligible Owners must activate before the request starts or they are not recognised |
| Azure Customer Lockbox Approver for Subscription | Approves Lockbox requests without full Owner rights | Assign to the security operations lead per subscription; management group scope is not supported |
| Key Vault and Managed HSM administrators | Control customer-managed keys that provide cryptographic separation (the IL5 approach) | Separate from subscription Owners; use RBAC, purge protection and logging |
| Policy and landing zone administrators | Maintain the guardrails that enforce location, encryption and configuration | Changes through pipelines with approval; see the Azure Policy and Management Groups Guide |
- One admin identity per cloud: do not reuse a commercial cloud admin account through B2B to administer Azure Government; keep privileged accounts native to each tenant, with their own break-glass pair. See the Break-Glass Account Guide.
- Screened personnel apply to Microsoft, not to you: Microsoft's screened US persons commitment covers its own staff. Your administrators' eligibility (for example ITAR US person requirements) remains your responsibility, enforced through HR process and Conditional Access.
Integrations, API tokens and service accounts
- Service principals and managed identities: they work the same way, but tokens are issued by the cloud's own authority, and resource audiences differ. Microsoft gives the example of IoT Hub, where Azure Government uses the audience
https://iothubs.azure.usrather thanhttps://iothubs.azure.net. Prefer managed identities to client secrets; see the Azure Managed Identities Security Guide and the Azure Entra Client Secrets Security Guide. - Pipelines: Azure DevOps service connections and GitHub workflows must target the Government environment explicitly. A pipeline identity that can deploy to both commercial and Government subscriptions is a bridge across the boundary; give each cloud its own identity.
- Hybrid identity: Entra Connect must be on the latest release for Azure Government, and its agents need Government URLs such as
*.msappproxy.us,*.servicebus.usgovcloudapi.netandlogin.windows.us. The sync service account is tier 0; see the Microsoft Entra Connect and Cloud Sync Hardening Guide. - Keys as the separation mechanism: for IL5, Microsoft describes DISA-approved logical separation by cryptographic means, with keys held in Key Vault in FIPS 140 validated HSMs and owned by the IL5 system owner; a service holding mixed data must use a dedicated key for IL5 data. In Europe, Sovereign Public Cloud lets customers manage keys in HSM-based key stores. See the Azure Key Vault Security Guide and the BYOK, HYOK and External Key Management Guide.
- Secrets in code: Microsoft's Azure Government security guidance is to keep only Key Vault URI references in code and templates, never secrets themselves.
Logging and detection
| Event | Where it is logged | Detection |
|---|---|---|
| Customer Lockbox request created, approved, denied, expired (subscription scope) | Azure Activity Log: Create Lockbox Request, Approve Lockbox Request, Deny Lockbox Request, Lockbox Request Expiry | Alert on every request; check approval matches an open support case |
| Customer Lockbox tenant-scoped request | Entra audit log, Service = Access Reviews (Create request, Request approved, Request denied) | Same as above; tenant-scoped access is more sensitive |
| Cross-cloud B2B settings or cross-tenant access changed | Entra audit log | High-severity alert; it widens who can reach the boundary |
| Policy assignment or exemption changed in sovereign landing zone | Activity Log | Alert on location, encryption and confidential computing policy changes |
| Key disabled, deleted or access policy changed | Key Vault and Managed HSM diagnostic logs | Alert, because key loss is data loss and key access is data access |
| Microsoft operational access in EU/EFTA (eligible customers) | Data Guardian logs | Review against support activity |
In Azure Government, Log Analytics and Microsoft Sentinel use Government endpoints (ods.opinsights.azure.us, api.loganalytics.us), so agents and forwarders configured for commercial endpoints silently send nothing. Confirm data arrival after deployment; see the Azure Monitor, Activity Log and Diagnostic Settings Guide. Lockbox history is no longer shown in the Lockbox portal History tab, so the Activity Log and Entra audit log are the record; retain them.
Metrics:
- Lockbox decisions made within four days, and the share approved with a matching support case.
- Policy compliance for location, encryption and confidential computing assignments in the sovereign landing zone.
- Resources holding regulated data encrypted with customer-managed keys, as a percentage.
- Naming violations found by scanning resource names and tags for restricted terms.
- Privileged accounts per cloud without PIM, phishing-resistant MFA or native tenant membership.
Hardening baseline
- Decide the route. US regulated (FedRAMP High, IL4, IL5, ITAR, CJIS): Azure Government. European residency and operational sovereignty: global Azure in EU Data Boundary regions with Sovereign Public Cloud controls. Disconnected or national-operator needs: Sovereign Private Cloud or a National Partner Cloud. Compare providers with the EU Sovereign Cloud Options Compared Guide.
- Design identity. For Azure Government, decide between Entra Government and Entra Public per application, document where apps are registered, and plan cross-cloud B2B only where required. For EU, confirm tenant country and billing address rules for each service family (Microsoft 365 customers with Multi-Geo are not in scope of the EU Data Boundary).
- Deploy guardrails as code. Use the Sovereign Landing Zone (Bicep or Terraform), an opinionated Azure Landing Zone variant that applies policy as code for residency, confidential computing and location controls, or an equivalent landing zone in Azure Government. See the Azure Landing Zones Security Guide.
- Set up keys before data. Create Key Vault or Managed HSM keys owned by the workload owner, with purge protection, and use a dedicated key per regulated data set.
- Enable Customer Lockbox. It needs a support plan of at least Developer and the Global Administrator role to enable. Assign Azure Customer Lockbox Approver for Subscription at subscription scope and set alternate notification email.
- Enforce naming rules. Publish a naming standard that forbids export-controlled, IL5 or CUI terms in subscription, resource group, resource, deployment and tag names, and scan for violations. See the CUI Guide.
- Pilot and verify. Deploy a test workload, confirm endpoints, token audiences, logging and policy effects, then migrate production. Rollback in Azure Government means moving workloads back to another cloud, which changes your authorisation boundary: treat it as a compliance decision, not a technical toggle.
Framework mapping
| Capability | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| Cloud choice and residency commitments | SA-9 | GV.OC-03, GV.SC-05 | A.5.23 Information security for use of cloud services, A.5.31 Legal, statutory, regulatory and contractual requirements |
| Customer Lockbox and provider access | AC-3, SA-9 | PR.AA-05 | A.5.19 Information security in supplier relationships |
| Customer-managed keys | SC-12, SC-28 | PR.DS-01 | A.8.24 Use of cryptography |
| Privileged roles per cloud | AC-2, AC-6, IA-2 | PR.AA-01, PR.AA-05 | A.8.2 Privileged access rights |
| Lockbox, policy and key logging | AU-2, AU-6 | DE.CM-03 | A.8.15 Logging |
Common misconfigurations
- App registered in the wrong tenant: an Azure Government app meant for Entra Public users, registered in the Government directory, fails sign-in. Record the intended authority per app.
- Sensitive data in metadata: project codes, programme names or export-controlled terms in resource or tag names leave the compliance boundary by Microsoft's own definition. Scan and rename.
- Commercial endpoints hard-coded: SDKs, agents and scripts pointed at
management.azure.comor commercial log endpoints break or send data to the wrong place. Parameterise the cloud environment. - Lockbox approvers that do not exist yet: role assignments made after a request starts are not recognised, and management group assignments are not supported. Assign approvers ahead of time at subscription scope.
- Assuming the EU Data Boundary covers everything: configuration data such as resource names is excluded, non-regional Azure services need separate configuration, and limited transfers continue. Read the scope before promising residency to a regulator.
- Bridging clouds with one identity: a shared pipeline or admin identity across commercial and Government tenants turns the weakest tenant into the way in. Federation trust abuse is covered in the Golden SAML and Federation Trust Abuse Defence Guide.
Practitioner checklist
- Record which cloud each workload uses and why, mapped to the obligation (FedRAMP, IL, ITAR, CJIS, EU Data Boundary).
- Document the identity authority and registration tenant for every application in Azure Government.
- Keep privileged accounts native to each tenant with PIM, phishing-resistant MFA and per-cloud break-glass accounts.
- Parameterise cloud environments in SDKs, CLI, PowerShell, Entra Connect agents and pipelines, and test endpoints.
- Enable Customer Lockbox, assign subscription-scope approvers in advance and alert on every request.
- Use customer-managed keys in Key Vault or Managed HSM for regulated data, with separate key administrators.
- Enforce a naming standard with no restricted information in resource names or tags.
- Deploy guardrails through the Sovereign Landing Zone or an equivalent policy-as-code baseline and monitor compliance.
- Confirm logs arrive at Government or EU workspaces and retain Lockbox records.
Standards and references
- Microsoft Learn: What is Azure Government?
- Microsoft Learn: Compare Azure Government and Global Azure
- Microsoft Learn: Planning Identity for Azure Government Applications
- Microsoft Learn: Isolation Guidelines for Impact Level 5 Workloads
- Microsoft Learn: Customer Lockbox for Microsoft Azure
- Microsoft Learn: What is the EU Data Boundary?
- Microsoft Learn: Sovereign Public Cloud Overview
- Microsoft Learn: Microsoft Entra B2B in Government and National Clouds
Related NHI Mgmt Group resources: Data Sovereignty and Residency Guide · Microsoft Azure Security Guide · FedRAMP Guide · AWS European Sovereign Cloud Guide