App Service stuck in AdminDisabled state after subscription reactivation — cannot start

Hussein Alwahab 0 Reputation points
2026-09-29T14:05:23.01+00:00

Hi community,

My Azure App Service has been stuck in AdminDisabled state for several days

after my subscription was reactivated following a billing issue. The payment

has been resolved and the subscription shows as Active, but the app still

cannot be started.

Environment:

  • Subscription: be7e6498-cc65-4a01-a171-72e7e0bdc691
  • Resource group: govshield-rg
  • App Service: govshield-app
  • App Service Plan: ASP-govshieldrg-9d43

What I tried:

az webapp start --name govshield-app --resource-group govshield-rg

→ Operation returned an invalid status 'Bad Request'

az resource update --resource-group govshield-rg --name govshield-app \

--resource-type "Microsoft.Web/sites" --set properties.enabled=true

→ Operation returned an invalid status 'Bad Request'

az webapp show --name govshield-app --resource-group govshield-rg \

--query "{state:state, enabled:enabled}"

→ "enabled": true, "state": "AdminDisabled"

Portal behavior:

  • Start/Restart buttons are greyed out
  • Health check save fails with "subscription suspended" error even though subscription is Active

Question:

How do I lift the AdminDisabled state without deleting and recreating

the App Service? I cannot delete it because my CI/CD pipeline does not

recreate it — it only deploys to an existing App Service.

Any help appreciated. I have an open billing support ticket but only

getting automated responses so far.

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Salamat Shah 750 Reputation points MVP
    2026-09-29T17:16:54.4266667+00:00

    The AdminDisabled state is typically an administrative platform restriction and cannot be cleared using az webapp start or by setting properties.enabled=true.

    Since the billing issue is resolved and the subscription is Active, I recommend:

    • Verify there are no remaining subscription restrictions in Azure Portal → Subscriptions.
    • Escalate the existing Azure Billing/Support ticket and request that the subscription/App Service backend restriction be removed.
    • Do not delete or recreate the App Service, especially if your CI/CD pipeline depends on the existing resource.

    Microsoft Support may need to clear the residual suspension state on the backend before the App Service can start normally.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.