Teams Phone device refuse login with 1449/1.0.94.2021033002 firmware and ADFS

%3CLINGO-SUB%20id%3D%22lingo-sub-2270432%22%20slang%3D%22en-US%22%3ETeams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2270432%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anybody%20been%20using%20ADFS%20with%20Teams%20noticed%20an%20issue%20with%20the%20last%20two%20firmware%20updates%2C%20when%20performing%20logins%20off-network%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20customer%20running%20Yealink%20MP56%20phones%20and%20the%20latest%20firmware%20122.15.0.36%20running%20Teams%20App%201449%2F1.0.94.2021022403%20or%20%3CSPAN%3E%3CSPAN%3E1449%2F1.0.94.2021033002%3C%2FSPAN%3E%3C%2FSPAN%3E%20can%20no%20longer%20login%20using%20either%20the%20device%20login%20code%20or%20typing%20user%2Fpass.%20The%20login%20seems%20to%20get%20stuck%20in%20a%20loop%20between%20device%20registration%20and%20preparing%20the%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suspect%20this%20is%20partially%20to%20do%20with%20the%20ADFS%20configuration%20not%20using%20UPN%20for%20authentication%2C%20but%20this%20wasn't%20an%20issue%20prior%20to%201449%2F1.0.94.2021022403.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2270432%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271000%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271000%22%20slang%3D%22en-US%22%3EI'm%20having%20the%20same%20issue%20with%20a%20Yealink%20T55A.%20Once%20the%20update%20was%20completed%2C%20the%20phone%20will%20not%20receive%20a%20device%20code%20for%20provisioning.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271298%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271298%22%20slang%3D%22en-US%22%3ESame%20issue%20here.%20Yealink%20VP59.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272260%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272260%22%20slang%3D%22en-US%22%3ESame%20issue%20here.%20Yealink%20MP54%20and%20AudiocodesC450HD.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272938%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272938%22%20slang%3D%22en-US%22%3EAre%20you%20able%20to%20open%20a%20support%20ticket%20with%20Microsoft%3F%20Can%20you%20send%20me%20the%20ticket%20number%20as%20a%20message%20you've%20opened%20it%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273264%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273264%22%20slang%3D%22en-US%22%3EDon't%20know%20if%20this%20helps%20anyone%2C%20but%20I%20opened%20tickets%20with%20Microsoft%20Teams%20support%2C%20Azure%20support%2C%20and%20Yealink.%20So%20far%2C%20everyone%20is%20saying%20it's%20someone%20else's%20issue.%20This%20has%20been%20going%20on%20for%20about%209%20days.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273332%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273332%22%20slang%3D%22en-US%22%3EIt%20would%20be%20helpful%20if%20you%20can%20send%20me%20a%20message%20with%20the%20Microsoft%20Teams%20ticket%20details.%20I%20am%20a%20PM%20in%20the%20team%2C%20and%20would%20like%20to%20see%20this%20ticket.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274577%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274577%22%20slang%3D%22en-US%22%3EDM%20sent%20with%20ticket%20number.%20I%20did%20speak%20with%20a%20contact%20at%20Yealink%20yesterday%20and%20they%20suggested%20a%20possible%20issue%20with%20device%20count%20limits%2C%20but%20I%20realized%20this%20morning%20I'm%20trying%20to%20login%20to%20the%20same%20device%20I%20already%20have%20registered%20under%20the%20tenant%20so%20it%20shouldn't%20(in%20theory)%20be%20that.%3CBR%20%2F%3E%3CBR%20%2F%3ERolling%20back%20to%20an%20earlier%20firmware%20and%20Teams%20app%20from%20last%20year%20seems%20to%20resolve%20the%20issue.%20Upgrading%20again%20breaks%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2274914%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274914%22%20slang%3D%22en-US%22%3EI%20sent%20the%20ticket%20information%20in%20a%20DM.%20The%20ticket%20with%20Azure%20was%20closed%20because%20it%20was%20a%20'duplicate'%20ticket.%20Yealink%20also%20said%20it%20may%20be%20a%20problem%20with%20too%20many%20devices%20for%20the%20user%2C%20but%20only%20one%20is%20assigned%20and%20I%20have%20set%20my%20company%20limit%20to%2020%2C%20so%20that%20should%20not%20be%20an%20issue.%20I%20am%20going%20to%20try%20to%20downgrade%20it%20today%2C%20similar%20to%20what%20jangliss%20did%2C%20to%20see%20if%20my%20problem%20is%20fixed.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275011%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275011%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1025164%22%20target%3D%22_blank%22%3E%40Jacob_B%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20assuming%20you%20are%20using%20ADFS%3F%20Did%20Microsoft%20gather%20the%20ADFS%20logs%20from%20your%20failed%20attempts%3F%20I'm%20working%20on%20gathering%20those%20myself.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20gone%20back%20and%20done%20additional%20testing%20and%20it%20doesn't%20appear%20to%20be%20limited%20to%20a%20particular%20vendor.%20I've%20tested%20with%20Poly%20CCX%20400%2C%20CCX%20500%2C%20and%20CCX%20700%2C%20AudioCodes%20HD450%2C%20Yealink%20T56A%2C%20T58A%2C%20and%20MP56.%26nbsp%3B%20It's%20after%20deploying%20the%20February%20update%20which%20appears%20to%20be%20bundled%20with%20most%20of%20the%20latest%20firmwares%20from%20the%20vendors%2C%20things%20break.%26nbsp%3B%20Going%20to%20roll%20back%20a%20few%20firmware%20and%20do%20additional%20testing%20to%20verify.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275201%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275201%22%20slang%3D%22en-US%22%3EIf%20possible%2C%20could%20you%20send%20this%20ticket%20information%20to%20me%20as%20well%3F%20I%20am%20deploying%20an%20MP56%20with%20the%20same%20firmware%2FTeams%20version%2C%20and%20the%20same%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%2C%20to%20confirm%2C%20are%20you%20seeing%20the%20%22Oops%2C%20you%20can't%20access%20this%20right%20now.%22%20error%20when%20attempting%20to%20login%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275294%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275294%22%20slang%3D%22en-US%22%3EDM%20sent.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2275298%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2275298%22%20slang%3D%22en-US%22%3EI%20was%20not%20able%20to%20find%20any%20failed%20logins%20in%20any%20of%20the%20Microsoft%20cloud%20services%2C%20it's%20like%20the%20device%20is%20not%20connecting%20or%20seeing%20Microsoft%20at%20all.%20I%20checked%20my%20firewall%20to%20verify%20that%20no%20ports%20needed%20to%20access%20and%20run%20Teams%20are%20being%20blocked.%20Downgrading%20did%20not%20help%2C%20so%20no%20luck%20there.%20I%20sent%20a%20video%20of%20the%20issue%20to%20Microsoft%20today%20for%20them%20to%20view%20the%20problem%20that%20I%20am%20running%20into.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276245%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276245%22%20slang%3D%22en-US%22%3EFYI%20-%20the%20phone%20is%20not%20saving%20the%20time%20settings%20when%20it's%20rebooted%20which%20may%20be%20part%20of%20the%20problem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2276340%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2276340%22%20slang%3D%22en-US%22%3EI%20originally%20opened%20this%20thinking%20it%20might%20have%20been%20ADFS%20related%2C%20but%20also%20seeing%20this%20across%20tenants%20not%20using%20ADFS.%20This%20seems%20like%20a%20big%20issue!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2277964%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277964%22%20slang%3D%22en-US%22%3EWe%20are%20having%20the%20same%20issue%20with%20Poly%20C60%20conference%20room%20phones%20once%20updated%20to%20firmware%207.0.2.1071.%20This%20firmware%20comes%20with%20Teams%20App%201449%2F1.0.94.2021022403%20and%20we%20get%20the%20same%20login%20loop.%20I've%20tried%20updating%20to%20Teams%20App%201449%2F1.0.94.2021033002%20but%20problem%20persists.%20I%20have%20tried%20both%20the%20original%20web%20login%20method%20as%20well%20as%20the%20new%20remote%20provision%2Flogin%20method%20and%20both%20result%20in%20the%20same%20login%20loop.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20I%20roll%20the%20firmware%20back%20to%205.9.5.3153%20and%20Teams%20App%201449%2F1.0.94.2020121001%2C%20I%20can%20web%20login%20the%20phone%20again%20without%20issue.%20I%20can%20then%20fully%20upgrade%20the%20phone's%20firmware%20and%20Teams%20App%20version%20to%20latest%20and%20the%20phone%20will%20stay%20logged%20in.%20However%2C%20if%20I%20log%20it%20out%2C%20I%20can't%20log%20it%20back%20in%20as%20it%20gets%20stuck%20in%20the%20same%20loop.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2279936%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2279936%22%20slang%3D%22en-US%22%3EThe%20biggest%20issue%20of%20all%20is%20that%20there's%20no%20way%20to%20stop%20these%20phones%20from%20automatically%20getting%20the%20update%20eventually!%20Deferring%20for%2090%20days%20is%20the%20best%20we%20can%20do%20and%20that's%20a%20very%20manual%20process%20to%20have%20to%20set%20each%20and%20every%20phone%20as%20they%20come%20in.%20Imagine%20how%20rough%20it's%20going%20to%20be%20when%20you%20have%20hundreds%20of%20phones!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280275%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280275%22%20slang%3D%22en-US%22%3EHas%20anyone%20found%20a%20real%20solution%20to%20this%20issue%3F%20I%20am%20about%20to%20start%20rolling%20back%20firmware%20but%20was%20hoping%20someone%20has%20an%20answer.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2280375%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280375%22%20slang%3D%22en-US%22%3EI've%20not%20heard%20anything%20back%20on%20our%20open%20Microsoft%20support%20ticket%20but%20the%20more%20people%20that%20open%20tickets%2C%20the%20more%20visibility%20this%20is%20going%20to%20get%20for%20quicker%20resolution.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2281576%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2281576%22%20slang%3D%22en-US%22%3EI'd%20definitely%20agree.%20Open%20tickets%20if%20you%20haven't%20already.%20I've%20not%20heard%20anything%20from%20support%20on%20my%20ticket%20other%20than%20%22sorry%20for%20the%20delay%2C%20we're%20waiting%20to%20hear%20back%20from%20engineering%22.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2301403%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2301403%22%20slang%3D%22en-US%22%3EHi%20All%2C%3CBR%20%2F%3EWe%20are%20experiencing%20the%20exact%20same%20issue%20described%20here%20using%20Yealink%20T55A%20IP%20phones%20off%20network.%20We%20have%20opened%20a%20case%20with%20our%20Teams%20telecom%20provider.%20Will%20update%20here%20if%20we%20receive%20any%20news.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2311959%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2311959%22%20slang%3D%22en-US%22%3EThis%20ended%20up%20being%20an%20issue%20with%20a%20DNS%20server%20for%20my%20phone%2C%20but%20Microsoft%20and%20Yealink%20did%20not%20find%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2340406%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2340406%22%20slang%3D%22en-US%22%3EHi%20All%2C%3CBR%20%2F%3EAn%20update%20on%20our%20side.%20We%20are%20using%20Intune%20and%20when%20we%20allowed%20the%20device%20to%20be%20enrolled%20when%20the%20user%20signs%20in%20the%20issue%20does%20not%20happen.%3CBR%20%2F%3ENot%20sure%20why%20but%20it%20seems%20stable.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2341823%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2341823%22%20slang%3D%22en-US%22%3EJeroen%2C%20can%20you%20give%20additional%20details%20on%20what%20you%20had%20to%20do%20to%20fix%20it%3F%3CBR%20%2F%3EWe%20use%20ADFS%20with%20synced%20accounts%20to%20AAD.%20When%20I%20update%20a%20phone%20to%20latest%20version%2C%20seems%20ok%20at%20first%20but%20if%20user%20logs%20out%20of%20that%20phone%2C%20they%20are%20unable%20to%20log%20back%20in.%20Almost%20like%20a%20log%20in%20loop.%20It%20prompts%20user%20for%20mfa%20and%20it%20almost%20looks%20like%20it%20is%20going%20to%20log%20in%20but%20then%20it%20goes%20back%20to%20original%20start%20page%20where%20it%20displays%20the%20login%20code.%20This%20happens%20on%20or%20off%20internal%20network.%20I%20did%20create%20a%20test%40company.onmicrosoft.com%20and%20it%20seems%20to%20work%20fine.%3CBR%20%2F%3ERolling%20back%20to%20older%20firmware%20like%206.0.X%20on%20Poly%20CCX%20phones%2C%20user%20is%20able%20to%20log%20in%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2344500%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2344500%22%20slang%3D%22en-US%22%3EHi%20_tricks%2C%20what%20I%20did%20was%20allow%20the%20IP%20phone%20to%20enroll%20into%20Intune.%20The%20Yealink%20T55A%20we%20use%20has%20Android%20version%207.1%20and%20can%20only%20be%20enrolled%20into%20Intune%20as%20%22device%20administrator%22%20which%20we%20actually%20are%20blocking%20for%20personal%20devices.%3CBR%20%2F%3ESo%20what%20we%20did%20was%20upload%20the%20serial%20number%20of%20the%20Yealink%20phone%20into%20Intune%20as%20a%20corporate%20identifier.%20This%20will%20then%20allow%20the%20device%20to%20be%20enrolled.%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20we%20had%20the%20device%20enrolled%20into%20Intune%20we%20could%20log%20out%20and%20back%20in.%20Using%20different%20user%20accounts%20and%20the%20device%20kept%20working.%20As%20soon%20as%20I%20removed%20the%20device%20from%20Intune%20enrollment%20and%20tried%20the%20log%20out%20%2F%20log%20in%20it%20would%20get%20into%20the%20loop%20again.%3CBR%20%2F%3ESo%20without%20Intune%20enrollment%20we%20still%20need%20to%20downgrade%20the%20Teams%20app%20version%20and%20device%20firmware......%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20you%20could%20say%20this%20is%20kind%20of%20a%20workaround.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2344579%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2344579%22%20slang%3D%22en-US%22%3EI've%20done%20a%20single%20device%20test%20successfully%20doing%20what%20Jeroen%20described...a%20Trio%20C60.%20Our%20Android%20version%20%22floor%22%20is%20currently%20excluding%20the%20single%20AudioCodes%20C450HD%20test%20device%20I%20have%20and%20I've%20not%20pushed%20to%20have%20the%20floor%20lowered%20just%20for%20the%20test.%20Registering%20the%20device's%20serial%20along%20in%20InTune%20didn't%20get%20around%20our%20Android%20version%20limit.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2363780%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Phone%20device%20refuse%20login%20with%201449%2F1.0.94.2021033002%20firmware%20and%20ADFS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2363780%22%20slang%3D%22en-US%22%3EEVERYONE....please%20reach%20out%20to%20your%20TAMs%2C%20support%20engineers%2C%20whoever%20you%20can%20and%20push%20for%20greater%20visibility%20of%20this%20issue!%20We've%20had%20a%20case%20open%20for%20a%20month%20now%20and%20getting%20pretty%20much%20nowhere.%20Last%20week%2C%20MS%20engaged%20Poly%20support%20believing%20it%20to%20be%20their%20problem%20for%20some%20reason...as%20if%20it's%20a%20base%20firmware%20issue%20rather%20than%20a%20problem%20with%20the%20Teams%20app%20code%20itself.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20I%20understand%20it%2C%20the%20base%20firmware%20is%20%22owned%22%20by%20the%20phone%20manufacturers.%20Of%20course%20every%20manufacturers%20firmware%20is%20different.%20Our%20Poly%20phones%20run%20Android%209.%20I%20know%20the%20AudioCodes%20C450HD%20runs%20Android%207.%20It%20seems%20pretty%20obvious%20to%20me%20that%20the%20common%20thread%20between%20Poly%2C%20AudioCodes%2C%20and%20Yealink%20phones%20is%20the%20Teams%20app%20code%20itself%2C%20not%20the%20base%20firmware.%3CBR%20%2F%3E%3CBR%20%2F%3EKeep%20in%20mind%20that%20we%20(the%20customer)%20haven't%20been%20given%20control%20to%20disable%20automatic%20firmware%20upgrades%20from%20Teams%20Admin%20Center.%20The%20best%20we%20can%20do%20is%20defer%2090%20days.%20Even%20if%20you%20back-level%20the%20code%2C%20the%20phone%20is%20going%20to%20get%20the%20upgrade%20forced%20back%20down%20to%20it%20by%20Microsoft.%20And%20if%20you%20miss%20one%20setting%20the%2090%20day%20deferral%2C%20that%2030%20days%20is%20going%20to%20be%20hitting%20you%20very%20soon.%3C%2FLINGO-BODY%3E
Frequent Contributor

Has anybody been using ADFS with Teams noticed an issue with the last two firmware updates, when performing logins off-network?

 

I have a customer running Yealink MP56 phones and the latest firmware 122.15.0.36 running Teams App 1449/1.0.94.2021022403 or 1449/1.0.94.2021033002 can no longer login using either the device login code or typing user/pass. The login seems to get stuck in a loop between device registration and preparing the device.

 

I suspect this is partially to do with the ADFS configuration not using UPN for authentication, but this wasn't an issue prior to 1449/1.0.94.2021022403.

26 Replies
I'm having the same issue with a Yealink T55A. Once the update was completed, the phone will not receive a device code for provisioning.
Same issue here. Yealink MP54 and AudiocodesC450HD.
Are you able to open a support ticket with Microsoft? Can you send me the ticket number as a message you've opened it?
Don't know if this helps anyone, but I opened tickets with Microsoft Teams support, Azure support, and Yealink. So far, everyone is saying it's someone else's issue. This has been going on for about 9 days.
It would be helpful if you can send me a message with the Microsoft Teams ticket details. I am a PM in the team, and would like to see this ticket.
DM sent with ticket number. I did speak with a contact at Yealink yesterday and they suggested a possible issue with device count limits, but I realized this morning I'm trying to login to the same device I already have registered under the tenant so it shouldn't (in theory) be that.

