Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The subscription --ID-- is not allowed to create or update the serverfarm #2635

Open
tongchaij opened this issue Apr 22, 2024 · 23 comments
Open
Labels

Comments

@tongchaij
Copy link

Does this occur consistently? Yes (Since Applied Azure)

Repro steps:

  • Create Web App or Create Web App Plan (Try every location)

Action: appService.CreateWebApp
Error type: Forbidden
Error Message: The subscription '7651c700-0a86-4769-9e33-a73b86fa3bfe' is not allowed to create or update the serverfarm.

Version: 0.25.2
OS: win32
OS Release: 10.0.22631
Product: Visual Studio Code
Product Version: 1.88.1
Language: en

Call Stack
handleErrorResponse extension.bundle.js:2:1725611
deserializeResponseBody extension.bundle.js:2:1726338
@smitter-ua
Copy link

Have the same issue right at this moment

@alexweininger
Copy link
Member

Thanks for reporting this issue. It looks like the Azure App Service is experiencing some service side issues. Creating or updating web apps is intermittently failing. Please try again later, and if we get updates we'll let you know.

@thebolaji
Copy link

I'm also facing the same issue right now, any solution yet??

@ayanatwork-github
Copy link

What is the ETA for the issue. It only with App Service and Azure Function apps. Rest of the services are easily deployable.
I have a "pay-as-you-go" subscription, but while deploying app service or function app getting the error mentioned.

@hqt98
Copy link

hqt98 commented Apr 23, 2024

I'm experiencing the same issue

@DanielBradley1
Copy link

Experience the same issue on Sponsorship subscriptions

@smitter-ua
Copy link

smitter-ua commented Apr 23, 2024

I made it working after enabling another "Resource Provider". So besides "Microsoft.Web", I also enabled "Microsoft.DomainRegistration" on my subscription. I found out that this provider is involved in App Service creation as well as Function App, since they are based on the App Service by observing providers list from this article.
"Microsoft.DomainRegistration" was not enabled by default for my "free-tier" subscription, so I guess this should be a problem

@mberrishdev
Copy link

Experience the same issue on Sponsorship subscriptions

Yes, i have same problem.

@ayanatwork-github
Copy link

As per @smitter-ua , I have registered Microsoft.DomianRegsitration, but facing the same issue.

@shailesh-sakaria
Copy link

I have registered Microsoft.DomianRegsitration too along with Microsoft.Web, but facing the same issue.

@stuartharper01
Copy link

I have registered Microsoft.DomianRegsitration too along with Microsoft.Web, but facing the same issue.

@stv707
Copy link

stv707 commented Apr 25, 2024

I can confirm this, seems this issue is affecting only the FREE Tier Azure Subscription ( At least from my side ). Other TIER Subscription seems have no issue, and only on Web App and Function because both requires ASP ( Azure Service Plan ) , which the Subscription cannot plumb ASP. seems like, Microsoft not looking into this with urgency, MS learn Community forum logged this as been happening for past 1week+ . https://learn.microsoft.com/en-us/answers/questions/1659099/the-subscription-is-not-allowed-to-create-or-updat

@shailesh-sakaria
Copy link

I am using Pay As you Go subscription, still I am facing this error for new subscription.

@hqt98
Copy link

hqt98 commented Apr 25, 2024

I resolved the issued. I had to tag @AzureSupport on Twitter, then I sent them my sub id and they gave me a 72 hour technical support package that allows me to contact their tech support. Currently, this is a quota problem that can only be fixed by the engineering team case-by-case. They resolve my case after around 30 hours.

@rickycraft
Copy link

I have a subscription using Azure for Students and i cannot create the "App Service Plan" with the same error message. First approach to Azure and having this issue...from such a big provider this is a real disappointment.

@ayodejii
Copy link

ayodejii commented May 1, 2024

any update on this yet? I currently am facing this issue.

@Yassab09
Copy link

Yassab09 commented May 7, 2024

I was finally able to solve this issue after 3 days of tinkering. As i use a Free Plan, i couldn't create a support request. So here's what i did:

  • Openened docs at https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types
  • Click on any "Open Cloud Shell" button in green. A new cloud shell will open asking you to login.
  • Unregister Microsoft.Web using: Unregister-AzResourceProvider -ProviderNamespace Microsoft.Web
  • In your Azure Subscription page under Settings>Ressource providers, you will see that the status of Microsoft.Web is now "Unregistering" Don't freak out if this takes too long, in my case it took 45 minutes as it had to unregister throughout all regions.
  • Once Unregister is completed, all i had to do is to Register Again using Cloud Shell (the register button on the web portal might not work), just open Cloud Shell and type: Register-AzResourceProvider -ProviderNamespace Microsoft.Web
  • Wait for it to finish and do the same for Microsoft.NetworkFunction and Microsoft.DomainRegistration as they are both somehow intertwined with Microsoft.Web (I couldn't find any evidence but it is what it is, feel free to correct me).
  • After doing so, check which Region is assigned to your account subscription, as you will face the same issue again if you try to deploy to a wrong region. Go to Organization settings, just under the Overview, you will see "Geography > Region" in my case it was set to "Europe North", since i couldn't change it, i just deployed to the same region.

I hope this helps anyone facing the same issue.

@tsoliangwu0130
Copy link

Any update on this? Facing the same issue here.

@kingson-lab
Copy link

Any update on this? Facing the same issue here.
Even after register all Microsoft.Web, Microsoft.NetworkFunction and Microsoft.DomainRegistration and also tried on all region to create App Service.

@41WhiteElephants
Copy link

I resolved the issue based on the https://www.reddit.com/r/AZURE/comments/1chl7nj/visual_studio_professional_subscription_and/
by upgrading my subscription to pay-as-you-go. The deployment of AppService completed immediately after I confirmed my credit card.

@nbelyh
Copy link

nbelyh commented May 23, 2024

@41WhiteElephants
I have pay-as-you-go and started getting this issue just yesterday (before I was able to create web apps)
What is going on here.

@nbelyh
Copy link

nbelyh commented May 23, 2024

Just created a new subscription (a second one)
Creating new app source plan just worked for it without any issues.

@mubashar1199
Copy link

mubashar1199 commented Oct 24, 2024

I was finally able to solve this issue after 3 days of tinkering. As i use a Free Plan, i couldn't create a support request. So here's what i did:

  • Openened docs at https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types
  • Click on any "Open Cloud Shell" button in green. A new cloud shell will open asking you to login.
  • Unregister Microsoft.Web using: Unregister-AzResourceProvider -ProviderNamespace Microsoft.Web
  • In your Azure Subscription page under Settings>Ressource providers, you will see that the status of Microsoft.Web is now "Unregistering" Don't freak out if this takes too long, in my case it took 45 minutes as it had to unregister throughout all regions.
  • Once Unregister is completed, all i had to do is to Register Again using Cloud Shell (the register button on the web portal might not work), just open Cloud Shell and type: Register-AzResourceProvider -ProviderNamespace Microsoft.Web
  • Wait for it to finish and do the same for Microsoft.NetworkFunction and Microsoft.DomainRegistration as they are both somehow intertwined with Microsoft.Web (I couldn't find any evidence but it is what it is, feel free to correct me).
  • After doing so, check which Region is assigned to your account subscription, as you will face the same issue again if you try to deploy to a wrong region. Go to Organization settings, just under the Overview, you will see "Geography > Region" in my case it was set to "Europe North", since i couldn't change it, i just deployed to the same region.

I hope this helps anyone facing the same issue.

This worked, dont forget to register Microsoft.NetworkFunction and Microsoft.DomainRegistration if not already. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests