IP Geolocation Correction Request - 64.239.232.0/22

Open a private Microsoft Entra support request to have [IP Address]/22 escalated for correction in Microsoft’s IP-geolocation mapping; Microsoft Q&A cannot directly update the production database.

Submit the correction request

1. Sign in to the Microsoft Entra admin center as at least a Service Support Administrator.
2. Go to Diagnose and solve problems → New support request.
3. Describe the issue as Microsoft Entra sign-in logs reporting incorrect IP geolocation.
4. Continue past the recommended solutions, complete Additional details, and select Create. Microsoft recommends including the start date, reproduction steps, and relevant logs or diagnostics.^1^
5. Include the following in the private ticket:
   • Subnet: [IP Address]/22
   • Incorrect location: Canada
   • Requested location: East Wenatchee, Washington, United States
   • APNIC registration showing country: US
   • Authoritative geofeed URL and the exact matching entry
   • Several affected public IP addresses within the /22
   • Recent affected sign-in timestamps, correlation/request IDs, and screenshots showing the IP and reported location
   • Business impact, including the affected compliance or Conditional Access controls
   • Tenant ID and subscription details only in the private support request, not in this public thread

Use a concise request such as:

Please escalate this request to the Microsoft Entra engineering team for an IP-geolocation mapping correction. Microsoft Entra sign-in logs currently map [IP Address]/22 to Canada. The registered and authoritative location is East Wenatchee, Washington, US. APNIC and the authoritative geofeed have already been updated. Attached are representative sign-in events, timestamps, correlation IDs, registry data, and geofeed evidence.

This matches previous Entra cases where Microsoft engineering corrected Canada-to-US and other inaccurate backend mappings; customers were then asked to check their latest sign-ins.^2^ Registry and geofeed updates alone do not immediately change Entra’s result because country/region resolution uses Microsoft’s periodically updated mapping table.^3^

Mitigate policy impact while the correction is pending

If the compliance problem comes from Conditional Access treating this corporate egress range as an untrusted location:

1. Sign in as a Conditional Access Administrator.
2. Go to Entra ID → Conditional Access → Named locations.
3. Select New location, choose an IP-ranges location, and enter:

      [IP Address]/22
   

4. Optionally select Mark as trusted location only if the entire subnet is controlled and trusted by your organization.
5. Update the relevant Conditional Access policy to include or exclude that named location according to the intended access rule.

IP-based named locations can be used in Conditional Access and can improve Entra ID Protection risk calculations.^3^

This is an interim policy mitigation; it does not correct the city or country displayed in sign-in logs. Avoid broadly excluding the subnet from MFA or other controls unless that bypass is explicitly required and risk-approved.

After Microsoft confirms the backend update, generate new sign-ins from representative addresses in the block and inspect Entra ID → Monitoring & health → Sign-in logs. Preserve the support case if new events still show Canada.

References

1. Find help and get support for Microsoft Entra
2. How do I change GeoLocation on a public IP address showing wrong location/region in Azure Sign-in Logs? - Microsoft Q&A
3. Conditional Access: Network assignment