Authentication Issues when using Conditional Access
When using the Microsoft Teams thick client on Windows there is a client timing issue when using Conditional Access in certain use cases. For example, if the Teams client launches before the operating system has established connectivity to the network, connected to VPN, etc. it will get blocked from connecting based on one's Conditional Access criteria. Rather than retrying periodically in the background it just fails. This results in a really bad user experience and often people do not understand they need to relaunch the client or log back in for it to try again. The expected behavior would be that it would periodically attempt to login in the background every 15-60 seconds for a seamless user experience, at least for the first few minutes after logging into the machine. Please fix this behavior in the Teams thick client app for Windows. The expected behavior is similar to how the Skype for Business client works.