Windows 365 Enterprise known issues

This page's changes and edits · All guidance changes

Microsoft's edit · 13 Nov 2025 23:07 UTC

Edits

Microsoft's commit message in MicrosoftDocs/SupportArticles-docs · commit e9bcc19 · +12 ~~−12~~ lines · also on GitHub

⋯ 1 unchanged line

22 title: Windows 365 Enterprise and Frontline Known issues

33 description: Learn about known issues for Windows 365 Enterprise.

44 manager: dcscontentpm

5 −ms.date: 10/29/2025

5 +ms.date: 11/17/2025

66 ms.topic: troubleshooting

77 ms.reviewer: msft-jasonparker, stulimat, scottduf

88 ms.custom:

⋯ 8 unchanged lines

1717

1818 The following items are known issues for Windows 365 Enterprise.

1919

20 −## First-time Cloud PC sign-in triggers Impossible Travel Location alert

20 +## First-time Cloud PC sign-in triggers an impossible travel location alert

2121

2222 When you use Conditional Access, a user who signs in to a Cloud PC for the first time might trigger an impossible travel location alert.

2323

⋯ 3 unchanged lines

2727

2828 ## Watermarking support in Windows 365

2929

30 −Watermarking support is configured on session hosts and enforced by the Remote Desktop client. The settings for Watermarking support can be configured via Group Policy (GPO) or the Intune Settings Catalog. The default for the QR code embedded content setting doesn't allow administrators to look up device information from leaked images for Cloud PCs.

30 +Watermarking support is configured on session hosts and enforced by the Remote Desktop client. You can configure Watermarking support by configuring a Group Policy Object (GPO) or the Intune Settings Catalog. The default for the QR code embedded content setting doesn't allow administrators to look up device information from leaked images for Cloud PCs.

3131

3232 ### Solution

3333

34 −Ensure that the QR code embedded content setting is configured to **Device ID** either in the GPO or the Intune Settings Catalog for the Intune Configuration profile used to configure Watermarking support.

34 +Check the GPO or the Intune Settings Catalog for the Intune Configuration profile that you used to configure Watermarking support. Make sure that the QR code embedded content setting is configured to **Device ID**.

3535

3636 For more information, see [Administrative template for Azure Virtual Desktop](/azure/virtual-desktop/administrative-template?tabs=intune#configure-the-administrative-template).

3737

⋯ 1 unchanged line

3939

4040 ## In-place Windows upgrade might change the computer name

4141

42 −Upgrading an existing Cloud PC between release versions of Windows 10 to Windows 11 might cause the computer name to be changed to a name with a prefix of "pps" while leaving the Intune device name unchanged.

42 +Upgrading an existing Cloud PC between release versions of Windows 10 to Windows 11 might cause the computer name to change to a name that has a prefix of "pps." The Intune device name remains unchanged.

4343

4444 ### Solution

4545

⋯ 1 unchanged line

4747

4848 ## Windows 365 provisioning fails

4949

50 −Windows 365 provisioning failures might occur if both of the following conditions are met:

50 +Windows 365 provisioning might fail if both of the following conditions are met:

5151

5252 - The Desired State Configuration (DSC) extension isn't signed.

5353 - The PowerShell Execution policy is set to **AllSigned** in the GPO.

⋯ 18 unchanged lines

7272

7373 ### Solution

7474

75 −To enable secure boot on the Cloud PC, see [Reprovision](/windows-365/enterprise/reprovision-cloud-pc) the specific Cloud PC.

75 +To enable secure boot on the Cloud PC, reprovision the specific Cloud PC. for more information, see see [Reprovision a Cloud PC](/windows-365/enterprise/reprovision-cloud-pc)

7676

77 −To remove not compliant settings:

77 +To remove "not compliant" settings:

7878

7979 1. [Create a filter for all Cloud PCs](/windows-365/enterprise/create-filter#create-a-filter-for-all-cloud-pcs).

80 −2. For any existing device compliance policies that both evaluate to a Cloud PC and contain either of the **Not Compliant** settings, use this new filter to exclude Cloud PCs from the policy assignment.

81 −3. Create a new device compliance policy without either of the **Not Compliant** settings and use this new filter to include Cloud PCs for the policy assignment.

80 +1. For any existing device compliance policies that both evaluate to a Cloud PC and contain either of the **Not Compliant** settings, use this new filter to exclude Cloud PCs from the policy assignment.

81 +1. Create a new device compliance policy without either of the **Not Compliant** settings and use this new filter to include Cloud PCs for the policy assignment.

8282

8383 ## Single sign-on users see a dialog to allow remote desktop connection during the connection attempt

8484

85 −When you enable single sign-on, a prompt appears to authenticate to Microsoft Entra ID and allow the Remote Desktop connection when launching a connection to a new Cloud PC. Microsoft Entra remembers up to 15 devices for 30 days before prompting again. If you see this dialog, select **Yes** to connect.

85 +When you enable single sign-on, you see a prompt to authenticate to Microsoft Entra ID and allow the Remote Desktop connection when launching a connection to a new Cloud PC. Microsoft Entra remembers up to 15 devices for 30 days before prompting again. If you see this dialog, select **Yes** to connect.

8686

87 −To prevent this dialog from appearing, you can create a preconsented device group. Follow the instructions to [configure a target device group](/azure/virtual-desktop/configure-single-sign-on#configure-the-target-device-groups) to get started.

87 +To prevent this dialog from appearing, you can create a preconsented device group. To get started, fFollow the instructions to [configure a target device group](/azure/virtual-desktop/configure-single-sign-on#configure-the-target-device-groups).

8888

8989 <a name='single-sign-on-user-connections-are-being-denied-through-azure-ad-conditional-access---42317382--'></a>

9090

⋯ 254 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/SupportArticles-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 00:39 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.