Merge pull request #307866 from halkazwini/afd-faq

AFD FAQ update

Author: prmerger-automator[bot]

articles/frontdoor/front-door-faq.yml

@@ -6,7 +6,7 @@ metadata:
   ms.author: halkazwini
   ms.service: azure-frontdoor
   ms.topic: faq
-  ms.date: 03/23/2025
+  ms.date: 11/05/2025
 title: Azure Front Door frequently asked questions (FAQ) 
 summary : |
   This article provides answers to the most frequently asked questions about Azure Front Door features and functionality. If you don't see the answer to your question, you can contact us through the following channels (in escalating order):
@@ -70,10 +70,10 @@ sections:
       - question: |
           What is the estimated time for deploying an Azure Front Door? Does my Front Door remain operational during the update process?
         answer: |
-          The deployment time for new Front Door configurations varies depending on the type of change. Typically, it takes between 3 and 20 minutes for the changes to propagate to all our edge locations worldwide.
+          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.
           
           > [!NOTE]  
-          > Custom TLS/SSL certificate updates might take longer, from several minutes up to an hour, to be deployed globally.
+          > Custom TLS/SSL certificate updates might take longer, up to an hour, to be deployed globally.
           
           Updates to routes or origin groups/backend pools are seamless and don't cause any downtime (assuming the new configuration is correct). Certificate updates are also done atomically, so there's no risk of outage.
       - question: |