Rolling back to an earlier firmware and Teams app from last year seems to resolve the issue. Upgrading again breaks it.
I sent the ticket information in a DM. The ticket with Azure was closed because it was a 'duplicate' ticket. Yealink also said it may be a problem with too many devices for the user, but only one is assigned and I have set my company limit to 20, so that should not be an issue. I am going to try to downgrade it today, similar to what jangliss did, to see if my problem is fixed.

@Jacob_B 

 

I am assuming you are using ADFS? Did Microsoft gather the ADFS logs from your failed attempts? I'm working on gathering those myself.

 

I've gone back and done additional testing and it doesn't appear to be limited to a particular vendor. I've tested with Poly CCX 400, CCX 500, and CCX 700, AudioCodes HD450, Yealink T56A, T58A, and MP56.  It's after deploying the February update which appears to be bundled with most of the latest firmwares from the vendors, things break.  Going to roll back a few firmware and do additional testing to verify.

If possible, could you send this ticket information to me as well? I am deploying an MP56 with the same firmware/Teams version, and the same problem.

Also, to confirm, are you seeing the "Oops, you can't access this right now." error when attempting to login?
I was not able to find any failed logins in any of the Microsoft cloud services, it's like the device is not connecting or seeing Microsoft at all. I checked my firewall to verify that no ports needed to access and run Teams are being blocked. Downgrading did not help, so no luck there. I sent a video of the issue to Microsoft today for them to view the problem that I am running into.
FYI - the phone is not saving the time settings when it's rebooted which may be part of the problem.
I originally opened this thinking it might have been ADFS related, but also seeing this across tenants not using ADFS. This seems like a big issue!
We are having the same issue with Poly C60 conference room phones once updated to firmware 7.0.2.1071. This firmware comes with Teams App 1449/1.0.94.2021022403 and we get the same login loop. I've tried updating to Teams App 1449/1.0.94.2021033002 but problem persists. I have tried both the original web login method as well as the new remote provision/login method and both result in the same login loop.

If I roll the firmware back to 5.9.5.3153 and Teams App 1449/1.0.94.2020121001, I can web login the phone again without issue. I can then fully upgrade the phone's firmware and Teams App version to latest and the phone will stay logged in. However, if I log it out, I can't log it back in as it gets stuck in the same loop.
The biggest issue of all is that there's no way to stop these phones from automatically getting the update eventually! Deferring for 90 days is the best we can do and that's a very manual process to have to set each and every phone as they come in. Imagine how rough it's going to be when you have hundreds of phones!
Has anyone found a real solution to this issue? I am about to start rolling back firmware but was hoping someone has an answer.
I've not heard anything back on our open Microsoft support ticket but the more people that open tickets, the more visibility this is going to get for quicker resolution.
I'd definitely agree. Open tickets if you haven't already. I've not heard anything from support on my ticket other than "sorry for the delay, we're waiting to hear back from engineering".