During my preparation for the AZ-140 (Azure Virtual Desktop) certification I had problems creating a NetApp Files Account. When creating the NetApp account, I received the following error message:
Creation of ‘netAppAccounts’ has been restricted in this region
The only prerequisite before creating a NetApp Account is to register the Azure Provider “Microsoft.NetApp”. This was already done as described in the Microsoft Learn article before creating the NetApp account.
1 2 |
az account set --subscription <subscriptionID> az provider register --namespace Microsoft.NetApp --wait |
![](https://i0.wp.com/citrixguyblog.com/wp-content/uploads/2022/10/2022-10-19-08_39_32-Visual-Studio-Enterprise-1-Microsoft-Azure-and-10-more-pages-Personal-Mic.png?resize=810%2C178&ssl=1)
You can see that the ‘Microsoft.NetApp’ resource provider was registered successfully. I thought: Well it is the cloud maybe give it some time? But even after 24 hours the creation of the NetApp Account was still not possible. I reached out on Twitter and got feedback from Andreas Fleischmann with the missing hint.
I am using a MSDN Visual Studio Enterprise subscription in my tenant. It seems that Azure NetApp Files is restricted for those subscriptions. You need to contact the Azure Support and request a quota for the NetApp service.
After the Microsoft Support Engineer completed the quota request the creation of the NetApp account was possible 🙂
![](https://i0.wp.com/citrixguyblog.com/wp-content/uploads/2022/10/2022-10-19-09_58_59-2022-10-18-20_36_44-New-support-request-Microsoft-Azure-and-5-more-pages-Per.png?resize=810%2C642&ssl=1)
![](https://i0.wp.com/citrixguyblog.com/wp-content/uploads/2022/10/2022-10-18-20_37_23-New-support-request-Microsoft-Azure-and-5-more-pages-Personal-Microsoft​-E.png?resize=810%2C526&ssl=1)
![](https://i0.wp.com/citrixguyblog.com/wp-content/uploads/2022/10/2022-10-19-10_01_38-2022-10-18-20_38_03-New-support-request-Microsoft-Azure-and-5-more-pages-Per.png?resize=779%2C666&ssl=1)
Thanks!!! Saved my ass! 🙂
Thanks for this post! I was also getting this error when trying to deploy ANF to a Microsoft Partner subscription.