Report wrong geolocation of IP addresses in Azure

Question

Report wrong geolocation of IP addresses in Azure

Jay Hickman 0

Multiple users in India have reported issues connecting to the customer's VPN or AVD, with connection attempts failing. The public IP address for the user’s machine typically corresponds to either the BOM or HYD proxy, but when accessing the customer network, the customer observes those IP’s from different regions.

Summary of the issue:

Expected:
BOM Proxy/NAT IP range: 192.188.171.0/24 (should show BOM/Mumbai region)
HYD Proxy/NAT IP range: 206.126.100.0/24 (should show HYD/Hyderabad region)
Observed:
BOM Proxy IPs are appearing as tagged to Taipei, Taiwan.
HYD Proxy IPs are appearing as tagged to Austin, Texas.
Customers checked for the unsuccessful login logs and the IPs are being identified as belonging to Taipei or Austin rather than BOM or HYD. Multiple users in India have reported issues connecting to the customer's VPN or AVD, with connection attempts failing. The public IP address for the user’s machine typically corresponds to either the BOM or HYD proxy, but when accessing the customer network, the customer observes those IP’s from different regions. Summary of the issue:
- Expected:
- BOM Proxy/NAT IP range: 192.188.171.0/24 (should show BOM/Mumbai region)
- HYD Proxy/NAT IP range: 206.126.100.0/24 (should show HYD/Hyderabad region)
- Observed:
- BOM Proxy IPs are appearing as tagged to Taipei, Taiwan.
- HYD Proxy IPs are appearing as tagged to Austin, Texas.
- Customers checked for the unsuccessful login logs and the IPs are being identified as belonging to Taipei or Austin rather than BOM or HYD.

Multiple Geolocation services show both of these IP ranges at the correct location in India.

User's image

Alex Burlachenko 25,290 Reputation points MVP Volunteer Moderator

2025-10-01T09:43:12.58+00:00
hi Jay ,

the ip addresses are physically in india, but azure's security logs are showing them as taiwan and texas. this is a serious issue because it can block legitimate users.

the problem is that azure uses its own internal geo ip database for services like conditional access and threat detection, and that database is out of date for these specific ip ranges owned by oracle.

most important step is to report this directly to microsoft so they can update their geo ip data. you need to open a support ticket in the azure portal. for the service type, choose 'azure active directory' or 'microsoft entra id'. in the ticket, clearly explain that the ip ranges 192.188.171.0/24 and 206.126.100.0/24 are being incorrectly geolocated. provide the evidence from ip2location and ipinfo.io showing the correct location is mumbai and hyderabad, india.

while you wait for microsoft to update their database, you have a workaround. if you are using conditional access policies that block based on location, you can create named locations based on these ip ranges. in the entra id admin center, go to security > conditional access > named locations. create a new ip based location for each range and manually set the country to india. then, in your conditional access policy, you can use these trusted named locations instead of the built in country condition.

this kind of geo ip discrepancy is a common challenge. all major cloud providers struggle to keep their ip databases perfectly in sync with the rapidly changing internet.

immediately open an azure support ticket to report the incorrect geo ip data. as a temporary fix, create named locations in entra id for these ip ranges and adjust your conditional access policies accordingly.

regards,

Alex

and "yes" if you would follow me at Q&A - personaly thx. P.S. If my answer help to you, please Accept my answer

https://ctrlaltdel.blog/
Ravi Varma Mudduluru 12,625 Reputation points Microsoft External Staff Moderator

2025-10-06T16:10:24.15+00:00

Hello @Jay Hickman,

Could you please check the private message and share me the requested details

Your answer

Alex Burlachenko 25,290 Reputation points MVP Volunteer Moderator

2025-10-01T09:43:12.58+00:00

hi Jay ,

the ip addresses are physically in india, but azure's security logs are showing them as taiwan and texas. this is a serious issue because it can block legitimate users.

the problem is that azure uses its own internal geo ip database for services like conditional access and threat detection, and that database is out of date for these specific ip ranges owned by oracle.

most important step is to report this directly to microsoft so they can update their geo ip data. you need to open a support ticket in the azure portal. for the service type, choose 'azure active directory' or 'microsoft entra id'. in the ticket, clearly explain that the ip ranges 192.188.171.0/24 and 206.126.100.0/24 are being incorrectly geolocated. provide the evidence from ip2location and ipinfo.io showing the correct location is mumbai and hyderabad, india.

while you wait for microsoft to update their database, you have a workaround. if you are using conditional access policies that block based on location, you can create named locations based on these ip ranges. in the entra id admin center, go to security > conditional access > named locations. create a new ip based location for each range and manually set the country to india. then, in your conditional access policy, you can use these trusted named locations instead of the built in country condition.

this kind of geo ip discrepancy is a common challenge. all major cloud providers struggle to keep their ip databases perfectly in sync with the rapidly changing internet.

immediately open an azure support ticket to report the incorrect geo ip data. as a temporary fix, create named locations in entra id for these ip ranges and adjust your conditional access policies accordingly.

regards,

Alex

and "yes" if you would follow me at Q&A - personaly thx. P.S. If my answer help to you, please Accept my answer

https://ctrlaltdel.blog/
Ravi Varma Mudduluru 12,625 Reputation points Microsoft External Staff Moderator

2025-10-06T16:10:24.15+00:00

Hello @Jay Hickman,

Could you please check the private message and share me the requested details