This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 35%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
We are seeing incorrect geolocation details for one of our company’s public IP addresses in Microsoft Entra ID sign-in logs. Microsoft is showing logins originating from southern Ontario, Canada (the GTA), but this IP is actually assigned to our business network in Winnipeg, MB, Canada.
We have reviewed the location results of 11 geolocation providers. One of the eleven had an erroneous location that was very similar to what Azure is still returning. That location provider was notified, and published corrected results over 20 days ago. However, Microsoft Entra sign-in logs continue to show the incorrect location.
We have also previously tried creating a custom "IP address range" object via Defender Cloud Apps.
At this point, we don't know how to fix the problem.
I think we need Microsoft to update its internal geolocation mapping for this IP address.
Additional Microsoft Entra services and features related to identity, access, and network security
I think that Azure’s still reading a stale mmdb slice for ur /24… that shard just doesnt roll even if the upstream geo feed fixed it. u basically need MS to bump the backend ingest for that block so the geo data refreshes.
Thanks for your comment. I've come to the same conclusion, but not sure how to get assistance. I was hoping someone from Microsoft might reply here.
I first opened a ticket via the M365 Admin Center and was told they don't help with this type of problem - the ticket was closed out as a result. I then tried opening a ticket via the Entra portal - I provided all the information requested to open a ticket and then just before submitting the ticket, it indicated a paid support plan is required. I'm at a loss here.
sorry… the only thing that actually moves that stale geo slice is an Azure support case, so the simple way is to spin up a free Azure trial, go to Help + support → Create a support request → Technical → Networking, paste ur /24 and the correct coords in a txt, and they’ll refresh the ingest.