Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

Teams emergency location sticky

%3CLINGO-SUB%20id%3D%22lingo-sub-2270640%22%20slang%3D%22en-US%22%3ETeams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2270640%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20experienced%20the%20Teams%20client%20dynamic%20emergency%20location%20sticking%20and%20not%20updating%20properly%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20currently%20have%20an%20office%20location%20configured%20according%20to%20Microsoft%20documentation.%26nbsp%3B%20Civic%20Address%20verified%2C%20places%20configured%20under%20civic%20address%20(i.e.%20bldg%201%2C%202%2C%20etc.)%2C%20public%20IPs%20configured%2C%20LIS%20DB%20configured%20based%20on%20BSSID%2C%20BSSIDs%20attached%20to%20places%20under%20civic%20address.%26nbsp%3B%20We've%20found%20that%20at%20first%20connect%20the%20Windows%2010%20Teams%20clients%20(similar%20for%20mobile%20clients)%2C%20pick%20up%20the%20dynamic%20emergency%20location%20correctly.%26nbsp%3B%20Upon%20moving%20the%20Windows%20client%20to%20another%20emergency%20location%20(i.e.%20moving%20from%20bldg%201%20to%202)%2C%20the%20client%20never%20updates%20the%20emergency%20location.%26nbsp%3B%20The%20only%20reliable%20way%20of%20updating%20the%20client%20emergency%20location%2C%20after%20it%20has%20been%20moved%2C%20is%20to%20log%20out%20of%20Teams%20and%20log%20back%20in.%26nbsp%3B%20In%20several%20testing%20situations%20the%20client%20does%20not%20update%20automatically%20in%20over%2024%20hours.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20an%20open%20case%20with%20Microsoft%20which%20has%20been%20closed%20and%20re-opened%20twice%20since%20originally%20reported.%26nbsp%3B%20I%20was%20notified%20last%20month%20that%20the%20fix%20was%20included%20in%20a%20Teams%20patch%20applied%20to%20version%201.4.00.7174%20which%20has%20come%20and%20gone%20and%20been%20tested.%26nbsp%3B%20The%20Teams%20client%20still%20won't%20update%20automatically.%26nbsp%3B%20The%20case%20is%20open%20again%20and%20I'm%20awaiting%20feedback%20from%20Microsoft%20after%20providing%20additional%20logs%20from%20our%20testing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20short%20the%20emergency%20locations%20work%20just%20fine%2C%20it%20is%20the%20automatic%20change%20of%20emergency%20location%20which%20is%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20performed%20an%20additional%20test%20recently%20between%20civic%20addresses.%26nbsp%3B%20I%20connected%20to%20a%20network%20at%20civic%20address%201%20and%20then%20moved%20the%20client%20to%20civic%20address%202.%26nbsp%3B%20The%20client%20kept%20the%20emergency%20location%20of%20civic%20address%201.%26nbsp%3B%20Only%20after%20reboot%20of%20the%20client%20or%20restart%20of%20Teams%20client%20did%20the%20emergency%20location%20update%20to%20the%20proper%20setting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELastly%20I%20tested%20a%20fresh%20Teams%20client%20on%20a%20non-company%20computer%20to%20potentially%20rule%20out%20security%20configurations%20of%20the%20client.%26nbsp%3B%20The%20same%20behavior%20existed.%26nbsp%3B%20While%20not%20conclusive%20I%20suspect%20this%20points%20back%20to%20a%20Teams%20client%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20experienced%20this%20and%20has%20been%20able%20to%20narrow%20this%20issue%20down%20to%20a%20bug%20or%203rd%20party%20cause%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2270640%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2336451%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2336451%22%20slang%3D%22en-US%22%3EYes%2C%20we%20do%20have%20the%20same%20issue.%20Log%20out%20login%20back%20will%20show%20the%20right%20location.%20It%20seems%20to%20be%20a%20bug%20and%20MS%20is%20working%20on%20it.%20So%20as%20of%20now%2C%20it%20works%20when%20switching%20from%20one%20network%20to%20another%20but%20not%20between%20the%20access%20points.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2371661%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2371661%22%20slang%3D%22en-US%22%3EI%20was%20told%20by%20Microsoft%20that%20a%20fix%20had%20been%20pushed%20to%20customers%20but%20have%20not%20yet%20been%20told%20which%20version%20would%20contain%20the%20fix.%20On%20Friday%20we%20received%20an%20update%20to%20version%201.4.00.11161.%20I've%20since%20tested%20it%20and%20the%20patch%20either%20wasn't%20in%20this%20version%20update%20or%20did%20not%20fix%20the%20issue.%20I've%20opened%20the%20case%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377028%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377028%22%20slang%3D%22en-US%22%3EI've%20been%20told%20by%20Microsoft%20the%20fix%20will%20be%20included%20in%20slimcore%20version%202021.10.%20I've%20found%20reference%20to%20the%20current%20slimcore%20version%20in%20the%20logs%20that%20download%20when%20pressing%20ctrl%2C%20alt%2C%20shift%201.%20Log%20file%20named%20%22MSTeams%20Diagnostics%20Log%20%3CDATE%3E_%3CTIME%3E.txt%22%3C%2FTIME%3E%3C%2FDATE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2446324%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2446324%22%20slang%3D%22en-US%22%3EThe%20release%20date%20of%20this%20patch%20is%20still%20unknown.%20Do%20you%20know%20any%20information%20on%20the%20release%20of%20this%20patch%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2452683%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2452683%22%20slang%3D%22en-US%22%3EWe%20have%20tested%20this%20in%20Slim%20Core%20Verison%3A%202021.14.41%20and%20yet%20no%20luck.%20The%20location%20didn't%20change%20automatically%20when%20moving%20from%20one%20access%20point%20to%20another.%20Only%20after%20a%20restart%20of%20Teams%20client%2C%20the%20emergency%20location%20appeared.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2453131%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2453131%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1038246%22%20target%3D%22_blank%22%3E%40radz%3C%2FA%3E%26nbsp%3BThank%20you%20for%20this%20update.%26nbsp%3B%20I%20still%20have%20an%20earlier%20version%20of%20slimcore%20so%20haven't%20been%20able%20to%20test%20yet%20again.%26nbsp%3B%20I'll%20let%20Microsoft%20know%20this%20news%20and%20work%20on%20getting%20another%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2454470%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2454470%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1024820%22%20target%3D%22_blank%22%3E%40dwilliamsucb%3C%2FA%3E%20I%20got%20an%20update%20that%20the%20actual%20fix%20is%20expected%20to%20release%20in%20Slimcore%20Version%202021.22%20%3A(%3C%2Fimg%3E%20and%20no%20ETA%20when%20it%20will%20be%20released.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2454542%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2454542%22%20slang%3D%22en-US%22%3EThanks%20for%20this%20update.%20Unfortunate%20that%20there%20is%20no%20ETA.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2593050%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2593050%22%20slang%3D%22en-US%22%3EI%20just%20received%20a%20new%20Teams%20update%20a%20few%20days%20back.%20Verizon%201.4.00.19572%20and%20along%20with%20the%20update%20received%20an%20update%20to%20slimcore%20version.%20My%20slimcore%20version%20is%20now%202021.14.41%20which%20appears%20to%20be%20a%20later%20version%20than%20the%20slimcore%20version%202021.10%20which%20according%20to%20Microsoft%20included%20the%20bugfix.%20Unfortunately%20the%20bug%20is%20not%20fixed%20in%20the%20updates%20I%20received.%20In%20fact%20it%20appears%20the%20problem%20is%20worse.%3CBR%20%2F%3E%3CBR%20%2F%3EPrior%20to%20this%20update%20my%20client%20would%20show%20the%20correct%20emergency%20location%20if%20I%20logged%20out%20of%20Teams%20and%20logged%20in%20again.%20Even%20though%20it%20is%20not%20feasible%20for%20users%20it%20was%20a%20consistent%20result.%20Now%20after%20the%20change%20it%20appears%20that%20the%20old%20location%20is%20somehow%20cached.%20Today%20I%20logged%20out%20of%20the%20Teams%20client%20and%20logged%20back%20in%20which%20resulted%20in%20the%20Old%20location%20being%20shown%20as%20my%20emergency%20location%20instead%20of%20the%20location%20I%20was%20actually%20in.%20I%20repeated%20this%20several%20times%20and%20the%20new%20location%20would%20not%20appear.%3CBR%20%2F%3E%3CBR%20%2F%3EI'll%20continue%20testing%20but%20am%20a%20bit%20concerned%20that%20Microsoft%20doesn't%20understand%20the%20problem%20they%20are%20trying%20to%20solve.%20Unfortunately%20also%20there%20is%20literally%20no%20information%20being%20shared%20with%20me%20to%20indicate%20otherwise.%20Ten%20months%20without%20a%20fix%20seems%20a%20bit%20excessive%20when%20talking%20about%20a%20feature%20that%20is%20literally%20for%20people's%20safety.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2593083%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2593083%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1038246%22%20target%3D%22_blank%22%3E%40radz%3C%2FA%3E%20It%20took%20some%20time%20for%20us%20to%20receive%20the%20version%20that%20you%20tested%20in%20June.%20I%20just%20received%20the%20version%20update%20that%20included%20slimcore%202021.14.41%20and%20can%20confirm%20your%20results%20that%20the%20bug%20is%20not%20fixed.%20Since%20you%20seem%20to%20be%20receiving%20the%20updates%20a%20bit%20quicker%20than%20me%2C%20would%20you%20mind%20posting%20your%20results%20after%20you%20receive%20the%202021.22%20update%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2598087%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2598087%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1024820%22%20target%3D%22_blank%22%3E%40dwilliamsucb%3C%2FA%3E%20The%20fix%20is%20released%20in%20Slim%20core%20version%202021.22.%20however%2C%20it%20is%20taking%208-10%20min%20for%20the%20location%20to%20update%20once%20the%20user%20moves%20from%20one%20WAP%20to%20another.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2598997%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2598997%22%20slang%3D%22en-US%22%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1038246%22%20target%3D%22_blank%22%3E%40radz%3C%2FA%3E.%208-10%20minutes%20is%20not%20ideal%20but%20it%20is%20better%20than%20where%20we%20are%20now.%20I%20suspect%20we'll%20receive%20this%20update%20in%20the%20upcoming%20weeks%20and%20I'll%20test%20as%20well.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2656058%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2656058%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1038246%22%20target%3D%22_blank%22%3E%40radz%3C%2FA%3E%20Interesting%20thing%20happened%20around%20two%20weeks%20ago%20(approximately%20Aug4).%20My%20client%20is%20now%20updating%20like%20yours%20after%208-10%20minutes.%20I%20have%20not%20received%20the%20same%20Teams%20update%20as%20you%20yet%20though.%20I%20still%20have%20the%20previous%20slimcore%20that%20you%20had%202021.14.41%20update.%20I%20received%20this%20update%20on%20July%2023.%20Directly%20after%20this%20update%20the%20problem%20seemed%20worse.%20I%20had%20a%20cached%20location%20showing%20up%20even%20after%20logging%20off%20and%20logging%20back%20on.%20Then%20around%20August%204%20the%20client%20started%20updating%20like%20you%20described%20after%208-10%20minutes.%20It%20seems%20fairly%20consistent%20at%20this%20point.%20With%20that%20said%2C%20the%20only%20conclusions%20I%20can%20come%20to%20are%201)%20Microsoft%20has%20done%20something%20on%20the%20backend%20that%20explains%20the%20behavior%20we%20are%20seeing%20or%202)%20it%20took%20some%20time%20and%20multiple%20reboots%20for%20slimcore%202021.14.41%20to%20change%20what%20we%20are%20seeing.%20The%20second%20point%20seems%20unlikely.%20I%20still%20have%20the%20ticket%20open%20and%20waiting%20for%20a%20response%20from%20the%20product%20support%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2858365%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2858365%22%20slang%3D%22en-US%22%3EI%20am%20working%20with%20a%20customer%20who%20is%20having%20the%20same%20issue.%20We%20have%20tried%20roaming%20between%20access%20points%20and%20even%20switching%20from%20WiFi%20to%20Wired%20with%20no%20change%20in%20the%20location%20information%20for%20what%20seems%20to%20be%20at%20least%205-10%20minutes.%20My%20understanding%20is%20that%20when%20the%20Teams%20client%20detects%20the%20network%20change%20it%20will%20update%20settings%20such%20as%20E911%20location%20or%20after%20an%20undetermined%20amount%20of%20time.%20It%20would%20be%20nice%20to%20know%20what%20the%20expectations%20are%20in%20the%20client%20for%20the%20refresh%20rate%20of%20this.%20It%20would%20be%20easier%20to%20explain%20to%20the%20customer%20if%20I%20had%20this%20information.%20I'm%20tempted%20to%20open%20a%20ticket%20with%20Microsoft%20but%20I%20don't%20feel%20like%20going%20through%20the%20Tier%201%20mumbo%20before%20getting%20someone%20to%20answer%20my%20questions.%20Anyone%20else%20have%20anything%20to%20share%20on%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2865477%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20emergency%20location%20sticky%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2865477%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1141729%22%20target%3D%22_blank%22%3E%40JBoslooper_Magenium%3C%2FA%3E%26nbsp%3Bso%20I%20have%20received%20some%20feedback%20from%20Microsoft%20with%20an%20explanation%20of%20how%20this%20works.%26nbsp%3B%20The%20main%20issue%20where%20the%20emergency%20location%20was%20stuck%20or%20not%20working%20appears%20to%20be%20resolved.%20I%20believe%20it%20was%20a%20backend%20fix%20instead%20of%20client%20update.%26nbsp%3B%20Anyway%20around%20August%20the%20client%20started%20updating%20consistently%20at%20first%20a%2010%20minute%20window%20and%20now%20consistently%20at%205%20minutes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20described%20to%20me%20that%20a%20network%20change%20would%20start%20a%20timer%20on%20the%20client.%26nbsp%3B%20At%205%20minutes%20the%20client%20will%20send%20a%20request%20to%20Teams%20backend%20to%20check%20for%20it's%20emergency%20location.%26nbsp%3B%20If%20the%20Emergency%20Location%20is%20different%20it%20will%20update%20the%20client.%26nbsp%3B%20This%20is%20what%20I'm%20experiencing%20at%20this%20point%20in%20time.%26nbsp%3B%20If%20I%20change%20from%20wired%20to%20wireless%2C%205%20minutes%20after%20this%20change%20the%20location%20updates.%26nbsp%3B%20Same%20goes%20with%20other%20network%20changes%20(i.e.%20BSSID%20change%2C%20leave%20one%20building%20and%20reconnect%20in%20another%2C%20disconnect%20Wi-Fi%20adapter%20and%20reconnect).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETwo%20additional%20points%20were%20made%20by%20the%20Microsoft%20contact.%26nbsp%3B%20%26nbsp%3BFirst%2C%20the%20location%20is%20%22hashed%20and%20cached%20for%204%20hours%20(or%20until%20there%20is%20a%20network%20change)%22.%26nbsp%3B%20Second%2C%20if%20there%20was%20no%20event%20(Teams%20startup%20or%20network%20change)%20for%204%20hours%2C%20the%20Teams%20client%20will%20send%20a%20new%20request.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

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?

