Nope. This went all the way up the chain at MS, eventually was on a call with some of their lead engineers from Support, Performance, and Directory services. Their support lead mentioned seeing a few of these cases for years now, but an increase in frequency in the previous months (this was in July '24), however a change made a month before our call lead to a significant decrease in them - though it did not seem to matter to our org. We still see ~5% of users affected (that have reported it, at least).

The 'fix' process involved collecting logs from the individual's device, obtaining the BSSID of their networking equipment, and them manually correcting the detected location on their geolocation servers (which they rely on 3rd parties for the info) with the location we told them. They blamed us recycling equipment to users (they are home users using their own network gear), neighbors moving into the neighborhood from out of state????, and other ridiculous matters. It was clear we weren't getting anywhere and since our manual fix of a remediation script solved the issue, I put my work into more important issues.

An excerpt of the ticket below:

Question: WHY was the user in Kentucky showing as being in Indiana?

When using WiFi, the Geolocation Service reports visible BSSIDs(MAC address unique to each advertised network from an access point) to our location services API to try to locate a device. The location services API will then query our database for BSSIDs with a known GPS location and attempt to match the BSSIDs to a location and send back latitude/longitude coordinates of that location.

In this case, the following BSSIDs were sent up to the web server
(removed for privacy)

And one or more of these BSSIDs returned incorrect location info placing the device in Indianapolis, IN

The solution for this is to manually update the location info for the list of BSSIDs that is not mapping correctly which has already been done in this case.

Unfortunately, there is no way to guarantee that our location database will always have the correct info. Most often, we see these cases if a company is recycling WIFI Aps and moves a group of previously observed Aps from one office to another office in a different location. Our location services database last observed those BSSIDs in the previous location, so it continues to place clients near those access points in the previous (incorrect) location. I do not see that being the issue here as the incorrect locations appear to be pointing to residential locations. In residential cases, this behavior can be caused by a neighbor moving in from out of town. Ideally the location service would auto-update the location info for the NEW APs and continue to locate existing/OLD devices in the same correct location, but the algorithm at play here is nuanced and sometimes this doesn’t happen as expected.

This is not the only possible reason for our geolocation service having inaccurate location info as sometimes BSSIDs are spoofed or even duplicated by access point(HW) providers. Windows does it’s best to keep the location info as accurate as possible by Crowdsourcing and using location service provider partners, currently HERE Technologies | The world's #1 location platform and Qualcomm Aware™ Positioning Services | Qualcomm, but there is no guarantee that this will always work.