Microsoft.OperationsManagement Resource Provider Registration State Mismatch and Deployment Failure (Shows Registered but receiving MissingSubscriptionRegistration error)

Cheney Ahn 0 Reputation points
2025-05-22T05:16:46.21+00:00

Problem Description:

We are experiencing an unusual issue with the Microsoft.OperationsManagement resource provider.

Observed Behavior:

  1. Resource Provider Registration Status: When checking the registration state of the Microsoft.OperationsManagement resource provider using az provider show --namespace Microsoft.OperationsManagement, the RegistrationState is explicitly reported as "Registered". Furthermore, the Azure Portal under "Subscriptions" -> "Resource Providers" also confirms that Microsoft.OperationsManagement is in a Registered state.

Deployment Failure: Despite the resource provider showing as "Registered," any attempt to deploy resources that depend on this namespace (e.g., Azure Monitor Container Insights solution) fails with the following error message:

JSON

Code="MissingSubscriptionRegistration"
Message="The subscription is not registered to use namespace 'Microsoft.OperationsManagement'. See https://aka.ms/rps-not-found for how to register subscriptions."
Details=[{"code":"MissingSubscriptionRegistration","message":"The subscription is not registered to use namespace 'Microsoft.OperationsManagement'. See https://aka.ms/rps-not-found for how to register subscriptions.","target":"Microsoft.OperationsManagement"}]

The error message explicitly states that the subscription is not registered for the namespace, which directly contradicts the "Registered" status returned by az provider show and shown in the Azure Portal.

Steps Taken to Resolve:

  1. Attempted to unregister and re-register the resource provider using az provider unregister --namespace Microsoft.OperationsManagement followed by az provider register --namespace Microsoft.OperationsManagement. After re-registration, az provider show still reports "Registered", but the deployment error persists.
  2. Confirmed that the currently active Azure CLI subscription matches the subscription where the deployment is being attempted.
  3. Verified the resource provider status in the Azure Portal and attempted re-registration there as well, but the issue remains.

Expected Outcome:

We expect the Microsoft.OperationsManagement resource provider to be fully and functionally registered with our subscription, allowing us to successfully deploy dependent services (such as Container Insights). Given the discrepancy between the reported "Registered" state and the "MissingSubscriptionRegistration" error, we suspect there might be an internal synchronization issue or a backend problem within Azure.

Additional Information:

  • This issue is occurring in the '(e.g., Korea Central)' Azure region.
  • The specific resource we are trying to deploy is the 'Azure Monitor Container Insights solution' and aks-kfncczpjmfmw4.
  • I am trying GraphRAG and this error has incurred, too.
Checking cloud region for VM sku availability... Done.
Checking Location for SKU Quota Usage... Done.
Checking if resource group gx-rag-test exists... Yes.
Checking if APIM was soft-deleted... Done.
Deploying Azure resources...
Deployment name: graphrag-deploy-2025-05-22_04-44-48
ERROR: {"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/c1485840-0dbe-4669-96fb-3ddc0690c403/resourceGroups/gx-rag-test/providers/Microsoft.Resources/deployments/graphrag-deploy-2025-05-22_04-44-48","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidTemplateDeployment","message":"The template deployment 'aks-deployment' is not valid according to the validation procedure. The tracking id is '9b51e8c4-00f4-4da0-aa12-d38665d8917c'. See inner errors for details.","details":[{"code":"InternalOperationError","message":"Preflight validation check for resource(s) for container service aks-kfncczpjmfmw4 in resource group gx-rag-test failed. Message: We are unable to serve this request due to an internal error, Correlation ID: 86aced28-432c-4fdf-840b-ec0c1c4001bd, Operation ID: 7755345f-559f-4cea-886a-bcb6354bbd8f, Timestamp: 2025-05-22T04:46:16Z.. Details: "}]}]}}
Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,658 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Alex Burlachenko 10,255 Reputation points
    2025-05-22T15:13:31.7766667+00:00

    Dear Cheney Ahn,

    Thank you for reaching out and sharing the details of your issue. I really appreciate you taking the time to post this on the Q&A portal, and I’ll do my best to help clarify what might be going wrong.

    From what you’ve described, it sounds like there’s a confusing mismatch where the Azure CLI and the Azure Portal both show Microsoft.OperationsManagement as "Registered," but deployments still fail with a MissingSubscriptionRegistration error. This can definitely be frustrating, especially when you’ve already tried re-registering the provider.

    First, let’s double-check a few things to make sure we’re on the same page. Even though the provider appears registered, sometimes there can be delays or sync issues between Azure’s backend services. The official Microsoft documentation mentions that registration can take up to 15 minutes to fully propagate, though it’s usually faster. You can find more details about this here: Register resource provider - Microsoft Docs.

    Since you’re deploying in the Korea Central region, there might also be regional replication delays. One thing you could try is forcing a refresh by unregistering the provider, waiting a few minutes, and then registering it again. After that, give it another 10-15 minutes before attempting the deployment. Sometimes, the system needs a bit more time to fully update.

    Another thing to verify is whether the subscription you’re using has the necessary permissions. Even if the provider is registered, role assignments or policy restrictions could block deployments. The error message suggests checking https://aka.ms/rps-not-found, which explains how to ensure your subscription is properly set up.

    For the Container Insights deployment, there might be additional dependencies. The Azure Monitor team has a troubleshooting guide here: Troubleshoot Azure Monitor Container Insights, which could help pinpoint if there’s a related configuration issue.

    Lastly, the internal error you’re seeing (Correlation ID: 86aced28-432c-4fdf-840b-ec0c1c4001bd) suggests there might be a temporary backend problem. If the issue persists after re-registering and waiting, it could be worth opening a support ticket with Microsoft so they can investigate the logs for that specific correlation ID.

    I hope this helps, and please let me know if you’ve already tried these steps or if there’s any additional detail that might shed more light on the problem

    Best regards,
    Alex
    P.S. If my answer help to you, please Accept my answer
    PPS That is my Answer and not a Comment
    https://ctrlaltdel.blog/
    
    0 comments No comments

Your answer

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