🚨 Azure Error: 'NoRegisteredProviderFound' — Cause, Fix, and Troubleshooting Guide

What this error means

Azure Resource Manager returns NoRegisteredProviderFound when it cannot match your request to a registered resource provider for the given resource type at the requested location and API version. Either the provider is not registered on the subscription, or the type is not offered in that region, or the api-version you asked for is not supported there. The literal error:

{
  "error": {
    "code": "NoRegisteredProviderFound",
    "message": "No registered resource provider found for location 'westus3' and API version '2023-05-01' for type 'flexibleServers'. The supported api-versions are '2021-06-01, 2022-01-01, 2023-06-01-preview'. The supported locations are 'eastus, eastus2, westus2, centralus, ...'."
  }
}

Helpfully, the message lists both the supported API versions and the supported locations for the type — the answer is almost always in that text.

What users report

• A deployment or az command fails with NoRegisteredProviderFound naming a location, an API version, and a resource type.
• The message enumerates “supported api-versions” and “supported locations” that differ from what you sent.
• A template that works in one region fails in another for the same resource type.
• A previously-working template breaks after pinning a newer apiVersion that a region has not received yet.

Tenant and app configuration causes

• Provider not registered — the Microsoft.* resource provider is in NotRegistered state on the subscription, so no location/version resolves.
• Type not offered in the region — the resource type (or the specific sub-type) is simply not available in the chosen location.
• Unsupported API version for the region — the pinned api-version exists globally but has not rolled out to that region, or is preview-only there.
• Preview feature not enabled — the type/version requires a preview feature flag registered on the subscription.
• Typo in type/namespace — a mistyped resource type resolves to no provider at all.

Confirming tenant configuration

Check the provider’s registration state first:

az provider show --namespace Microsoft.DBforPostgreSQL \
  --query "registrationState" -o tsv

If it is NotRegistered or Registering, that alone can cause the error. List which API versions the type actually supports:

az provider show --namespace Microsoft.DBforPostgreSQL \
  --query "resourceTypes[?resourceType=='flexibleServers'].apiVersions | [0]" -o json

And which locations the type is offered in:

az provider show --namespace Microsoft.DBforPostgreSQL \
  --query "resourceTypes[?resourceType=='flexibleServers'].locations | [0]" -o json

Compare those to the location and api-version in your template — the mismatch is the cause. Check for a required preview feature:

az feature list --namespace Microsoft.DBforPostgreSQL \
  --query "[?properties.state!='Registered'].{name:name, state:properties.state}" -o table

Resolution

Register the provider if it is not registered (registration is subscription-wide and idempotent):

az provider register --namespace Microsoft.DBforPostgreSQL
# poll until Registered
az provider show --namespace Microsoft.DBforPostgreSQL --query registrationState -o tsv

Use a supported region for the type — pick one from the “supported locations” list the error printed:

az postgres flexible-server create \
  --resource-group data-rg --name pg-prod \
  --location eastus2 --tier Burstable --sku-name Standard_B1ms

Pin a supported API version. In Bicep/ARM, set apiVersion to one the region supports (from the diagnose step):

resource pg 'Microsoft.DBforPostgreSQL/flexibleServers@2023-06-01-preview' = {
  name: 'pg-prod'
  location: 'eastus2'
  // ...
}

Register any required preview feature, then re-register the provider so the feature takes effect:

az feature register --namespace Microsoft.DBforPostgreSQL --name <feature-name>
az provider register --namespace Microsoft.DBforPostgreSQL

Avoiding tenant drift

• Provider registration is subscription-wide, not per-RG. Register once per subscription; do not re-register per deployment.
• Preview API versions are region-gated. A -preview api-version may exist in the docs but not in your region; the error’s list is authoritative.
• NoRegisteredProviderFound vs MissingSubscriptionRegistration. The latter fires when the provider is flatly unregistered; this one also covers region/api-version mismatches even when the provider is registered.
• Registration takes time. After az provider register, allow the state to reach Registered before deploying, or the same error recurs.

Related tenant errors

• MissingSubscriptionRegistration — the provider-not-registered case in its purest form.
• InvalidTemplateDeployment — pre-flight template validation wrapping errors like this one.
• InvalidResourceReference — a referenced resource id that ARM cannot resolve.