-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Microsoft.Network Resource Provider "Subscription is not registered with NRP." #26489
Copy link
Copy link
Open
Labels
ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupAuto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamact-identity-squadquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Metadata
Metadata
Assignees
Labels
ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupAuto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamact-identity-squadquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Checked and did not see any under these terms: https://github.com/Azure/azure-cli/issues?q=is%3Aissue+is%3Aopen+NRP
Related command
I am unable to use my subscription when running an mg deployment command like.
az deployment mg create --name $name --location $location --template-file $file --management-group-id $mgid --parameters networkingSub=$networkingSub.Describe the bug
I am unable to use my subscription when running an mg deployment command like.
az deployment mg create --name $name --location $location --template-file $file --management-group-id $mgid --parameters networkingSub=$networkingSub. The subscription is created using bicep.Even when running the command to register my networking subscription with the networking resource provider using
az provider register --namespace 'Microsoft.Network' --subscription $networkingSub, I still face this subscription is not registered with NRP error even with retry logic in place. When using other resource provdiers likeaz provider register --namespace 'Microsoft.AnyType' --subscription $subscriptionId, I have no issues and the registration happens without fail.To Reproduce
Expected behavior
The Microsoft.Network resource provider should register without issue and I should be able to deploy networking resources underneath this subscription.
When using Azure PowerShell I see the expected behavior when trying to register this subscription with the Microsoft.Network resource provider. No issues are faced with Azure PowerShell and no retry logic is needed.
Environment summary
Locally deployed using Windows.