All Changes to Azure Frondoor Configuration are blocked currently

Question

All Changes to Azure Frondoor Configuration are blocked currently

Nandipally, Dheeraj 145

Hi

We are currently blocked with front door deployments, what is the ETA for the Front door to be operational and unblocked ?

Jing Liu 20 Reputation points

2025-11-03T04:54:09.5933333+00:00

2 days after the outage, I'm still getting: "BadRequest: All Changes to Azure Frondoor Configuration are blocked currently. ". What's the ETA of unblocking?
Palivela Raviteja 15 Reputation points

2025-11-03T06:47:02.9833333+00:00

What's the ETA of unblocking?
Joshua Moniz 0 Reputation points

2025-11-03T07:20:00.49+00:00

We are currently unable to update our Azure Front Door (Standard/Premium) configuration. Whenever we attempt to modify or save changes to a Ruleset, we receive the following error:

“Failed to update the rule set '<rule set name>'. Error: All Changes to Azure Front Door Configuration are blocked currently.”

Because of this block, our active configuration is preventing access to our site and we’re unable to roll back or apply any updates.

We suspect the configuration propagation may be stuck globally, or that one or more edge locations have failed to sync, resulting in a global lock.

Please investigate and advise if there’s a known replication issue, and help us clear the configuration block so we can restore normal service.
Jan Zakrzewski 50 Reputation points

2025-11-03T08:24:37.3966667+00:00

This is from Azure Service Health: "Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 03 November 2025 or sooner as events warrant."
Ali Reaziat 25 Reputation points

2025-11-03T16:24:14.7966667+00:00

November 3rd 2025 and the issue still remains!! our business has been practically shut down! This is insane
Ali Reaziat 25 Reputation points

2025-11-03T16:25:59.4733333+00:00

We have never received communication on this outage. It's Nov 3rd and no update. This has also affected all DNS updates, SSL reissues and modifications.
Anonymous

2025-11-03T16:55:14.38+00:00

Hello @Nandipally, Dheeraj,

Apologies for the inconvenience. As of now, there are no new updates. We are continuing to closely monitor the situation with our internal team. Once there are any developments, we will get back to you immediately.
Das, Deepak 0 Reputation points

2025-11-04T07:52:41.6833333+00:00

@Anonymous any update on this issue? we are stucked and can't proceed with our deployment
Bhavin Parmar 0 Reputation points

2025-11-04T11:19:10.0933333+00:00

@Anonymous Please update once the problem is resolved.
Jainam Khakhkhar 5 Reputation points

2025-11-04T11:20:11.9866667+00:00

@Anonymous any update on this issue? we're stucked!!
Anonymous

2025-11-04T13:03:39.2433333+00:00

We are still facing this issue. I hope it will be resolved before this weekend.
Waldo Kloor 0 Reputation points

2025-11-04T14:20:55.4166667+00:00

We are also facing this issue and are blocked for these types of deployments.
Balwant Patel 51 Reputation points

2025-11-04T14:23:49.21+00:00

Any ETA please.
Daniel Sanders 6 Reputation points

2025-11-04T17:00:08.3133333+00:00

We are also waiting for a solution and the status page is not providing any usefull updates. Is the planning still to lift restrictions on the fifth?
Niccolo 70 Reputation points

2025-11-04T17:03:20.6066667+00:00

We are also facing issues. Microsoft representative are not replying to us and we are asking credit request, because we are deeply affeected.
Anant Chaudhari 5 Reputation points

2025-11-04T17:05:20.3266667+00:00

We are also BLOCKED by this. Creation of new Front Door Services in our Prod/pre_Prod environments with below error:
Error: Profile Name: "fd-pf-****-001"): performing Create: unexpected status 400 (400 Bad Request) with error: BadRequest: All Changes to Azure Frondoor Configuration are blocked currently.
passerbliss 5 Reputation points

2025-11-04T17:40:36.8433333+00:00

For myself, Azure Front Door profile has been stuck in a 'Deleting' state for a number of days. Receiving the error "All changes to Azure Frontoor Configuration are blocked currently" if I try to modify the profile. Noted that the Tracking ID YKYN-BWZ states the issue is resolved, however this doesn't appear to be the case.
Steven Trotter 10 Reputation points

