Subnet Geolocation Wrong

Question

Hello,

Microsoft’s IP geolocation seems to be incorrectly marking one of my subnets as MU, when it resides in ZA. I’ve checked my login activity logs and that’s where I’ve seen this.

Checking public IP geolocation DBs, and I can confirm they are correct.

How does this get resolved? I’ve submitted corrections to Bing Maps, but it’s still problematic.

I got new IP subnets, and having the same issue on them. Last time, MS assisted me over private message via https://learn.microsoft.com/en-us/answers/questions/5845716/microsoft-ip-geolocation?page=1&orderby=Helpful&comment=answer-12709374&translated=false#newest-answer-comment

Please may someone reach out to me, so I can provide the new IP subnet so this can be resolved ? @Raja Pothuraju as discussed.

Answer 1

Hello Matthew Burnett,

Greetings! Thanks for raising this question in the Q&A forum.

Incorrect IP geolocation tagging on sign-in and risk detection logs (showing as MU instead of ZA) is a known type of issue, and it is not something that can be corrected from the customer side through Entra ID settings, since the geolocation data is sourced from Microsoft's internal IP geolocation database rather than from your tenant configuration. Public geolocation database corrections, such as the one you submitted to Bing Maps, typically do not propagate to the dataset Microsoft Entra ID uses internally, which is why the issue persists even after that correction.

1. Avoid posting the specific subnet publicly Since resolving this requires Microsoft to manually correct internal geolocation mapping for your specific IP ranges, it is best not to share the exact subnet details in a public forum post. The private message route you used previously for your earlier subnet is the correct channel for this. Open a formal Azure Support request for the new subnet Rather than relying only on a forum mention, the most reliable path is to open a support case under the Entra ID or Azure networking category, referencing your earlier case or thread where this was resolved for your previous subnet, and providing the new subnet privately through the support ticket's secure channel.

https://portal.azure.com → Help + Support → Create a support request

Reference your prior resolved case

When opening the new request, link back to your earlier thread and case so the support engineer can see the precedent and apply the same internal correction process used last time, which should speed up resolution.

If you do not have an Azure support plan

If you are on a free tier without paid support, you can still open a basic technical support request tied to the Entra ID service, since geolocation data accuracy issues are typically handled as a backend data correction rather than a billable support engagement.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.