![]() Signing in to the Cloud PC with Azure Active Directory-only user accounts Possible solution: Update VPN clients to the most up-to-date versions. Some other possible causes for Cloud PC connection failures include: Out-of-date third-party VPN client versions Possible solution: If the issue persists, sign in to > select the cog icon next to the Cloud PC > Restart. Potential cause: This error can occur when the Cloud PC’s processor is over-utilized. If this keeps happening, contact your network administrator for assistance. ![]() Possible solution: Review the settings and confirm that they aren’t interfering with connections. Potential cause: This error can be caused by network configuration settings, like: If this keeps happening, ask your admin or tech support for help. We couldn't connect to the gateway because of an error. Possible solution: Sign in to > select the cog icon next to the Cloud PC > Restart. Potential cause: There may be a resource issue on your Cloud PC. Specific connection errors We couldn't connect because there are currently no available resources Then, set an Azure AD conditional access policy and assign it to the appropriate users. Possible solution: Remove per-user multi-factor authentication for all users connecting to Cloud PCs. Because it blocks sign-in, per-user multi-factor authentication isn't supported for users connecting to Azure AD joined Cloud PCs. Potential cause #2: Per-user multi-factor authentication is turned on for the user account. ![]() If you only manage the user's physical device through Group Policy or you don't manage the user's physical device, you (or the user) can manage this setting through the allow PKU2U authentication requests to this computer to use online identities policy.
0 Comments
Leave a Reply. |