2025-11-04T21:05:55.3033333+00:00

Any idea when this is going to be resolved? Taking a week is not great but it's far better than it going down again so I sympathise, but not even giving an indication if this is weeks (it's not less), month, years (surely not but how do we know at this stage) is surely embarrassing for a major cloud provider.
Balwant Patel 51 Reputation points

2025-11-04T21:22:34.4933333+00:00

It's 4 days today someone form Microsoft must come up with ETA
RD-D 30 Reputation points

2025-11-05T08:01:22.65+00:00

Agreed with everyone that this is a truly embarrassing situation for Microsoft. It's now getting on for nearly a week and the amount of wasted time, energy and opportunity this issue must have caused globally must be huge.

On a positive note, it seems as of 01:00 CET today (5th) it is still on track to be resolved sometime today.

We continue to hit our milestones toward the expectation to lift this restriction on 05 November 2025. The next update will be sent to confirm once this has happened, or sooner if events warrant.

I really hope Microsoft learn from this and make positive changes. It's the second time just in October that Front Door has experienced a major outage, and on both occasions the Azure monitoring appeared to lag behind the issue. Trust is easily lost, and the handling of this most recent incident of this has been very disappointing.
Emre Y 15 Reputation points

2025-11-05T14:22:31.02+00:00

We are still not able to do anything with "frondoor". Do we get any updates for that? Unfortunately the https://azure.status.microsoft/de-de/status page shows everything looks good, which is misleading imho.. at least you guys could be more transparent..
Fabio Junior Colan Wong 50 Reputation points

2025-11-05T14:58:44.05+00:00

Hello,

We are still experiencing a blocking issue when performing any action. Please provide an ETA, as our operations are currently suspended and we are unable to perform any updates. This results in the loss of clients and revenue.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mark Frick 55 Reputation points

2025-11-05T15:11:19.39+00:00

I am not buying their cascading configuration story on the source of the problem, but that is secondary to the pathetic way this incident has been handled. If it were truly a configuration issue gone bad, this would have been resolved in a day. Here we are, sitting almost a week later with no information or ETA, and they have us locked out. We are considering moving our CDNs to AWS or Google because Azure support has become a bad joke. This incident is all the evidence you need.
Barry Bahrami 26 Reputation points

2025-11-05T17:45:37.0466667+00:00

I wouldn't be holding operations and incurring ongoing impact to business. IMHO, you should move the FD service over to another. Imperva, Cloud Flare, etc.. You don't necessarily need to be stuck where you are.
Ali Reaziat 25 Reputation points

2025-11-05T19:09:35.6866667+00:00

It's Nov 5 and still locked! What is the ETA? Our business has practically been shut down since last Friday
Mitchell Moore 10 Reputation points

2025-11-05T21:13:05.8733333+00:00

Hello, as of writing this post it is 21:11 GMT. Is there any ETA on when this will be fixed? It was my understanding that November 5th was the 'fix' date, although I never saw an official source claiming this.

I understand if there is no answer, but I would really appreciate at least some sort of ETA on the matter. Communication on this issue has been really poor from Microsoft's end.
Mark Frick 55 Reputation points

2025-11-05T21:41:52.4366667+00:00

I have not seen any official notice from Azure but I was able to submit a FD change for a certificate because I kept trying every hour. It took a very long time to finish but it did complete. That said, Azure did not handle this incident well. On my other App Services there is marketing note about moving to Front Door ... lol ... you have to be kidding now.
Mark Frick 55 Reputation points

2025-11-05T21:55:13.5633333+00:00

Front Page ... that ages me ... Front Door is the correct term
Angel Cruz 0 Reputation points

2025-11-05T22:52:26.1166667+00:00

Now it's working, I have deleted a front door without issues a minutes ago, thks
Oporto, Leonardo 0 Reputation points

2025-11-05T23:26:53.3566667+00:00

As I understand this would be solved on nov 5. But I don't see any update. Does anyone have any info?

Thanks
Angel Cruz 0 Reputation points

2025-11-06T01:03:23.5933333+00:00

Now it's working, I have deleted a front door without issues a minutes ago, thks
Anonymous

2025-11-06T03:52:51.78+00:00

Hello @Nandipally, Dheeraj,

