Forum Discussion
Fslogix (2.9.8308.44092)
so the best solution is to stay under the FsLogix version (2.9.8308.44092) from this version onwards the problem arises, can it be fixed with a patch that will make Microsoft fslogix?
We did a rollback to version 2.9.8228.50276 and have no problems at the moment.
Waiting for an update of Microsoft that tackles the issues.
TiboV let's wait, whoever has news first shares
thank youScherubini Problem is known officialy now:
https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#azure-ad-authentication-for-applications
Users may be required to authenticate to their applications (for example, Microsoft 365 apps, Teams (work or school), OneDrive, etc.) at every sign-in. The repeated authentication prompts are due to the virtual machines Azure AD device state. We recommend virtual machines are Azure AD Joined (AADJ) or Hybrid Azure AD Joined (HAADJ) for the best user experience.
Virtual machines, which are AADJ or HAADJ create the user's primary refresh token (PRT) at sign-in. Primary refresh token(s) created at sign-in will be used to authenticate to Azure AD based applications. Standard Domain Joined (DJ) virtual machines don't create a PRT at sign-in, instead rely on the Microsoft Azure AD broker plugin.
Azure AD broker directories and apps
Starting in FSLogix 2210 (2.9.8361.52326) and later versions, all content stored in following locations is no longer roamed as part of the user profile.
%USERPROFILE%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
%USERPROFILE%\AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy
%USERPROFILE%\AppData\Local\Microsoft\TokenBroker- thank you very much so whoever wants to use the version of FSLogix 2210 from (2.9.8361.52326) and later what should he do?