diff --git a/articles/frontdoor/front-door-faq.yml b/articles/frontdoor/front-door-faq.yml
index 3e52e94e2e10..6e3eaec664c3 100644
--- a/articles/frontdoor/front-door-faq.yml
+++ b/articles/frontdoor/front-door-faq.yml
@@ -142,6 +142,11 @@ sections:
         answer:  |
           To use Azure Front Door Standard or Azure Front Door (classic), you need a public IP address or a publicly resolvable DNS name. This requirement allows Azure Front Door to route traffic to your backend resources. You can use Azure resources like Application Gateways or Azure Load Balancers to route traffic to resources in a virtual network. If you use Azure Front Door Premium, you can use Private Link to connect to origins behind an internal load balancer through a private endpoint. For more information, see [Secure origins with Private Link](private-link.md).
 
+      - question: |
+          Why do I see multiple `X-Azure-Ref` values in my backend application logs when requests pass through Azure Front Door?
+        answer:  |
+          The `X-Azure-Ref` value displayed in the client response and Azure Front Door access logs represents the primary request correlation identifier generated by Azure Front Door. Additional `X-Azure-Ref` values observed only in backend application logs are expected and are internal correlation identifiers generated during request processing within the Azure Front Door platform. These internal identifiers are used by the service for request tracking and diagnostics and do not indicate multiple client requests.
+        
       - question: |
           Can I use Private Link to connect Azure Front Door to Azure Key Vault?
         answer: |