Could you confirm whether you can be able to configure for all create, update, delete, WAF, and cache purge actions for Azure Front Door and CDN profiles? These operations may take up to 45 minutes to complete for added safety.
Salimath, Vishwanath (623) 5 Reputation points

2025-11-06T04:37:12.9866667+00:00

It’s working now, however, the workflow took around 35 minutes to complete.
Seleke, Tshepo T 0 Reputation points

2025-11-06T06:43:28.7833333+00:00

Anybody aware what could be causing https://js.monitor.azure.com/scripts/b/ai.config.1.cfg.json to surface 503 errors taking the whole app service
Anonymous

2025-11-06T17:47:40.44+00:00

Hello @Nandipally, Dheeraj,

The temporary Service Management restrictions on Azure Front Door have been lifted on 5th November, and customers can now resume their configuration changes.

The Azure portal also reflects this update as a banner:

The backend team is actively monitoring the platform. And in case of any issues, we will reach out to the backend team for further assistance.

Reference: Azure Front Door frequently asked questions (FAQ) | Microsoft Learn
Shanzs 0 Reputation points

2025-11-07T08:23:52.5833333+00:00

Created AFD profile Nov 7 2025 8:00 AM UTC. While I am able to complete the configuration, I am unable to access the AFD endpoint from browser. Browser error ...

Page not found

Oops! We weren't able to find your Azure Front Door Service configuration. If it's a new configuration that you recently created, it might not be ready yet. You should check again in a few minutes. If the problem persists, please contact Azure support.

Alert on Azure portal
Anonymous

2025-11-11T17:47:33.32+00:00

Hello @Shanzs,

Kindly raise a ticket in the Q&A portal regarding the issue you are facing, and we will get back to you.

Regard's
Jeevan S

1 answer

Your answer

Jing Liu 20 Reputation points

2025-11-03T04:54:09.5933333+00:00

2 days after the outage, I'm still getting: "BadRequest: All Changes to Azure Frondoor Configuration are blocked currently. ". What's the ETA of unblocking?
Palivela Raviteja 15 Reputation points

2025-11-03T06:47:02.9833333+00:00

What's the ETA of unblocking?
Joshua Moniz 0 Reputation points

2025-11-03T07:20:00.49+00:00

We are currently unable to update our Azure Front Door (Standard/Premium) configuration. Whenever we attempt to modify or save changes to a Ruleset, we receive the following error:

“Failed to update the rule set '<rule set name>'. Error: All Changes to Azure Front Door Configuration are blocked currently.”

Because of this block, our active configuration is preventing access to our site and we’re unable to roll back or apply any updates.

We suspect the configuration propagation may be stuck globally, or that one or more edge locations have failed to sync, resulting in a global lock.

Please investigate and advise if there’s a known replication issue, and help us clear the configuration block so we can restore normal service.
Jan Zakrzewski 50 Reputation points

2025-11-03T08:24:37.3966667+00:00

This is from Azure Service Health: "Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 03 November 2025 or sooner as events warrant."
Ali Reaziat 25 Reputation points

2025-11-03T16:24:14.7966667+00:00

November 3rd 2025 and the issue still remains!! our business has been practically shut down! This is insane
Ali Reaziat 25 Reputation points

2025-11-03T16:25:59.4733333+00:00

We have never received communication on this outage. It's Nov 3rd and no update. This has also affected all DNS updates, SSL reissues and modifications.
Anonymous

2025-11-03T16:55:14.38+00:00

Hello @Nandipally, Dheeraj,

Apologies for the inconvenience. As of now, there are no new updates. We are continuing to closely monitor the situation with our internal team. Once there are any developments, we will get back to you immediately.
Das, Deepak 0 Reputation points

2025-11-04T07:52:41.6833333+00:00

@Anonymous any update on this issue? we are stucked and can't proceed with our deployment
Bhavin Parmar 0 Reputation points

2025-11-04T11:19:10.0933333+00:00

@Anonymous Please update once the problem is resolved.
Jainam Khakhkhar 5 Reputation points

2025-11-04T11:20:11.9866667+00:00

@Anonymous any update on this issue? we're stucked!!
Anonymous

2025-11-04T13:03:39.2433333+00:00

We are still facing this issue. I hope it will be resolved before this weekend.
Waldo Kloor 0 Reputation points

