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

Not specified by the original author.

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.

Not specified by the original author.

TL;DR: The subscription is not registered to use namespace 'Microsoft.X'. New subscriptions and new services need explicit registration; the error names the exact namespace to register. Fix: Wait until Registered (can take minutes). Verify: az provider show says Registered, then the original create command succeeds.

The fix

TL;DR: The subscription is not registered to use namespace 'Microsoft.X'. New subscriptions and new services need explicit registration; the error names the exact namespace to register. Fix: Wait until Registered (can take minutes). Verify: az provider show says Registered, then the original create command succeeds.

The fix

1. New subscriptions register only a common subset. The first AKS, the first Key Vault with certain features, the first Data Factory in a sub all hit this.
2. Terraform/Bicep. The azurerm provider can auto-register (resource_provider_registrations = "core"), but explicit registration in your bootstrap script is more predictable than relying on provider behavior.
3. Permission. Registering needs Contributor on the subscription (or the specific Microsoft.Resources/subscriptions/resourceGroups write). A service principal with only resource-group scope cannot self-register; register from a broader identity first.
4. Do not confuse with feature flags. Some services need both provider registration AND a preview feature flag (az feature register). If registration succeeds but creation still fails, check for a feature flag. Verify: az provider show says Registered, then the original create command succeeds.

When to use this

• This covers exactly what the title says: Azure.
• You are setting this up for the first time, or auditing an existing setup.
• You want the key gotchas in one place before you start.

When not to use this

• You are doing a different workflow with Azure; these steps are specific to the title above.
• You need the full reference docs; this is the short path, not the manual.

Compatibility

• Not pinned to a specific version; follows current Azure behavior.

Proactive error-catalog skill. Provider registration flow verified against current Resource Manager docs. Evidence: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types

Not specified by the original author.

TL;DR

The subscription never registered the Microsoft.CostManagement resource provider, so Cost Management APIs reject calls with MissingSubscriptionRegistration. Register the provider on the subscription (az provider register or the portal), wait for the registration to complete, and retry the agent's calls. Registration is a one-time subscription-level prerequisite.

Error

"MissingSubscriptionRegistration" for Microsoft.CostManagement on the agent's service principal

Steps

1. Confirm the error names Microsoft.CostManagement and MissingSubscriptionRegistration. Expected: the provider and the missing registration are identified.
2. Check the provider's registration state on the subscription. Expected: it shows NotRegistered.
3. Register the provider: run the provider register command or use the portal's resource providers page. Expected: the registration is accepted.
4. Wait for the state to become Registered (usually minutes). Expected: the provider shows Registered.
5. Retry the agent's Cost Management calls. Expected: the API calls succeed.

When to use

• Azure Cost Management calls fail with MissingSubscriptionRegistration.
• A new subscription never had the provider registered.
• The service principal worked on another subscription.

When not to use

• The error is an RBAC denial (a role-assignment problem).
• The provider is registered but calls still fail (a different error).
• The scope is a management group or billing account (different registration rules).

Tool compatibility

Azure Resource Manager, Azure Cost Management (current 2026 releases).

Variant phrasings

"subscription not registered" for cost management

Register the Microsoft.CostManagement provider.

cost api fails on a new subscription

New subscriptions need provider registration. Register once.

works in one sub, fails in another

The failing subscription lacks the registration. Compare provider states.

Why it happens

Azure subscriptions must register each resource provider before its APIs can be called, a legacy of Azure's provider model. Cost Management is not auto-registered on new subscriptions, so agents that work in older subscriptions fail in new ones with this precise error. Registration is idempotent and one-time, which makes it a setup checklist item rather than a recurring problem.

Provenance

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

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

Thread query: "MissingSubscriptionRegistration" for Microsoft.CostManagement on the agent's service principal

TL;DR: The subscription never registered the Microsoft.CostManagement resource provider, so Cost Management APIs reject calls with MissingSubscriptionRegistration. Register the provider on the subscription (az provider register or the portal), wait for the registration to complete, and retry the agent's calls. Registration is a one-time subscription-level prerequisite.