Anyone faced this error before when running az deployment mg create command to deploy a bicep file with parameters? I thought it was transient, but it happens consistently daily during my deployment testing.
Also raised this question on GitHub.
Anyone faced this error before when running az deployment mg create command to deploy a bicep file with parameters? I thought it was transient, but it happens consistently daily during my deployment testing.
Also raised this question on GitHub.
On
In my case I was getting error while applying a blueprint:
There were error(s) encountered during the deployment:
The artifact 'network_deploy_spoke' of type 'Template' failed to deploy due to the following error: Template deployment failed with error [
{ "code": "SubscriptionNotRegistered", "message": "Subscription XXX is not registered with NRP." },
{ "code": "SubscriptionNotRegistered", "message": "Subscription XXX is not registered with NRP." },
{ "code": "SubscriptionNotRegistered", "message": "Subscription XXX is not registered with NRP." },
{ "code": "SubscriptionNotRegistered", "message": "Subscription XXX is not registered with NRP." } ]
So as methioned in the doc, used below to find and compare NotRegistered providers.
Get-AzResourceProvider -ListAvailable | Where-Object RegistrationState -eq "NotRegistered" | Select-Object ProviderNamespace, RegistrationState | Sort-Object ProviderNamespace
Then registering with those using below fixed the issue for me:
Register-AzResourceProvider -ProviderNamespace Microsoft.Compute
Register-AzResourceProvider -ProviderNamespace Microsoft.KeyVault
Register-AzResourceProvider -ProviderNamespace Microsoft.Management
Register-AzResourceProvider -ProviderNamespace Microsoft.RecoveryServices
Register-AzResourceProvider -ProviderNamespace Microsoft.Sql
Register-AzResourceProvider -ProviderNamespace Microsoft.Web
The
Microsoft.Networkresource provider is not registered for the related subscription.You can check the documentation to enable it:
Register resource provider