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

Hi Hussein Alwahab & thx for join me at Q&A platform,

u know this looks more like a subscription reactivation state synchronization issue on the App Service backend than a problem with your web app configuration.

The important detail is that properties.enabled is already true, while the actual runtime state remains AdminDisabled. Those are different things. Setting enabled=true or running az webapp start won't necessarily remove an administrative restriction imposed by the platform.

The Health Check error is another useful clue. If App Service still reports "subscription suspended" while Azure shows the subscription as Active, the Microsoft.Web resource provider may still be treating the subscription or resource as restricted.

I'd first verify that the subscription is fully enabled, not just that the outstanding payment has been processed. You can check the ARM subscription state with:

az account show --query "{name:name,state:state,id:id}" -o json

Also check whether other apps in the same subscription are affected and whether the App Service Plan itself is operational. That should help distinguish a subscription-wide restriction from one affecting this particular site.

You can check the resource state directly:

az webapp show -g govshield-rg -n govshield-app --query "{state:state,enabled:enabled,serverFarmId:serverFarmId}" -o json

However, I wouldn't keep retrying resource updates or try to force the state through ARM. There isn't a documented customer-facing command that reliably clears an App Service AdminDisabled state imposed by an administrative restriction.

At this point, I'd escalate the existing billing case and explicitly request involvement from the Azure App Service / Microsoft.Web support team.

Ask them to verify that the subscription reactivation has propagated to the App Service resource provider, check whether an administrative disable flag is still present, and determine whether the site needs a backend reactivation.

Include the subscription ID, web app resource ID, billing case number, the approximate UTC time the subscription became Active, and the failed Start operation's correlation ID from the Activity Log.

I'd specifically mention that the portal still returns a subscription-suspended error. That's stronger evidence of a backend state mismatch than the disabled Start button alone. U shouldn't need to delete and recreate the web app just to resolve this. And given your CI/CD dependency on the existing resource, I definitely wouldn't take that route without Microsoft confirming that recovery isn't possible.

If the billing team continues sending automated responses, request escalation to a support engineer who can investigate the App Service resource state, rather than opening another billing-only case.

rgds,

Alex

p.s. if my answer is help - pls mark it as an answer

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.