Forum Discussion

dwilliamsucb's avatar
dwilliamsucb
Brass Contributor
Apr 13, 2021

Teams emergency location sticky

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.  Civi...
  • dwilliamsucb's avatar
    dwilliamsucb
    Oct 20, 2021

    JBoslooper_Magenium so I have received some feedback from Microsoft with an explanation of how this works.  The main issue where the emergency location was stuck or not working appears to be resolved. I believe it was a backend fix instead of client update.  Anyway around August the client started updating consistently at first a 10 minute window and now consistently at 5 minutes. 

     

    Microsoft described to me that a network change would start a timer on the client.  At 5 minutes the client will send a request to Teams backend to check for its emergency location.  If the Emergency Location is different it will update the client.  This is what I'm experiencing at this point in time.  If I change from wired to wireless, 5 minutes after this change the location updates.  Same goes with other network changes (i.e. BSSID change, leave one building and reconnect in another, disconnect Wi-Fi adapter and reconnect).

     

    Two additional points were made by the Microsoft contact.   First, the location is "hashed and cached for 4 hours (or until there is a network change)".  Second, if there was no event (Teams startup or network change) for 4 hours, the Teams client will send a new request.

Resources