When deploying a MODM offer, it is possible that the Azure resources to deploy have not been registered in the subscription. This causes the deployment to fail.
It would be ideal to have MODM automatically register the required resource providers (in fact, this is default behavior in Terraform); however, the Managed Identity of the MODM deployment VM only has Owner permissions for it's own Resource Group. To be able to register the resources, a User Identity with the full permissions would need to be provided (instead of a System Identity).
Instead of having the administrator create a User Identity and add the permissions, it would be simpler (and likely easier) to document the resources required. That way the administrator can see what will be deployed and register the resource providers manually.
Output a list of resources the package will deploy with a list of pre-reqs. Example:
# Before installing, register the following resource providers:
az provider register --namespace Microsoft.Batch
az provider register --namespace Microsoft.Sql
When deploying a MODM offer, it is possible that the Azure resources to deploy have not been registered in the subscription. This causes the deployment to fail.
It would be ideal to have MODM automatically register the required resource providers (in fact, this is default behavior in Terraform); however, the Managed Identity of the MODM deployment VM only has Owner permissions for it's own Resource Group. To be able to register the resources, a User Identity with the full permissions would need to be provided (instead of a System Identity).
Instead of having the administrator create a User Identity and add the permissions, it would be simpler (and likely easier) to document the resources required. That way the administrator can see what will be deployed and register the resource providers manually.
Request/Recommendation: