Azure Front Door Propagation Time

Question

Azure Front Door Propagation Time

UWinkenjo 35

After the recent incident with Azure Front Door, restrictions have been lifted but confiugration propagation time is still 45 minutes. This blocks us in many ways, as we need to purge content automatically and also have a lot of configuration changes upcoming due to a platform relaunch, each action takes ages. I didn't find information on next steps anywhere. Is there a timeline when we can expect to have everything working as usual again?

UWinkenjo 35 Reputation points

2025-11-19T11:09:40.9666667+00:00

Dear @Vallepu Venkateswarlu ,

thank you very much for your answer, I really appreciate it!

But yes, I read all these documentations and official statements already, of course. Unfortunately, this doesn't really help, as it's not concrete enough. The question is more like:

What about the ongoing platform enhancements that are underway, are we now talking about a week, a month, a year or even longer? Do you have any idea what we can expect here?
Vallepu Venkateswarlu 10,270 Reputation points Microsoft External Staff Moderator

2025-11-19T12:00:14.9366667+00:00

Hi @Udo,

Thanks for your reply,

As we do not have a specific time boundary at the moment, the information will be published on the Azure Front Door FAQ page once it is updated.

You can also refer to the official Azure status history (Preliminary PIR), which explains that the introduction of new stages in the configuration propagation pipeline, along with additional “bake time” between stages, has led to increased configuration propagation times.

This affects all operations on the Azure Front Door platform, including create, update, delete, WAF operations, and cache purges.

If you would like to share feedback, you can submit a request through the feedback channel. team will review it and respond as soon as possible.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
UWinkenjo 35 Reputation points

2025-11-19T13:01:06.2066667+00:00

Dear @Vallepu Venkateswarlu ,

this helps. So absolutely no specific timeframe at the moment, I will follow the resources.

Thanks again for your help!
RKProphet2012 0 Reputation points

2025-11-26T19:40:43.26+00:00

This is really quite difficult for us right now. We're a very small team and new to using AFD and have a more complicated SPA boot in and associated microservice structure for bot-SSR and seo/social-agents/crawlers that needs iterative attempts to get right for what we're trying to do, and I've been spending all day over the last week just trying to get our configuration setup correctly and bringing down our main site. Fortunately, we're not fully launched yet, but I am just struggling with trying to have progress and losing so much time.

I would appreciate any clarity that may be available as to when this propagation time will be reduced. Or if there are any good, up-to-date guides that relate to some of what we're trying to do (AFD Standard not classic), that would be helpful. Thank you!
Jakhongir Mustafaev 65 Reputation points

2025-12-20T14:26:15.0933333+00:00

45 minutes actually prolonging up to 1.5 - 2 hours, and this is making things quite difficult and slow to test in prod with caching and CDN. Yes, it is taking days, instead of hours, agree with the above comments to deploy and test.

Is there any way the Azure AFD team can expedite those fixes before everyone moves to Cloudflare?) Actually, we are literally considering it.
Reto Klaus 5 Reputation points

2026-01-17T10:38:04.49+00:00

This behavior makes Azure Front Door extremely difficult to operate and maintain. A deployment time of up to 45 minutes just to test configuration changes - without clear visibility into when those changes are actually applied - is not acceptable from an operational perspective.

It effectively means waiting (potentially 45 minutes) while repeatedly refreshing the service, hoping the configuration has propagated.

This also creates serious challenges during go-lives. We cannot reliably validate all settings in advance, and once a configuration is deployed to production, any required correction results in another long wait before we can test again. This significantly increases operational risk and prolongs incidents.

If this behavior continues, Azure Front Door becomes unsuitable for any serious production environment, and we would be forced to evaluate alternative solutions that provide predictable and transparent configuration propagation.
Brad Moutoux 0 Reputation points

2026-05-28T15:48:55.46+00:00

Azure Front Door and its propagation time is UNACCEPTABLE. No other provider has such a fantastically huge LAG time. This makes it almost impossible to build, update, or troubleshoot ANYTHING because you just never know if it is all propagated or not unless you keep checking. By keep checking, I mean you keep waiting, and waiting. And waiting. If Microsoft wants to be in this field it needs to learn how to play this game. I just moved my organization to AFD and CDN from Cloudflare. And so far, the results have been absolutely horrendous sure to the WAIT times.

