Microsoft Security | Microsoft Entra | Other
Additional Microsoft Entra services and features related to identity, access, and network security
Microsoft Entra Domain Services provisioning fails in two regions after clean portal deployments
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 14.000000000000002%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
Robert Castles
31
Reputation points
Tenant ID: f13a93c0-dc63-4489-96f6-a3dc5dcd1d53 Subscription ID: 6ffdb3fd-2e5c-4707-a334-3a2ec6601ff1 Managed domain: g7294.onmicrosoft.com
Microsoft Entra Domain Services provisioning fails after portal-only Standard SKU deployments in both East US 2 and East US. The resource creation operation initially reports success, remains Deploying for hours, then the managed domain resource changes to Failed.
The East US deployment used a newly created VNet/subnet and default AAD DS NSG. Configuration diagnostics reported the subnet as OK. Health reports no alerts, but Overview reports Failed. Resource diagnostic settings expose domain audit categories only and do not show provisioning-controller errors.
Relevant correlation IDs:
- East US 2 portal attempt:
08d8f411-6b42-48dc-b561-e8a15b6951c1 - Earlier East US attempt:
4a6ba948-1272-4639-9f65-deab9986e686
Please investigate the backend AAD DS provisioning failure for this tenant/subscription and advise whether a tenant or Azure Developer Program restriction is preventing managed-domain creation.
Microsoft Security | Microsoft Entra | Other
Sign in to answer