Microsoft Authenticator is a trusted tool for securing accounts with two‑factor authentication, but sometimes it can display a login attempt from the wrong city or even the wrong country.
This issue often raises concern among users who fear their accounts may be compromised, yet in most cases the problem stems from how networks and devices report location data rather than from actual security breaches.
Understanding the common causes — such as VPN routing, disabled location services, or outdated app settings — and applying simple fixes can help restore accurate location reporting and ensure smoother, more reliable authentication.
Reasons for Incorrect Login Location
Here are the reasons for the incorrect login location.
• Network Routing – Using office, school, or corporate networks (including VPNs) often routes traffic through servers in another city or country.
• VPNs or Proxies – These services mask your real IP address, making the location appear different.
• Disabled Location Services – If your phone’s location services are off, the app relies only on IP‑based location, which is less accurate.
• Incorrect Date & Time Settings – Wrong system time or time zone can cause mismatches in location reporting.
• Outdated Authenticator App – Older versions may not sync location data correctly.
• Battery Optimization Restrictions – Aggressive battery saving settings can interfere with background sync and location accuracy.
How To Fix Incorrect Login Location
Follow this step by step guide when you get incorrect login location.
1. Check Your Network
When Microsoft Authenticator is showing a wrong location, check your internet connection. You can switch between Wi‑Fi and mobile data to see if the location updates correctly.
If your connection gets interrupted, check how to fix that.
If you are using any VPN or proxy services, then disable it and check if that works. If you are not using any VPN service then you can use one and see if that helps.
2. Verify Device Settings
The next thing you can do is verify the device settings.
Ensure Location Services are enabled on your phone.
- To do that, swipe down from the top of the screen and tap the Settings icon, or open the Settings app from your app drawer.
- Scroll down and tap Location.
- Toggle the Location switch to ON.
- If prompted, allow system services to access location.
- Next confirm Date & Time is set to automatic and matches your region.
- To do that open Settings.
- Go to System or General management or Additional Settings.
- Tap Date & time.
- Turn ON:
Set Time automatically and Set Time Zone automatically or similar options.
- If you don’t see “System,” try searching Date & time in the Settings search bar.
3. Update the Authenticator App
The next thing you can do is update the Authenticator app.
- To do that open Google Play. Then search for Authenticator app.
- Look for any available updates. In case there is the Update button instead of Open download and install the updates.
- Once done, open the authenticator app and check.
- You can also Open Authenticator app ten click on the three dots menu to open Settings.
- Then select App updates and make sure updates are turned on.
- Disable battery optimization for Authenticator to improve sync accuracy.
4. Disable office, school, or corporate network
If you’re using an office, school, or corporate network including cloud-based VPNs, incorrect login locations are common because these networks route traffic through centralized servers that may be in another city or country.
To fix this, disconnect from office Wi-Fi or the corporate VPN and complete the login using a personal network such as mobile data or a personal hotspot, then reconnect to the work network afterward.
If possible, use a personal device instead of a managed work device, and confirm “This was me” on any security alerts to reduce future warnings.
For a long-term solution, you can also ask your IT team whether local network exit points are available.
Wrapping Up
So, there you have it!Incorrect login locations in Microsoft Authenticator are usually caused by network routing, VPNs, or device settings rather than actual security breaches.
By checking your network, enabling location services, updating the app, and avoiding corporate VPNs during login, you can ensure more accurate location reporting and reduce unnecessary alerts. For more such updates ask us in the commnets section provided below.