I thought Microsoft was trying to stop being a POS, but I guess not.
Vallepu Venkateswarlu 10,270 Reputation points Microsoft External Staff Moderator

2026-05-28T19:39:43.9866667+00:00

Hi Brad Moutoux,
The Configuration propagation times for a single create, update, delete, WAF, and cache purge operation for Azure Front Door and CDN profiles might take up to 20 minutes for added safety. Back-to-back changes can extend the total deployment time to approximately 40 minutes.

Ref: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-faq#what-is-the-estimated-time-for-deploying-an-azure-front-door--does-my-front-door-remain-operational-during-the-update-process-
UWinkenjo 35 Reputation points

2026-05-29T08:04:31.8533333+00:00

Hi @Vallepu Venkateswarlu , I totally agree with Brad and the others here. The propagation time has been reduced, but 40 minutes (and it's usually about 50 minutes in reality) is still unacceptable. I work with hundreds of domains, and additonally, there is an automated purge process from our content management system where editors see content changes very late. The biggest problem is that I can't really react on any DDoS or other attacks any more, because when the sites are attacked and I change anything in the Front Door WAF, the attack is already over when the changes are applied. What a nightmare!

The worst thing though is that there is absolutely no information on any progress for months now. I would be very happy if you could do some real research here, if somehow possible - the help page doesn't help at all. This problem should really be the No 1 priority at Microsoft. For me, it looks like no one cares...

Answer accepted by question author

0 additional answers

Your answer

UWinkenjo 35 Reputation points

2025-11-19T11:09:40.9666667+00:00

Dear @Vallepu Venkateswarlu ,

thank you very much for your answer, I really appreciate it!

But yes, I read all these documentations and official statements already, of course. Unfortunately, this doesn't really help, as it's not concrete enough. The question is more like:

What about the ongoing platform enhancements that are underway, are we now talking about a week, a month, a year or even longer? Do you have any idea what we can expect here?
Vallepu Venkateswarlu 10,270 Reputation points Microsoft External Staff Moderator

2025-11-19T12:00:14.9366667+00:00

Hi @Udo,

Thanks for your reply,

As we do not have a specific time boundary at the moment, the information will be published on the Azure Front Door FAQ page once it is updated.

You can also refer to the official Azure status history (Preliminary PIR), which explains that the introduction of new stages in the configuration propagation pipeline, along with additional “bake time” between stages, has led to increased configuration propagation times.

This affects all operations on the Azure Front Door platform, including create, update, delete, WAF operations, and cache purges.

If you would like to share feedback, you can submit a request through the feedback channel. team will review it and respond as soon as possible.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
UWinkenjo 35 Reputation points

2025-11-19T13:01:06.2066667+00:00

Dear @Vallepu Venkateswarlu ,

this helps. So absolutely no specific timeframe at the moment, I will follow the resources.

Thanks again for your help!
RKProphet2012 0 Reputation points

2025-11-26T19:40:43.26+00:00

This is really quite difficult for us right now. We're a very small team and new to using AFD and have a more complicated SPA boot in and associated microservice structure for bot-SSR and seo/social-agents/crawlers that needs iterative attempts to get right for what we're trying to do, and I've been spending all day over the last week just trying to get our configuration setup correctly and bringing down our main site. Fortunately, we're not fully launched yet, but I am just struggling with trying to have progress and losing so much time.

I would appreciate any clarity that may be available as to when this propagation time will be reduced. Or if there are any good, up-to-date guides that relate to some of what we're trying to do (AFD Standard not classic), that would be helpful. Thank you!
Jakhongir Mustafaev 65 Reputation points

2025-12-20T14:26:15.0933333+00:00

45 minutes actually prolonging up to 1.5 - 2 hours, and this is making things quite difficult and slow to test in prod with caching and CDN. Yes, it is taking days, instead of hours, agree with the above comments to deploy and test.

Is there any way the Azure AFD team can expedite those fixes before everyone moves to Cloudflare?) Actually, we are literally considering it.
Reto Klaus 5 Reputation points

