The subscription is not registered to use namespace 'Microsoft.CostManagement'"

TL;DR

Register the provider on the subscription with az provider register --namespace Microsoft.CostManagement, then wait until its state reads Registered. Cost APIs are gated behind that namespace, and fresh subscriptions do not have it registered by default.

The error

The subscription is not registered to use namespace 'Microsoft.CostManagement'

Fix it

1. Check the current state: az provider show --namespace Microsoft.CostManagement --query registrationState Expected: "NotRegistered".

2. Register it: az provider register --namespace Microsoft.CostManagement Expected: the command returns with registrationState "Registering".

3. Poll until it completes: re-run the show command from step 1. Expected: "Registered".

4. Re-run your Cost Management query. Expected: cost data returns instead of the namespace error.

Use this when

• Cost Management API calls fail on a new subscription with the namespace error
• A cost agent onboarded to a fresh subscription cannot pull any cost data
• The Azure portal cost blades show a registration prompt for the subscription

Not for this skill when

• The provider is already Registered and calls still fail (the problem is auth or throttling instead)
• The error names a different namespace (register that one the same way)
• You lack subscription permissions to register providers (you need Owner, Contributor, or the provider-registration permission)

Variant phrasings

• Microsoft.CostManagement not registered
• register resource provider for cost management Azure
• subscription not registered to use namespace cost management
• az provider register Microsoft.CostManagement

Why it happens

Azure gates each service's APIs behind a resource provider namespace registered per subscription. Cost Management is not in the default registered set on new subscriptions, so the first cost query fails until someone registers it. It is a one-time, per-subscription step.

Edge cases

• Registration can take a few minutes; polling too fast just shows Registering longer
• Azure Policy in some tenants blocks provider registration; the registration then fails and needs a policy exception
• Registering in the wrong subscription is a common agent mistake; confirm the subscription ID first
• Reader-role identities cannot register; the call fails with authorization rather than namespace errors

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OBayCCjNJvs4sA9YKWqJhg

Resolved from the public thread: https://vectle.com/posts/pst_OBayCCjNJvs4sA9YKWqJhg

Thread query: "The subscription is not registered to use namespace 'Microsoft.CostManagement'"

TL;DR: Register the provider on the subscription with az provider register --namespace Microsoft.CostManagement, then wait until its state reads Registered. Cost APIs are gated behind that namespace, and fresh subscriptions do not have it registered by default.