Azure Front Door CORS rules stuck in "NotStarted" deployment status - configuration changes blocked

Question

Azure Front Door CORS rules stuck in "NotStarted" deployment status - configuration changes blocked

12th Pass 10

I have an Azure Front Door Standard profile with CORS rules configured but not deployed.

Issue:

Status: deploymentStatus = "NotStarted"
Error when trying to update: "BadRequest: All Changes to Azure Frondoor Configuration are blocked currently"

Impact:

Production application is failing CORS preflight requests with 405 errors, blocking all browser API calls.

Rules are properly configured to handle OPTIONS requests and set CORS headers
Unable to modify or trigger front door rules deployment via Azure CLI or Portal
Front Door profile status shows: ProvisioningState=Succeeded, ResourceState=Active

How can I trigger deployment of these existing CORS rules to the Front Door edge nodes?
Why are configuration changes blocked?

Anonymous

2025-11-03T06:51:19.71+00:00

Hi 12th Pass,

Welcome to Microsoft Q&A and thank you for posting your query here!

As per the latest update on the outage incident, all service management operations - including create, update, delete, and purge actions for Azure Front Door (AFD) and Azure CDN profiles are temporarily blocked to prevent further impact.

“Customer configuration changes to AFD remain temporarily blocked. We will notify customers once this block has been lifted. While error rates and latency are back to pre-incident levels, a small number of customers may still be experiencing issues, and we are actively working to mitigate this long tail. Updates will be provided directly via Azure Service Health.”

You can refer to the official status page here: https://azure.status.microsoft/status/history/

Customers will receive updates via email or Azure Service Health notifications. In parallel, we’re monitoring the situation internally and will share any progress as soon as it’s available.

Thanks,

Harish.
Anonymous

2025-11-06T03:40:18.1666667+00:00

Hi 12th Pass,

Good day, i hope you are doing well!

Quick update — Azure has lifted the temporary block on configuration operations. All create, update, delete, WAF, and cache purge actions for Azure Front Door and Azure CDN profiles are now enabled again.

If the profile still appears locked or pending migration, please retry the operation. It may take up to 45 minutes for configuration and propagation to complete for added safety, as noted in the Azure Front Door FAQ.

Once propagation finishes, you should be able to proceed with migration finalization or further updates. If the issue persists beyond that window, please do let us know.

i hope you should be able to perform all the actions.

Thanks,

Harish.
12th Pass 10 Reputation points

2025-11-09T12:55:22.5+00:00

Hi @Anonymous ,

Thanks for following up, but we are still stuck in the "Not Started" deployment state. We triggered redeployment, but that did not help.

Your answer

Anonymous

2025-11-03T06:51:19.71+00:00

Hi 12th Pass,

Welcome to Microsoft Q&A and thank you for posting your query here!

As per the latest update on the outage incident, all service management operations - including create, update, delete, and purge actions for Azure Front Door (AFD) and Azure CDN profiles are temporarily blocked to prevent further impact.

“Customer configuration changes to AFD remain temporarily blocked. We will notify customers once this block has been lifted. While error rates and latency are back to pre-incident levels, a small number of customers may still be experiencing issues, and we are actively working to mitigate this long tail. Updates will be provided directly via Azure Service Health.”

You can refer to the official status page here: https://azure.status.microsoft/status/history/

Customers will receive updates via email or Azure Service Health notifications. In parallel, we’re monitoring the situation internally and will share any progress as soon as it’s available.

Thanks,

Harish.
Anonymous

2025-11-06T03:40:18.1666667+00:00

Hi 12th Pass,

Good day, i hope you are doing well!

Quick update — Azure has lifted the temporary block on configuration operations. All create, update, delete, WAF, and cache purge actions for Azure Front Door and Azure CDN profiles are now enabled again.

If the profile still appears locked or pending migration, please retry the operation. It may take up to 45 minutes for configuration and propagation to complete for added safety, as noted in the Azure Front Door FAQ.

Once propagation finishes, you should be able to proceed with migration finalization or further updates. If the issue persists beyond that window, please do let us know.

i hope you should be able to perform all the actions.

Thanks,

Harish.
12th Pass 10 Reputation points

2025-11-09T12:55:22.5+00:00

Hi @Anonymous ,

Thanks for following up, but we are still stuck in the "Not Started" deployment state. We triggered redeployment, but that did not help.