MicrosoftHi Adam,
thank you for this promising information.
We've opened a case, the result after a couple of weeks of troubleshooting was the link to this blog entry.
It is a big issue, as it is not only accepting SSO, it destroys the Seamless SSO feature completely for M365 Apps. The user needs to type in UserName and Password every single day. The workaround is working right now, but will DisableAADWAM and DisableADALatopWAMOverride what is using an old libary work until the end of the year so we can use this until a proper solution is in place?
Also can you please update this articel. In here there is no hint that Seamless SSO for M365 Apps is not working as described anymore in the EU.
https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sso-how-it-works#how-does-sign-in-on-a-native-client-with-seamless-sso-work
From our point of view it is dramatic. We consult many customers and right now for all Customers with non-persistent devices or even persistent but floating assignment can not implement M365 Apps, as typing in Credentials every single day with opening Word will result in many tickets and complaints by the users.
To not stop migrate customers to M365. Will the workaround (DisableAADWAM and DisableADALatopWAMOverride) work until there is a proper solution?
Thank you in advance,
Nico
