Purge is taking long time to complete

Question

Purge is taking long time to complete

Anonymous

Since the recent issue with Azure CDN was addressed, I've noticed that purging the CDN now takes between 35 to 40 minutes. Before this, it used to be completed in under 10 minutes. Is it the new purging time or there is any issue related to purging?

Anonymous

2025-11-25T13:40:32.3033333+00:00

Will it take around 40 minutes to purge a single image?
Anonymous

2025-11-25T14:16:07.6533333+00:00

From above information it is mentioned that It will take 45mins to purge 100 URL's and we are process 1 image at a time still it is taking around 40 mins?
Vallepu Venkateswarlu 10,590 Reputation points Microsoft External Staff Moderator

2025-11-25T14:35:33.9966667+00:00

Hi @ Shoeb,
Even when purging a single image, Azure Front Door follows the same global propagation process used for larger batches. As mentioned in estimated time, all cache purge operations can take up to 45 minutes to fully propagate worldwide.

Each purge request can include up to 100 URLs (combination of domain and path). The first batch is processed and takes effect within approximately 45 minutes.

This is why your single-file purge is completing in around 35–45 minutes, which is within the expected platform behavior.
Anonymous

2025-11-25T15:18:55.71+00:00

Was this timing updated recently?
Vallepu Venkateswarlu 10,590 Reputation points Microsoft External Staff Moderator

2025-11-25T16:16:26.8933333+00:00

Hi @ Shoeb,

The internal team is working to reduce the current propagation time from 45 minutes to approximately 15 minutes. You can track this progress through the Azure Front Door Service History, and once the improvement is completed, the update will be reflected in the Post Incident Review (PIR).

Please "upvote" if the information helped you. This will help us and others in the community as well.
Anonymous

2025-11-25T16:18:11.2033333+00:00

Thank you for this information
Vallepu Venkateswarlu 10,590 Reputation points Microsoft External Staff Moderator

2025-11-25T16:21:26.9266667+00:00

Hi @ Shoeb,

I hope the information I provided is helpful in addressing all your queries.
David Gregory 0 Reputation points

2026-01-09T20:14:44.22+00:00

It has been over 2 months since the original incident that pushed the purge times up to 45 minutes, so how much longer are we expected to wait for this to be fixed? When deploying critical patches to our front end system waiting another ~45 minutes is not acceptable. In the documentation linked from this thread it says "Cache purging can take up to 10 minutes to propagate across all Azure Front Door POP locations.", which clearly is currently not the case.

If this isn't fixed soon then we will be forced to consider other CDNs, but that will involve a lot more work and cost.

Answer accepted by question author

0 additional answers

Your answer

Anonymous

2025-11-25T13:40:32.3033333+00:00

Will it take around 40 minutes to purge a single image?
Anonymous

2025-11-25T14:16:07.6533333+00:00

From above information it is mentioned that It will take 45mins to purge 100 URL's and we are process 1 image at a time still it is taking around 40 mins?
Vallepu Venkateswarlu 10,590 Reputation points Microsoft External Staff Moderator

2025-11-25T14:35:33.9966667+00:00

Hi @ Shoeb,
Even when purging a single image, Azure Front Door follows the same global propagation process used for larger batches. As mentioned in estimated time, all cache purge operations can take up to 45 minutes to fully propagate worldwide.

Each purge request can include up to 100 URLs (combination of domain and path). The first batch is processed and takes effect within approximately 45 minutes.

This is why your single-file purge is completing in around 35–45 minutes, which is within the expected platform behavior.
Anonymous

2025-11-25T15:18:55.71+00:00

Was this timing updated recently?
Vallepu Venkateswarlu 10,590 Reputation points Microsoft External Staff Moderator

2025-11-25T16:16:26.8933333+00:00

Hi @ Shoeb,

The internal team is working to reduce the current propagation time from 45 minutes to approximately 15 minutes. You can track this progress through the Azure Front Door Service History, and once the improvement is completed, the update will be reflected in the Post Incident Review (PIR).

Please "upvote" if the information helped you. This will help us and others in the community as well.
Anonymous

2025-11-25T16:18:11.2033333+00:00

Thank you for this information
Vallepu Venkateswarlu 10,590 Reputation points Microsoft External Staff Moderator

2025-11-25T16:21:26.9266667+00:00

Hi @ Shoeb,

I hope the information I provided is helpful in addressing all your queries.
David Gregory 0 Reputation points

2026-01-09T20:14:44.22+00:00

It has been over 2 months since the original incident that pushed the purge times up to 45 minutes, so how much longer are we expected to wait for this to be fixed? When deploying critical patches to our front end system waiting another ~45 minutes is not acceptable. In the documentation linked from this thread it says "Cache purging can take up to 10 minutes to propagate across all Azure Front Door POP locations.", which clearly is currently not the case.

If this isn't fixed soon then we will be forced to consider other CDNs, but that will involve a lot more work and cost.

Answer 1

Hi @Shoeb,

Welcome to Microsoft Q&A Platform.

The Configuration propagation times for all create, update, delete, WAF, and cache purge operations for Azure Front Door and CDN profiles might take up to 45 minutes for added safety. Ongoing platform enhancements are underway that will further reduce this time.

A purge request can process up to 100 URLs, and since each batch takes about 45 minutes to complete, any additional URLs must be purged in sequential 45-minute batches to avoid request rejection.

User's image

Ref: What is the estimated time for deploying an Azure Front Door?

The internal team is working to reduce the current propagation time from 45 minutes to approximately 15 minutes. You can track this progress through the Azure Front Door Service History, and once the improvement is completed, the update will be reflected in the Post Incident Review (PIR).

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

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

Answer 2

The purging time for Azure CDN can take up to 45 minutes for configuration propagation, including operations like cache purges. If you are experiencing purging times of 35 to 40 minutes, it may be within the expected range, especially if there have been recent changes or updates to the service. It's important to note that if you submit multiple purge requests, each batch can take approximately 45 minutes to process, and submitting new requests before the previous ones complete can lead to rejections.

If the purging process is consistently taking longer than expected, it may be worth checking for any ongoing issues or updates from Azure support.

References:

Azure Front Door frequently asked questions (FAQ)