2026-01-17T10:38:04.49+00:00

This behavior makes Azure Front Door extremely difficult to operate and maintain. A deployment time of up to 45 minutes just to test configuration changes - without clear visibility into when those changes are actually applied - is not acceptable from an operational perspective.

It effectively means waiting (potentially 45 minutes) while repeatedly refreshing the service, hoping the configuration has propagated.

This also creates serious challenges during go-lives. We cannot reliably validate all settings in advance, and once a configuration is deployed to production, any required correction results in another long wait before we can test again. This significantly increases operational risk and prolongs incidents.

If this behavior continues, Azure Front Door becomes unsuitable for any serious production environment, and we would be forced to evaluate alternative solutions that provide predictable and transparent configuration propagation.
Brad Moutoux 0 Reputation points

2026-05-28T15:48:55.46+00:00

Azure Front Door and its propagation time is UNACCEPTABLE. No other provider has such a fantastically huge LAG time. This makes it almost impossible to build, update, or troubleshoot ANYTHING because you just never know if it is all propagated or not unless you keep checking. By keep checking, I mean you keep waiting, and waiting. And waiting. If Microsoft wants to be in this field it needs to learn how to play this game. I just moved my organization to AFD and CDN from Cloudflare. And so far, the results have been absolutely horrendous sure to the WAIT times.

I thought Microsoft was trying to stop being a POS, but I guess not.
Vallepu Venkateswarlu 10,270 Reputation points Microsoft External Staff Moderator

2026-05-28T19:39:43.9866667+00:00

Hi Brad Moutoux,
The Configuration propagation times for a single create, update, delete, WAF, and cache purge operation for Azure Front Door and CDN profiles might take up to 20 minutes for added safety. Back-to-back changes can extend the total deployment time to approximately 40 minutes.

Ref: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-faq#what-is-the-estimated-time-for-deploying-an-azure-front-door--does-my-front-door-remain-operational-during-the-update-process-
UWinkenjo 35 Reputation points

2026-05-29T08:04:31.8533333+00:00

Hi @Vallepu Venkateswarlu , I totally agree with Brad and the others here. The propagation time has been reduced, but 40 minutes (and it's usually about 50 minutes in reality) is still unacceptable. I work with hundreds of domains, and additonally, there is an automated purge process from our content management system where editors see content changes very late. The biggest problem is that I can't really react on any DDoS or other attacks any more, because when the sites are attacked and I change anything in the Front Door WAF, the attack is already over when the changes are applied. What a nightmare!

The worst thing though is that there is absolutely no information on any progress for months now. I would be very happy if you could do some real research here, if somehow possible - the help page doesn't help at all. This problem should really be the No 1 priority at Microsoft. For me, it looks like no one cares...

Answer 1

Hi @Winkenjohann, Udo ext. /BSS HAM •,

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

Yes, Microsoft has recently updated the Azure Front Door FAQ, and it clearly states that.

Configuration propagation times for create, update, delete, WAF, and cache purge operations can take up to 45 minutes.

This applies to both Azure Front Door and Azure CDN profiles.

Microsoft also mentions that ongoing platform enhancements are planned to reduce this time, but no public timeline has been announced.

User's image

You can find the official Azure status history (Preliminary PIR) that he introduction of new stages in the configuration propagation pipeline was coupled with additional ‘bake time’ between stages, which has resulted in an increase in configuration propagation time, for all operations including create, update, delete, WAF operations on AFD platform, and cache purges. We continue to work on platform enhancements to ensure a robust configuration delivery pipeline and further reduce the propagation time. For more details on these temporary propagation delays.

As we do not have a specific time boundary at the moment, the information will be published on the Azure Front Door FAQ page once it is updated.

You can also refer to the official Azure status history (Preliminary PIR), which explains that the introduction of new stages in the configuration propagation pipeline, along with additional “bake time” between stages, has led to increased configuration propagation times.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Accept" the answer, if the information helped you. This will help us and others in the community as well.

Rakesh Karia 5 Reputation points

2025-12-23T15:26:16.01+00:00

We have also faced the same issue. We have migrated to Amazon Cloudfront free plan and it works like a charm. propagation takes only less than a minute.