Add FAQ about multiple X-Azure-Ref values

[Jagan Peddabavi (Jpeddabavi)]

  - 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.

[prmerger-automator]

Jagan Peddabavi (@Jpeddabavi) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[prmerger-automator]

Jagan Peddabavi (@Jpeddabavi) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit e0ebb7f:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/frontdoor/front-door-faq.yml	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.

[Copilot]

Note

Copilot was unable to run its full agentic suite in this review.

Pull request overview

Adds a new FAQ entry to explain why backend application logs may show multiple X-Azure-Ref correlation identifiers when traffic flows through Azure Front Door.

Changes:

• Adds a new question/answer describing primary vs. internal X-Azure-Ref values.
• Clarifies that extra values are internal to the platform and not multiple client requests.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Diana Richards (v-dirichards)]

Hussein Al Kazwini (@halkazwini)

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[learn-build-service-prod]

Learn Build status updates of commit 3ccec1b:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/frontdoor/front-door-faq.yml	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.

[Jagan Peddabavi (Jpeddabavi)]

#sign-off

[prmerger-automator]

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. Hussein Al Kazwini (@halkazwini)