Share via

Azure Purview Data Governance account creation fails with ResourceNotFound and no eligible location available

Moazzem Hossain 75 Reputation points
2026-05-06T19:26:58.6266667+00:00

I am trying to create a Microsoft Purview Data Governance account using Azure CLI, but the deployment is failing.

Command used:

az purview account create --name TBBD-Purview-DataGovernance --resource-group TBBD-Purview-RG

Error received:

(ResourceNotFound) The resource 'Microsoft.Purview/accounts/TBBD-Purview-DataGovernance' under resource group 'TBBD-Purview-RG' was not found.

Additional observations:

  • The Microsoft Purview resource provider is registered in the subscription
  • The resource group exists successfully
  • The Azure CLI purview extension is installed (preview)
  • The account creation fails consistently
  • No eligible location is available during the creation process
  • Supported service locations are returned as empty for the tenant

During multiple attempts, Azure indicates that no eligible location is available and supported service locations are empty for the tenant, which suggests a possible tenant-level limitation or missing service enablement for Microsoft Purview Data Governance.

Request:

I need help confirming whether this issue is caused by tenant-level service availability restrictions, region limitations, or missing Microsoft Purview Data Governance enablement. Also guidance on the correct prerequisites required to successfully create a Purview Data Governance account would be appreciated.

Microsoft Security | Microsoft Purview
0 comments No comments

1 answer

Sort by: Most helpful
  1. Pilladi Padma Sai Manisha 7,800 Reputation points Microsoft External Staff Moderator
    2026-05-07T08:50:46.87+00:00

    Hi Moazzem Hossain,
    it looks like the CLI can’t find any supported regions for your tenant, which usually means one of three things is going on:

    1. Tenant-level region restriction • By default the free-tier Purview account can only live in your Microsoft Entra home region, and you can only have one account per tenant unless you’ve been granted a quota increase or moved to the enterprise SKU.
    2. Missing CLI parameters • Unlike the portal, the CLI won’t prompt you for a location or SKU – if you don’t explicitly pass --location (and for non-free SKUs, --sku) it will report “no eligible locations.”
    3. Prerequisites not met • Even if your subscription shows Microsoft.Purview registered, you also need Microsoft.Storage (for the managed storage account) and Microsoft.EventHub (if you plan to enable the Kafka/Event Hubs integration), plus Contributor/Owner rights and no blocking Azure Policies on storage or Event Hubs.

    Here’s what you can try:

    1. Confirm you don’t already have a Purview account in this tenant • You can only create one free-tier account per tenant by default.
    2. Check your tenant’s home region and Purview availability • Look up “Supported regions” under Purview documentation (see ref list below) and make sure your location is listed for your tenant’s country/region.
    3. Explicitly register resource providers (if not already)
      
         az provider register --namespace Microsoft.Storage
      
         az provider register --namespace Microsoft.EventHub
      
         az provider register --namespace Microsoft.Purview
      
      
    4. Verify you have the right role • You need Owner or Contributor at the subscription level (or a custom role that allows creating storage, event hubs, and Purview accounts).
    5. Check for blocking Azure Policies • If there’s a deny policy on storage or Event Hubs, you’ll need to either disable it or create the “Purview exception” tag as outlined in the docs.
      
         az policy assignment list --scope /subscriptions/<your-subscription-id>
      
      
    6. Re-run the create command with location (and SKU if required):
      
         az purview account create \
      
           --name TBBD-Purview-DataGovernance \
      
           --resource-group TBBD-Purview-RG \
      
           --location <supported-region> \
      
           --sku Free \
      
           --managed-resource-group TBBD-Purview-DataGov-mrg
      
      
      • Replace <supported-region> with one from the region table for your tenant and change --sku to Standard if you’ve upgraded to enterprise.

    If after all that you still see “no eligible locations,” it’s almost certainly a tenant-side limit (either your free quota is already used or your home region isn’t enabled for Purview GA). In that case you can:

    • Open a support ticket to request region enablement or quota increase

    • Or upgrade to the enterprise SKU (which gives you a broader region list)

    Follow-up questions for you:

    • Do you already have a Purview account in this tenant?

    • What is your Microsoft Entra home region (you can see this in the Azure portal under Entra ID → Properties)?

    • Which region are you trying to deploy into?

    • Have you tried adding --location (and --sku) to your CLI command?

    • Do you have any Azure Policies blocking storage/Event Hubs in that subscription?

    References

    1. Create or delete a Microsoft Purview instance https://learn.microsoft.com/azure/purview/create-delete-instance
    2. Purview deployment checklist https://learn.microsoft.com/azure/purview/tutorial-azure-purview-checklist
    3. Register resource providers https://learn.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider
    4. Purview exception for Azure Policy https://learn.microsoft.com/azure/purview/create-azure-purview-portal-faq
    5. Create a Microsoft Purview account (portal quickstart) https://learn.microsoft.com/azure/purview/create-catalog-portal
    6. Regions supported by Microsoft Purview https://learn.microsoft.com/purview/data-governance-purview-portal#regions
    7. Quotas and limits (one free account per tenant) https://learn.microsoft.com/purview/data-governance-purview-portal-faq#can-i-create-new-microsoft-purview-accounts-in-my-subscription-
    8. Azure Policy overview https://learn.microsoft.com/azure/governance/policy/overview

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.