Apr 13 2021 10:39 AM
Apr 13 2021 10:39 AM
Has anyone experienced the Teams client dynamic emergency location sticking and not updating properly?
We currently have an office location configured according to Microsoft documentation. Civic Address verified, places configured under civic address (i.e. bldg 1, 2, etc.), public IPs configured, LIS DB configured based on BSSID, BSSIDs attached to places under civic address. We've found that at first connect the Windows 10 Teams clients (similar for mobile clients), pick up the dynamic emergency location correctly. Upon moving the Windows client to another emergency location (i.e. moving from bldg 1 to 2), the client never updates the emergency location. The only reliable way of updating the client emergency location, after it has been moved, is to log out of Teams and log back in. In several testing situations the client does not update automatically in over 24 hours.
I have an open case with Microsoft which has been closed and re-opened twice since originally reported. I was notified last month that the fix was included in a Teams patch applied to version 1.4.00.7174 which has come and gone and been tested. The Teams client still won't update automatically. The case is open again and I'm awaiting feedback from Microsoft after providing additional logs from our testing.
In short the emergency locations work just fine, it is the automatic change of emergency location which is not.
I performed an additional test recently between civic addresses. I connected to a network at civic address 1 and then moved the client to civic address 2. The client kept the emergency location of civic address 1. Only after reboot of the client or restart of Teams client did the emergency location update to the proper setting.
Lastly I tested a fresh Teams client on a non-company computer to potentially rule out security configurations of the client. The same behavior existed. While not conclusive I suspect this points back to a Teams client issue.
Has anyone else experienced this and has been able to narrow this issue down to a bug or 3rd party cause?
May 07 2021 11:25 AM