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/