Is there some sort of microsoft timeout for login.microsoftonline.com where the token expires? We’re utilizing Dell ThinOS thin clients and in WMS I have the broker set to Azure AVD.

When this is applied to the thin client, immediately a microsoft login box pops up over the Dell Login UI. If no user enters credentials in that login window for a while (I believe it’s 30-60min), the next person who tries to login receives the following message “Sorry, your sign-in timed out. Please sign in again.” It doesn’t say the credentials are invalid (because they aren’t) it just doesn’t successfully authenticate. At this point it does show our tenants custom background..

At that point the user can type their credentials in again and it successfully authenticates them. My worry is that we’ll have this happen to the first user who logs into each thin client every single morning and throughout the day as the thin clients set idle. 

There aren’t many options you can set for the Azure broker. I was wondering if anyone else has come across this and has a potential solution? Something to note is I’m also experiencing this from a web browser outside of utilizing a thin client across different tenants.

​Is there some sort of microsoft timeout for login.microsoftonline.com where the token expires? We’re utilizing Dell ThinOS thin clients and in WMS I have the broker set to Azure AVD. When this is applied to the thin client, immediately a microsoft login box pops up over the Dell Login UI. If no user enters credentials in that login window for a while (I believe it’s 30-60min), the next person who tries to login receives the following message “Sorry, your sign-in timed out. Please sign in again.” It doesn’t say the credentials are invalid (because they aren’t) it just doesn’t successfully authenticate. At this point it does show our tenants custom background.. At that point the user can type their credentials in again and it successfully authenticates them. My worry is that we’ll have this happen to the first user who logs into each thin client every single morning and throughout the day as the thin clients set idle.  There aren’t many options you can set for the Azure broker. I was wondering if anyone else has come across this and has a potential solution? Something to note is I’m also experiencing this from a web browser outside of utilizing a thin client across different tenants.  Read More

​