Microsoft.Network/AllowFrontdoor remains Pending after feature registration

Question

Microsoft.Network/AllowFrontdoor remains Pending after feature registration

Soifur Rahman 0

Hi,

I’m experiencing the same issue described here:

https://learn.microsoft.com/en-us/answers/questions/5945711/azure-front-door-waf-creation-fails-and-microsoft

I have already run:

az feature registration create --namespace Microsoft.Network --name AllowFrontdoor

However, the feature still shows:

Approval type: ApprovalRequired

Registration state: Pending

Microsoft.Network and Microsoft.Cdn are both registered. The Azure Front Door profile deploys successfully, but the WAF policy fails with:

WebApplicationFirewallPolicy validation failed. Policy ArmResourceId has incorrect formatting.

The existing answer does not resolve the issue because the feature requires approval for each subscription.

Could a Microsoft engineer please escalate this to a private support case and enable the feature for this subscription? I can provide the subscription ID, deployment details and correlation information privately.

Thanks,

Soifur

Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-07-24T13:35:12.8033333+00:00
Hello @Soifur Rahman

Thank you for reaching out to Microsoft Q&A

Based on the behaviour observed, this appears to be related to the Microsoft.Network/AllowFrontdoor feature registration/subscription flag rather than the Front Door deployment itself. The Front Door profile deploys successfully, whereas the WAF policy creation fails during ARM validation, which suggests the feature may not yet be fully enabled in the subscription.

According to Microsoft guidance, feature registrations can take time to propagate and may require up to 48 hours before the status is fully updated across the platform. If the feature remains in a Pending or ApprovalRequired state after the propagation window, it is recommended to:

Recheck the feature registration status.

Re-register the affected resource provider.

Allow additional time for backend propagation before further troubleshooting.

Please note that the "Pending" status referenced in some Front Door documentation can also be related to custom domain DNS validation, which is a separate scenario from the WAF policy creation failure reported here.

Recommended next steps:

Wait for the feature registration to complete propagation (up to 48 hours).

Revalidate the registration status after the propagation period.

Re-register the Microsoft.Network resource provider if the feature remains pending.

If the feature continues to remain in a Pending/ApprovalRequired state beyond the expected timeframe, consider engaging the appropriate support team to verify the subscription-level feature enablement.

At this stage, the behaviour points more towards a feature registration state issue than a Front Door deployment issue.
Soifur Rahman 0 Reputation points

2026-07-24T13:42:09.87+00:00

Hi Sindhuja,

Thanks for confirming. I registered Microsoft.Network/AllowFrontdoor today, so I’ll allow the full 48-hour propagation window.

The feature currently remains Pending. Microsoft.Network and Microsoft.Cdn are both Registered, and no custom domain is currently configured, so this is separate from DNS validation.

I’ll recheck the feature after the propagation window. If it remains Pending or ApprovalRequired, I’ll update this thread so it can be escalated for subscription-level enablement.

Thanks,

Soifur
Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-07-27T15:49:42.83+00:00

Hello @Soifur Rahman

Following up to see if the feature is registered. And, if you have any further query do let us know.
Soifur Rahman 0 Reputation points

2026-07-28T10:55:10.4433333+00:00

Hello Sindhuja,

I rechecked the feature today using az feature show --namespace Microsoft.Network --name AllowFrontdoor. The registration state is still Pending, despite more than 48 hours having passed.

Azure Front Door Standard itself has deployed successfully, but the WAF policy remains blocked by this feature state. Could this please be escalated to the Azure Networking team to check the subscription-level feature enablement? I can provide the subscription ID and deployment details privately if required.

Kind regards,

Soifur
Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-07-31T16:58:45.3333333+00:00

Hello @Soifur Rahman

I have initiated private message, please share the details
Soifur Rahman 0 Reputation points

2026-08-25T08:25:59.8433333+00:00

