Forum Discussion
Incorrect Network Egress Location
Hi guys. I just stumbled on this new connectivity analyzer and was playing around with it. I'm seeing the same issue. We are on Comcast fiber in Elkridge, MD but it says our egress location is in Ninnescah, KS over 1,100 miles away.
- We have been fighting this issue since Feb with Microsoft. They just say you need to set a local egress to fix this but there isn’t a person that has a clue on how to do this. Microsoft techs don’t want to help with the situation and they just blame someone else. If you look at the trace routes as soon as you hit the Microsoft network it takes you everywhere else but where it should be. They can’t even tell you how their tool is able to tell the location.
- PaulAndrew
Microsoft
Dan Rush We corrected the issues that Jason and John reported some time back. It was showing wrong locations for a small percentage of people. The location detection for the Microsoft 365 Admin Center network connectivity reporting is described on this doc page: https://docs.microsoft.com/en-us/Microsoft-365/Enterprise/office-365-network-mac-perf-overview
Regards,
Paul
- PaulAndrewCan you PM me your public IP Address please? I can take a look.
PaulPaulAndrew We have the same problem when running M365 network connectivity manual tests from home office on a corporate laptop with VPN with split tunnelling enabled for M365 per MS proxy PAC files instructions as compared to using a personal device on the same home networking. The network path in the M365 report for those two scenarios is very similar but the tests run from corporate laptop shows egress as Vancouver, BC even though we are in Ottawa, ON. From personal device the network egress location correctly shows as Ottawa, ON. While trivial to overlook it undermines the trustworthiness of the overall report.
