Clarification on Azure Front Door Handling of "Server" Response Header

Dear Azure Team,

I hope this message finds you well. I'm reaching out to seek clarification on an observed behavior related to the Azure Front Door service.

During my recent deployment, I noticed that when directly accessing the backend App Service endpoint, the response headers included the "Server" header (e.g., "Server: nginx/1.14.0"). However, when accessing the same application through the Azure Front Door, the "Server" response header was no longer present.

I thoroughly reviewed the Azure Front Door documentation but could not find any explicit mention of the service removing or modifying the "Server" response header by default. I understand that this practice is common among reverse proxies and Web Application Firewalls for security purposes, but I appreciate transparency and would like to understand the rationale behind this behavior better.

Could you kindly confirm if this is an expected and documented behavior of Azure Front Door? If so, I would greatly appreciate if you could provide a reference to the relevant documentation or clarify the reasoning behind this decision.

Additionally, if there is a way to configure Azure Front Door to preserve the "Server" response header (should I have a specific requirement for it), I would be grateful if you could guide me through the necessary steps.

Thank you in advance for your assistance. I appreciate your time and effort in ensuring the Azure documentation remains comprehensive and up-to-date.

Best regards,
Lucas