2025-11-04T14:20:55.4166667+00:00

We are also facing this issue and are blocked for these types of deployments.
Balwant Patel 51 Reputation points

2025-11-04T14:23:49.21+00:00

Any ETA please.
Daniel Sanders 6 Reputation points

2025-11-04T17:00:08.3133333+00:00

We are also waiting for a solution and the status page is not providing any usefull updates. Is the planning still to lift restrictions on the fifth?
Niccolo 70 Reputation points

2025-11-04T17:03:20.6066667+00:00

We are also facing issues. Microsoft representative are not replying to us and we are asking credit request, because we are deeply affeected.
Anant Chaudhari 5 Reputation points

2025-11-04T17:05:20.3266667+00:00

We are also BLOCKED by this. Creation of new Front Door Services in our Prod/pre_Prod environments with below error:
Error: Profile Name: "fd-pf-****-001"): performing Create: unexpected status 400 (400 Bad Request) with error: BadRequest: All Changes to Azure Frondoor Configuration are blocked currently.
passerbliss 5 Reputation points

2025-11-04T17:40:36.8433333+00:00

For myself, Azure Front Door profile has been stuck in a 'Deleting' state for a number of days. Receiving the error "All changes to Azure Frontoor Configuration are blocked currently" if I try to modify the profile. Noted that the Tracking ID YKYN-BWZ states the issue is resolved, however this doesn't appear to be the case.
Steven Trotter 10 Reputation points

2025-11-04T21:05:55.3033333+00:00

Any idea when this is going to be resolved? Taking a week is not great but it's far better than it going down again so I sympathise, but not even giving an indication if this is weeks (it's not less), month, years (surely not but how do we know at this stage) is surely embarrassing for a major cloud provider.
Balwant Patel 51 Reputation points

2025-11-04T21:22:34.4933333+00:00

It's 4 days today someone form Microsoft must come up with ETA
RD-D 30 Reputation points

2025-11-05T08:01:22.65+00:00

Agreed with everyone that this is a truly embarrassing situation for Microsoft. It's now getting on for nearly a week and the amount of wasted time, energy and opportunity this issue must have caused globally must be huge.

On a positive note, it seems as of 01:00 CET today (5th) it is still on track to be resolved sometime today.

We continue to hit our milestones toward the expectation to lift this restriction on 05 November 2025. The next update will be sent to confirm once this has happened, or sooner if events warrant.

I really hope Microsoft learn from this and make positive changes. It's the second time just in October that Front Door has experienced a major outage, and on both occasions the Azure monitoring appeared to lag behind the issue. Trust is easily lost, and the handling of this most recent incident of this has been very disappointing.
Emre Y 15 Reputation points

2025-11-05T14:22:31.02+00:00

We are still not able to do anything with "frondoor". Do we get any updates for that? Unfortunately the https://azure.status.microsoft/de-de/status page shows everything looks good, which is misleading imho.. at least you guys could be more transparent..
Fabio Junior Colan Wong 50 Reputation points

2025-11-05T14:58:44.05+00:00

Hello,

We are still experiencing a blocking issue when performing any action. Please provide an ETA, as our operations are currently suspended and we are unable to perform any updates. This results in the loss of clients and revenue.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mark Frick 55 Reputation points

2025-11-05T15:11:19.39+00:00

I am not buying their cascading configuration story on the source of the problem, but that is secondary to the pathetic way this incident has been handled. If it were truly a configuration issue gone bad, this would have been resolved in a day. Here we are, sitting almost a week later with no information or ETA, and they have us locked out. We are considering moving our CDNs to AWS or Google because Azure support has become a bad joke. This incident is all the evidence you need.
Barry Bahrami 26 Reputation points

2025-11-05T17:45:37.0466667+00:00

I wouldn't be holding operations and incurring ongoing impact to business. IMHO, you should move the FD service over to another. Imperva, Cloud Flare, etc.. You don't necessarily need to be stuck where you are.
Ali Reaziat 25 Reputation points

2025-11-05T19:09:35.6866667+00:00

It's Nov 5 and still locked! What is the ETA? Our business has practically been shut down since last Friday
Mitchell Moore 10 Reputation points

2025-11-05T21:13:05.8733333+00:00

