New Teams sign in error

[DFMIT]

I have the new teams installed and when a user logs into an instant clone non-persistent desktop, teams will open but at the top it will have a red bar with a sign in error, if you click sign in button at the top right, it will then prompt for MFA and everything will work. Has anyone else had this and were you able to resolve it.

I am using FSLOGIX office container to hold teams data.
I also have a DEM profile setup to retain some of the settings that the office container does not, such as auto start teams on windows login.

[Dominik]

Hello,

as far as remember I use this DEM settings to get Teams settings, include logon information. You can test on yours ENV.

Most important is folders, because in this place some information about logon are stored:

<LocalAppData>\Microsoft\Vault

<AppData>\Microsoft\Vault

DEM settings:

[IncludeRegistryTrees]
 
HKCU\Software\Microsoft\Office\Teams
 
 
[IncludeFolderTrees]
 
<LocalAppData>\Microsoft\Credentials
 
<LocalAppData>\Microsoft\Teams
 
<LocalAppData>\Microsoft\TeamsMeetingAddin
 
<LocalAppData>\Microsoft\TeamsPresenceAddin
 
<LocalAppData>\SquirrelTemp
 
<LocalAppData>\Microsoft\IdentityCache
 
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
<AppData>\Microsoft\Teams
 
<AppData>\Microsoft Teams
 
<AppData>\Teams

<AppData>\Microsoft\Protect

<LocalAppData>\Microsoft\Vault

<AppData>\Microsoft\Vault

 
 
[ExcludeFolderTrees]
 
<AppData>\Teams\logs
 
<AppData>\Microsoft\Teams\media-stack
 
<AppData>\Microsoft\Teams\Service Worker
 
<AppData>\Microsoft\Teams\Application Cache
 
<AppData>\Microsoft\Teams\Cache
 
<AppData>\Microsoft\Teams\tmp
 
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\TempState
 
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Temp
 
 
[ExcludeFiles]
 
<AppData>\Microsoft\Teams\logs.txt
 
<AppData>\Microsoft\Teams\lockfile
 

 

[DFMIT]

I am seeing the issue on the New Teams 2.1 not the classic teams.

[Zeno]

Hello DFMIT,

Did you solve this problem?

I have the same setup(New Teams 2.1 on non-persistent Win 11 23H2, ODFC, DEM) and I am facing the same issue.

[DFMIT]

I still do not have a resolution so I have kept teams classic in our production environment.

[BenTrojahn]

For us, this issue only happens on some 0365 with admin roles WHERE mfa was required.  The clue was that the issue happens in the full Outlook client where we not have expected an MFA prompt on prem.  Remove that role or MFA requirement and the issue went away.  All O365 apps now login automatically. 

Edited August 22 by BenTrojahn

[Holly Lehman]

@DFMIT based on this thread, did the reply from @BenTrojahn solve your issue, or are you still keeping with the classic Teams environment?

[Zeno]

On 8/26/2024 at 5:31 PM, Holly Lehman said:

@DFMIT based on this thread, did the reply from @BenTrojahn solve your issue, or are you still keeping with the classic Teams environment?

It didn’t work for me. My test user doesn't have any admin roles, MFA is enabled by Conditional access policy but the VDI public IP address is excluded as a trusted location.
OneDrive and Outlook sign in without any problems; it’s just Teams 2.1 that’s having issues.

I checked the Signin Logs and I noticed Error 9002341 

This led me to the comments on this article: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/upcoming-changes-to-windows-single-sign-on/bc-p/4167626/highlight/true#M7419

The failing SSO seems to be a known problem with non-persistant machines.

The mentioned workaround in the comments (EnableADAL,DisableAADWAM, DisableADALatopWAMOverride) didn't work for me either.

I guess the next thing I will try in the lab is hybrid joining the machines, at the moment i'm using AD Seamless SSO

Edited September 2 by Zeno

[vap0r]

Same issue here, been testing like crazy trying to get consistent sign in results with New Teams in my non persistent VDI environment but absolutely no luck.

[StephenWagner7]

AFAIK, using conditional access policies will not work if the Instant Clone isn't hybrid domain joined (Azure SSO via PRT). Someone please correct me if I'm wrong on this one...

[DFMIT]

All of our users see the error message, as they all have the MFA requirement.