Recently while
working on an implementation project for CMG, I came across an issue which I
had never dealt with before. I had taken care of the usual pre-requisites, but
nothing could have prepared me for what I was about to experience.
creating the Cloud Management Gateway Service, I got the following error.
access to the resource group prior to initiating the configuration.
SmsAdminUI.log logged some errors.
This got me looking into the activity of the resource group
and I verified that there was indeed an Azure policy blocking the creation of
the objects.
I matched the definition id and was able to identify the
policy in question. It was no other than, but the policy of Tags.
Classic providers within Azure don’t support tags. While
CMG uses Azure Resource Manager framework, it still uses classic service
providers for creating cloud objects. Mainly ClassicCompute and ClassicStorage.
Since the customer needed the Azure policy to be in place, I got the resource
group added in the exclusions.
I gave it another go at the creation of Cloud Management
Gateway service and this time it went through and the CMG objects got created.
Ref – https://docs.microsoft.com/en-us/azure/azure-resource-manager/tag-support