A community member has associated this post with a similar question:
The subscription is not allowed to create or update the serverfarm

Only moderators can edit this content.

The subscription is not allowed to create or update the serverfarm.

David McNicol 0

Hello,

I have been trying to create a webapps on a newly created subscriptions for two customers. The deployments fail with a Bad Gateway message and message in the operation details:

The subscription '

VenkateshDodda-MSFT 18,281 Reputation points Microsoft Employee

2024-04-19T07:23:02.86+00:00

@David McNicol as this issue is similar thread to the issue mentioned in the thread #1657059. I am marking this thread as duplicate of the other thread, and I would suggest you follow the latest discussion and suggested workaround in the other thread.

1 answer

Marcin Policht 10,845 Reputation points MVP

2024-04-18T11:09:25.2866667+00:00

Apparently this is an ongoing issue - you'd need to retry:

https://stackoverflow.com/questions/78101504/azure-app-service-deployment-failing-the-subscription-xxxx-xxxx-xxxx-is-not-al

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin
Please sign in to rate this answer.
David McNicol 0 Reputation points

2024-04-19T06:44:18.1966667+00:00

Hello,

Thanks for the reply.

I had seen this problem on three subscriptions on separate tenants. Since posting the question, I have been able to create the web app on one of the tenants, but get the same error on the other two today. I had checked the registration of the Microsoft.Web provider, new browsers etc today.

I had tried the command line instructions on the tenant that worked and one that does not. On both, the command

az provider list --query "[namespace=='Microsoft.Web'].resourceTypes[].resourceType"

returned nothing and

az provider list --query "[namespace=='Microsoft.Web']"

Returned false, this was after I had run the register command and checked the list of providers against the subscription. Microsoft.Web appears as registered in both the working and not working.

When you say an ongoing issue. Do you know if it affects subscriptions or is a transient problem with the creation process?