Hi @Sindhuja Dasari , apologies for the delay in response, I didn't receive a notification for this. I can't seem to raise a support ticket through Azure, it keeps referring me to this learn page
Soifur Rahman 0 Reputation points

2026-08-25T08:26:23.6966667+00:00

Hi @Sindhuja Dasari , apologies for the delay in response, I didn't receive a notification for this. I can't seem to raise a support ticket through Azure, it keeps referring me to this learn page
Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-08-26T08:45:00.56+00:00

Hello @Soifur Rahman

Please share the requested details over private message. Thank you

Your answer

Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-07-24T13:35:12.8033333+00:00

Hello @Soifur Rahman

Thank you for reaching out to Microsoft Q&A

Based on the behaviour observed, this appears to be related to the Microsoft.Network/AllowFrontdoor feature registration/subscription flag rather than the Front Door deployment itself. The Front Door profile deploys successfully, whereas the WAF policy creation fails during ARM validation, which suggests the feature may not yet be fully enabled in the subscription.

According to Microsoft guidance, feature registrations can take time to propagate and may require up to 48 hours before the status is fully updated across the platform. If the feature remains in a Pending or ApprovalRequired state after the propagation window, it is recommended to:

Recheck the feature registration status.

Re-register the affected resource provider.

Allow additional time for backend propagation before further troubleshooting.

Please note that the "Pending" status referenced in some Front Door documentation can also be related to custom domain DNS validation, which is a separate scenario from the WAF policy creation failure reported here.

Recommended next steps:

Wait for the feature registration to complete propagation (up to 48 hours).

Revalidate the registration status after the propagation period.

Re-register the Microsoft.Network resource provider if the feature remains pending.

If the feature continues to remain in a Pending/ApprovalRequired state beyond the expected timeframe, consider engaging the appropriate support team to verify the subscription-level feature enablement.

At this stage, the behaviour points more towards a feature registration state issue than a Front Door deployment issue.
Soifur Rahman 0 Reputation points

2026-07-24T13:42:09.87+00:00

Hi Sindhuja,

Thanks for confirming. I registered Microsoft.Network/AllowFrontdoor today, so I’ll allow the full 48-hour propagation window.

The feature currently remains Pending. Microsoft.Network and Microsoft.Cdn are both Registered, and no custom domain is currently configured, so this is separate from DNS validation.

I’ll recheck the feature after the propagation window. If it remains Pending or ApprovalRequired, I’ll update this thread so it can be escalated for subscription-level enablement.

Thanks,

Soifur
Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-07-27T15:49:42.83+00:00

Hello @Soifur Rahman

Following up to see if the feature is registered. And, if you have any further query do let us know.
Soifur Rahman 0 Reputation points

2026-07-28T10:55:10.4433333+00:00

Hello Sindhuja,

I rechecked the feature today using az feature show --namespace Microsoft.Network --name AllowFrontdoor. The registration state is still Pending, despite more than 48 hours having passed.

Azure Front Door Standard itself has deployed successfully, but the WAF policy remains blocked by this feature state. Could this please be escalated to the Azure Networking team to check the subscription-level feature enablement? I can provide the subscription ID and deployment details privately if required.

Kind regards,

Soifur
Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-07-31T16:58:45.3333333+00:00

Hello @Soifur Rahman

I have initiated private message, please share the details
Soifur Rahman 0 Reputation points

2026-08-25T08:25:59.8433333+00:00

Hi @Sindhuja Dasari , apologies for the delay in response, I didn't receive a notification for this. I can't seem to raise a support ticket through Azure, it keeps referring me to this learn page
Soifur Rahman 0 Reputation points

2026-08-25T08:26:23.6966667+00:00

Hi @Sindhuja Dasari , apologies for the delay in response, I didn't receive a notification for this. I can't seem to raise a support ticket through Azure, it keeps referring me to this learn page
Sindhuja Dasari 2,115 Reputation points Microsoft External Staff Moderator

2026-08-26T08:45:00.56+00:00

Hello @Soifur Rahman

Please share the requested details over private message. Thank you