In this blog post, you’ll learn how to resolve the error that occurs when updating or creating dynamic scopes for resources deployed in a newly added Azure subscription.
While updating a dynamic scope that was already applied to several existing subscriptions in my environment, I encountered the error below when I tried to add resources from a newly added subscription
I quickly figured out the problem because I knew that to work with different types of resources in Azure, each subscription requires specific resource providers. These resource providers offer a set of operations that enable you to manage the resources they support.
Without these resource providers registered on a subscription, you can’t use the associated resources. For example, without the Microsoft.Compute resource provider, you can’t deploy Azure Virtual Machines (VMs) or VM Scale Sets in that subscription. Similarly, if the Microsoft.Network resource provider isn’t registered, you won’t be able to work with virtual networks or load balancers.
To use Azure Update Manager (AUM) and related resources such as dynamic scopes, which can be part of your maintenance configuration, certain resource providers must be registered.
These required resource providers are not always registered by default, which can lead to errors like the one I encountered. Specifically, for AUM to work properly, you need to have the following resource providers registered: Microsoft.Compute, Microsoft.HybridCompute, and Microsoft.Maintenance*.
*Core provider for managing update configurations and schedules
As you can see in the screenshot below, in my case, the Microsoft.HybridCompute and Microsoft.Maintenance resource providers were not registered for the subscription that caused the issue.
To fix this error, I just had to enable those resource providers, and I was then able to update the dynamic scope related to a specific maintenance configuration in my environment.
If you come across the same issue in your environment, you can fix it manually by going to the Azure Portal and signing in with an account that has permission to register resource providers.
Then, go to the affected subscription under Subscriptions, select Resource providers, and search for Compute and Maintenance. Select any required resource providers that are unregistered, and click Register.
💡 Keep in mind that registering resource providers in a subscription can take up to 10 minutes to complete.
After registering all the required resource providers, you should be able to update or create the specific dynamic scope, just like I was able to in my case.
Conclusion
Whenever you encounter issues updating or creating maintenance configurations related to AUM, or when adjusting dynamic scopes within those configurations, be sure all required resource providers are registered, especially when adding resources from a newly added subscription.
I hope the manual steps outlined in this blog post help you resolve similar errors in your environment. If you have any questions or suggestions, feel free to reach out on X (@wmatthyssen) or leave a comment below.
