Skip to content

Commit e0371d3

Browse files
authored
Merge pull request #6762 from ChristianMontoya/patch-7
Updating AADJ errors on W365 Connection Errors
2 parents f5d5de4 + c057e53 commit e0371d3

2 files changed

Lines changed: 19 additions & 6 deletions

File tree

windows-365/enterprise/connection-errors.md

Lines changed: 19 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: ErikjeMS
88
ms.author: erikje
99
manager: dougeby
10-
ms.date: 02/08/2022
10+
ms.date: 02/10/2022
1111
ms.topic: reference
1212
ms.service: cloudpc
1313
ms.subservice:
@@ -32,14 +32,27 @@ ms.collection: M365-identity-device-management
3232

3333
The following errors can occur when connecting to a Cloud PC.
3434

35-
## Errors when connecting to an Azure AD join Cloud PC
35+
## Errors when connecting to an Azure Active Directory (Azure AD) joined Cloud PC
3636

37-
**Potential cause**: Possible causes for connection errors include:
37+
### The logon attempt failed
38+
**Potential cause #1**: The Cloud PC denied PKU2U protocol requests. The PKU2U protocol is only triggered in the following cases:
3839

39-
- Windows sign-in works directly against Azure AD, potentially triggering Azure AD authentication controls.
40-
- Sign-in attempts from the Windows desktop client to a Cloud PC use a different protocol, called PKU2U.
40+
- The Cloud PC is Azure AD joined.
41+
- The user is connecting from the Windows desktop client.
42+
- The user's physical device is Azure AD registered, Azure AD joined, or hybrid Azure AD joined to the same organization as the Cloud PC.
4143

42-
**Possible solution**: Follow the guidance to [troubleshoot connections to Azure AD joined VMs](/azure/virtual-desktop/troubleshoot-azure-ad-connections?context=/windows-365/context/pr-context).
44+
**Possible solution**: Turn on PKU2U protocol requests on your Cloud PC:
45+
46+
1. [Create a filter for all Cloud PCs](create-filter.md#create-a-filter-for-all-cloud-pcs).
47+
2. Create a device configuration policy [using the settings catalog](/mem/intune/configuration/settings-catalog).
48+
3. On the **Configuration settings** page, search for and select **Network Security Allow PKU2U Authentication Requests** > **Allow**.
49+
![Screenshot with the **Network Security Allow PKU2U Authentication Requests** set to **Allow**.](./media/connection-errors/allow-pku2u.png)
50+
5. On the **Assignments** page, select **Add all devices** > **Edit filter** > **Include filtered devices in assignment** > select the filter you created for all Cloud PCs.
51+
6. Complete the creation of the device configuration policy.
52+
53+
**Potential cause #2**: [Per-user multi-factor authentication](/azure/active-directory/authentication/howto-mfa-userstates) is turned on for the user account. Because it blocks sign-in, per-user multi-factor authentication isn't supported for users connecting to Azure AD joined Cloud PCs.
54+
55+
**Possible solution**: [Remove per-user multi-factor authentication](/azure/active-directory/devices/howto-vm-sign-in-azure-ad-windows#mfa-sign-in-method-required) for all users connecting to Cloud PCs. Then, [set an Azure AD conditional access policy](set-conditional-access-policies.md) and assign it to the appropriate users.
4356

4457
## Specific connection errors
4558

105 KB
Loading

0 commit comments

Comments
 (0)