14 Replies
Yes, we do have the same issue. Log out login back will show the right location. It seems to be a bug and MS is working on it. So as of now, it works when switching from one network to another but not between the access points.
I was told by Microsoft that a fix had been pushed to customers but have not yet been told which version would contain the fix. On Friday we received an update to version 1.4.00.11161. I've since tested it and the patch either wasn't in this version update or did not fix the issue. I've opened the case again.
I've been told by Microsoft the fix will be included in slimcore version 2021.10. I've found reference to the current slimcore version in the logs that download when pressing ctrl, alt, shift 1. Log file named "MSTeams Diagnostics Log <date>_<time>.txt"
The release date of this patch is still unknown. Do you know any information on the release of this patch?
We have tested this in Slim Core Verison: 2021.14.41 and yet no luck. The location didn't change automatically when moving from one access point to another. Only after a restart of Teams client, the emergency location appeared.

@radz Thank you for this update.  I still have an earlier version of slimcore so haven't been able to test yet again.  I'll let Microsoft know this news and work on getting another update.

@dwilliamsucb I got an update that the actual fix is expected to release in Slimcore Version 2021.22 :( and no ETA when it will be released.
Thanks for this update. Unfortunate that there is no ETA.
@radz It took some time for us to receive the version that you tested in June. I just received the version update that included slimcore 2021.14.41 and can confirm your results that the bug is not fixed. Since you seem to be receiving the updates a bit quicker than me, would you mind posting your results after you receive the 2021.22 update?
@dwilliamsucb The fix is released in Slim core version 2021.22. however, it is taking 8-10 min for the location to update once the user moves from one WAP to another.
Thanks @radz. 8-10 minutes is not ideal but it is better than where we are now. I suspect we'll receive this update in the upcoming weeks and I'll test as well.

@radzInteresting thing happened around two weeks ago (approximately Aug4). My client is now updating like yours after 8-10 minutes.  I have the previous slimcore that you had 2021.14.41 update. I received this update on July 23. Directly after this update the problem seemed worse. I had a cached location showing up even after logging off and logging back on. Then around August 4 the client started updating like you described after 8-10 minutes. It seems fairly consistent at this point. With that said, the only conclusions I can come to are 1) Microsoft has done something on the backend that explains the behavior we are seeing or 2) it took some time and multiple reboots for slimcore 2021.14.41 to change what we are seeing. The second point seems unlikely. I still have the ticket open and waiting for a response from the product support team.

I am working with a customer who is having the same issue. We have tried roaming between access points and even switching from WiFi to Wired with no change in the location information for what seems to be at least 5-10 minutes. My understanding is that when the Teams client detects the network change it will update settings such as E911 location or after an undetermined amount of time. It would be nice to know what the expectations are in the client for the refresh rate of this. It would be easier to explain to the customer if I had this information. I'm tempted to open a ticket with Microsoft but I don't feel like going through the Tier 1 mumbo before getting someone to answer my questions. Anyone else have anything to share on this?

@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.