If I had to guess, you're not actually getting a server ping. You're likely getting routed to the closest point of presence on the MSFT network. In KY, closest datacenter is likely northern VA. But you might actually be hitting the msft network at an even closer location and you're getting the ping from there. Obviously, azure.microsoft.com isn't one server but a geographically distributed group...


The host is behind a CDN, it is using local technology with your internet provider, which is why you get such low latency. To find out which Azure Region is the closest to you with the lowest ping times, go to [https://www.azurespeed.com/Azure/Latency](https://www.azurespeed.com/Azure/Latency) and check the latency charts.


[azure.microsoft.com](https://azure.microsoft.com) points to the marketing website for Azure. Why do you want to know where it is located? It is most likely behind a CDN so it is "everywhere". ICMP is blocked so your pings will not work. You can type that hostname into your browser and use the Network tab of the developer console to see where the HTTP traffic is coming from. My browser says: Request URL: https://azure.microsoft.com/en-us/ Request Method: GET Status Code: 200 Remote Address: []( Your result might be different.




I still can't tell precisely which server I'm connecting to given this information.


How precise are you looking for? Most of that info is held secret for a variety of reasons.


Just the city.


Do a traceroute you will know which city.




When I ping these servers in cmd, it times out. I read that it's from some sort of protection protocol or something, but how can I get around that and figure out which server I'm actually connecting to when getting 5 ping?


Even if you trace their IP address it hits their any-cast address. It will hit your ISP, and then hit the local proof of presence. https://docs.microsoft.com/en-us/azure/cdn/cdn-pop-locations


PSPing could also be used as it does a TCP latency check rather than ICMP (see here: [https://docs.microsoft.com/en-us/sysinternals/downloads/psping](https://docs.microsoft.com/en-us/sysinternals/downloads/psping)) As others have said, however, pinging [azure.microsoft.com](https://azure.microsoft.com) is just going to hit the CDN (Front Door) point of presence closest to you


Have a look at https://www.azurespeed.com/Azure/Latency You can test the latency to azure DCs.


These days it doesn’t really matter unless you need to deal w data storage regulations. Microsoft won’t tell you exactly where a server is, and for some global services like AzureAD it will always change depending on load