Health Probe Checking Exposes internal Servername

Hi All,

I just recently found that Health Probe Checking exposes the internal servername along with 200 OK response.

This happen even when I have Reverse Proxy in-place which is suppose to hide our internal servers. I could say its kind of similar situation wherein we have internal servernames in email headers.

I'm concerned in this case, as all this happens without any authentication, from any device, from any network.

Health Probe Checking

To ensure that load balancers do not route traffic to a Client Access server that Managed Availability has marked as offline, load balancer health probes must be configured to check<virtualdirectory>/healthcheck.htm (e.g., https://mail.contoso.com/owa/healthcheck.htm). Note thathealthcheck.htm does not actually exist within the virtual directories; it is generated in-memory based on the component state of the protocol in question.

https://mail.contoso.com/owa/healthcheck.htm

200 OK
CO2PRxxCA0xx.0xxA.MGD.MSFT.NET

NOTE- I have replaced some chars with 'xx'

How do we tell Managed Availability not to expose the servername or edit the information being displayed.

Regards,

Satyajit

Please“Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.