You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-365/known-issues-enterprise.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Windows 365 Enterprise and Frontline Known issues
3
3
description: Learn about known issues for Windows 365 Enterprise.
4
4
manager: dcscontentpm
5
-
ms.date: 10/29/2025
5
+
ms.date: 11/17/2025
6
6
ms.topic: troubleshooting
7
7
ms.reviewer: msft-jasonparker, stulimat, scottduf
8
8
ms.custom:
@@ -17,7 +17,7 @@ ms.collection:
17
17
18
18
The following items are known issues for Windows 365 Enterprise.
19
19
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
21
21
22
22
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.
23
23
@@ -27,27 +27,27 @@ When you use Conditional Access, a user who signs in to a Cloud PC for the first
27
27
28
28
## Watermarking support in Windows 365
29
29
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.
31
31
32
32
### Solution
33
33
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**.
35
35
36
36
For more information, see [Administrative template for Azure Virtual Desktop](/azure/virtual-desktop/administrative-template?tabs=intune#configure-the-administrative-template).
37
37
38
38
[!INCLUDE [Missing Start menu and taskbar when using iPad and the Remote Desktop app to access a Cloud PC](includes/known-issues.md)]
39
39
40
40
## In-place Windows upgrade might change the computer name
41
41
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.
43
43
44
44
### Solution
45
45
46
46
Find and manage the Cloud PC in Microsoft Intune by using the unchanged Intune device name, either through the **Devices** > **All devices** list or the **Devices** > **Windows 365** > **All Cloud PCs** list.
47
47
48
48
## Windows 365 provisioning fails<!--38483005-->
49
49
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:
51
51
52
52
- The Desired State Configuration (DSC) extension isn't signed.
53
53
- The PowerShell Execution policy is set to **AllSigned** in the GPO.
@@ -72,19 +72,19 @@ The following device compliance settings might report as **Not Compliant** when
72
72
73
73
### Solution
74
74
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)
76
76
77
-
To remove not compliant settings:
77
+
To remove "not compliant" settings:
78
78
79
79
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.
82
82
83
83
## Single sign-on users see a dialog to allow remote desktop connection during the connection attempt <!--42499792-->
84
84
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.
86
86
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).
0 commit comments