From e0ebb7f1727cb1fdcc269f449dfa283ef5729f6d Mon Sep 17 00:00:00 2001
From: Jagan Peddabavi <157447885+Jpeddabavi@users.noreply.github.com>
Date: Tue, 1 Sep 2026 17:36:56 -0700
Subject: [PATCH 1/2] Add FAQ about multiple X-Azure-Ref values

      - 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 don't indicate multiple client requests.
---
 articles/frontdoor/front-door-faq.yml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/articles/frontdoor/front-door-faq.yml b/articles/frontdoor/front-door-faq.yml
index 3e52e94e2e10..b8d24dbf2544 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 don't indicate multiple client requests.
+        
       - question: |
           Can I use Private Link to connect Azure Front Door to Azure Key Vault?
         answer: |

From 3ccec1ba423a23d3375277de9d6e474b093acbb4 Mon Sep 17 00:00:00 2001
From: Jagan Peddabavi <157447885+Jpeddabavi@users.noreply.github.com>
Date: Wed, 2 Sep 2026 09:53:00 -0700
Subject: [PATCH 2/2] Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---
 articles/frontdoor/front-door-faq.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/articles/frontdoor/front-door-faq.yml b/articles/frontdoor/front-door-faq.yml
index b8d24dbf2544..6e3eaec664c3 100644
--- a/articles/frontdoor/front-door-faq.yml
+++ b/articles/frontdoor/front-door-faq.yml
@@ -143,9 +143,9 @@ sections:
           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?
+          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 don't indicate multiple client requests.
+          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?