Hello, as of writing this post it is 21:11 GMT. Is there any ETA on when this will be fixed? It was my understanding that November 5th was the 'fix' date, although I never saw an official source claiming this.

I understand if there is no answer, but I would really appreciate at least some sort of ETA on the matter. Communication on this issue has been really poor from Microsoft's end.
Mark Frick 55 Reputation points

2025-11-05T21:41:52.4366667+00:00

I have not seen any official notice from Azure but I was able to submit a FD change for a certificate because I kept trying every hour. It took a very long time to finish but it did complete. That said, Azure did not handle this incident well. On my other App Services there is marketing note about moving to Front Door ... lol ... you have to be kidding now.
Mark Frick 55 Reputation points

2025-11-05T21:55:13.5633333+00:00

Front Page ... that ages me ... Front Door is the correct term
Angel Cruz 0 Reputation points

2025-11-05T22:52:26.1166667+00:00

Now it's working, I have deleted a front door without issues a minutes ago, thks
Oporto, Leonardo 0 Reputation points

2025-11-05T23:26:53.3566667+00:00

As I understand this would be solved on nov 5. But I don't see any update. Does anyone have any info?

Thanks
Angel Cruz 0 Reputation points

2025-11-06T01:03:23.5933333+00:00

Now it's working, I have deleted a front door without issues a minutes ago, thks
Anonymous

2025-11-06T03:52:51.78+00:00

Hello @Nandipally, Dheeraj,

Could you confirm whether you can be able to configure for all create, update, delete, WAF, and cache purge actions for Azure Front Door and CDN profiles? These operations may take up to 45 minutes to complete for added safety.
Salimath, Vishwanath (623) 5 Reputation points

2025-11-06T04:37:12.9866667+00:00

It’s working now, however, the workflow took around 35 minutes to complete.
Seleke, Tshepo T 0 Reputation points

2025-11-06T06:43:28.7833333+00:00

Anybody aware what could be causing https://js.monitor.azure.com/scripts/b/ai.config.1.cfg.json to surface 503 errors taking the whole app service
Anonymous

2025-11-06T17:47:40.44+00:00

Hello @Nandipally, Dheeraj,

The temporary Service Management restrictions on Azure Front Door have been lifted on 5th November, and customers can now resume their configuration changes.

The Azure portal also reflects this update as a banner:

The backend team is actively monitoring the platform. And in case of any issues, we will reach out to the backend team for further assistance.

Reference: Azure Front Door frequently asked questions (FAQ) | Microsoft Learn
Shanzs 0 Reputation points

2025-11-07T08:23:52.5833333+00:00

Created AFD profile Nov 7 2025 8:00 AM UTC. While I am able to complete the configuration, I am unable to access the AFD endpoint from browser. Browser error ...

Page not found

Oops! We weren't able to find your Azure Front Door Service configuration. If it's a new configuration that you recently created, it might not be ready yet. You should check again in a few minutes. If the problem persists, please contact Azure support.

Alert on Azure portal
Anonymous

2025-11-11T17:47:33.32+00:00

Hello @Shanzs,

Kindly raise a ticket in the Q&A portal regarding the issue you are facing, and we will get back to you.

Regard's
Jeevan S

Answer 1

Hello @Nandipally, Dheeraj,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

The temporary restrictions on Azure Front Door have been lifted as of November 5, so you can now resume your configuration changes without any issues.

As part of our incident response, the team is conducting an internal review to understand what happened and will share their findings soon. Once complete, a Final Post Incident Review (PIR) will be published here: https://azure.status.microsoft/en-us/status/history/

To stay informed and receive notifications when the PIR is available, please make sure you’ve set up Azure Service Health alerts:

Azure Service Health alerts

Post Incident Reviews

For additional guidance:

Monitoring granular impact: https://aka.ms/AzPIR/Monitoring

Preparing for cloud incidents: https://aka.ms/incidentreadiness

If you’re facing any further issues or need assistance, please reach out to us on this forum post. Thank you!

Azure status history | Microsoft Azure

Check the status history of Microsoft Azure services here.

Please do not forget to "Accept the answer” and “up-vote it” wherever the information provided helps you, this can be beneficial to other community members**.** It would be greatly appreciated and helpful to others.

All Changes to Azure Frondoor Configuration are blocked currently

Page not found

1 answer

Your answer