AllowFrontdoor feature registration stuck in Pending for 24+ hours — blocking WAF policy deployment

Question

AllowFrontdoor feature registration stuck in Pending for 24+ hours — blocking WAF policy deployment

Erik Becker 0

Subscription ID: 05a6bdcf-f4aa-4d4e-8a7e-48c5b95f846a

The Microsoft.Network/AllowFrontdoor feature registration has been stuck in "Pending" state

for over 24 hours on the subscription above.

Steps taken:

Registered via: az feature register --namespace Microsoft.Network --name AllowFrontdoor
Polled status repeatedly since via: az feature show --namespace Microsoft.Network --name AllowFrontdoor --query "properties.state" -o tsv
Status has remained "Pending" the entire time, well beyond the documented up-to-48-hour propagation window (and now well past that too).

This is blocking creation of Azure Front Door Standard WAF policies

(Microsoft.Network/frontdoorWebApplicationFirewallPolicies) for a production deployment.

Attempting to create the WAF policy fails with:

"WebApplicationFirewallPolicy validation failed. Policy ArmResourceId has incorrect

formatting."

This subscription doesn't have a paid support plan, so I'm unable to open a formal support

ticket for this (get "InvalidSupportPlan" when trying via the Support API). Could someone

help look into why this specific feature registration is stuck, or manually complete it on

the backend?

Happy to provide any additional details needed.

0 comments

2 answers

Your answer

Answer 1

kagiyama yutaka 5,330

I think when AllowFrontdoor stays Pending after the feature and provider register, the user side ends there, and it just needs Azure support or a moderator to check the subscription backend.

0 comments

Answer 2

Chandra Hundigam 11 Microsoft Employee

Basic self-help resources are included for all Azure customers at no additional cost. For one-on-one technical support, you need a paid support plan. https://azure.microsoft.com/en-us/support/plans/

Erik Becker 0 Reputation points

2026-09-09T22:29:52.51+00:00

I understand basic support doesn't cover general "how do I" questions, but this specific issue

is a backend feature registration stuck at the subscription level (Microsoft.Network/

AllowFrontdoor) — not something a customer can self-resolve regardless of support tier, since

there's no customer-facing action that completes it. I found a nearly identical case

(same error message: "Policy ArmResourceId has incorrect formatting") where a moderator was

able to escalate directly to the Azure Networking team for manual backend resolution without

the reporter needing a paid support plan:

https://learn.microsoft.com/en-us/answers/questions/5956150/

Would it be possible to take a look at whether the same kind of backend escalation applies here?

Happy to provide any further detail needed.