Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 22:55 UTC Customize Public modeDiscuss ChangeIntel on Discord

Windows 365 Enterprise known issues

This page's changes and edits · All guidance changes

Microsoft's edit ·

Learn Editor: Update known-issues-enterprise.md

Microsoft's commit message in MicrosoftDocs/SupportArticles-docs · commit b9610ef · +19 −3 lines · also on GitHub

11 ---
22 title: Windows 365 Enterprise and Frontline Known issues
3 −description: Learn about known issues for Windows 365 Enterprise and Frontline.
3 +description: Learn about known issues for Windows 365 Enterprise.
44 manager: dcscontentpm
5 −ms.date: 02/12/2026
5 +ms.date: 11/17/2025
66 ms.topic: troubleshooting
77 ms.reviewer: msft-jasonparker, stulimat, scottduf
88 ms.custom:
⋯ 6 unchanged lines
1515
1616 # Windows 365 Enterprise and Frontline known issues
1717
18 −The following items are known issues for Windows 365 Enterprise and Frontline.
18 +The following items are known issues for Windows 365 Enterprise.
1919
2020 ## First-time Cloud PC sign-in triggers an impossible travel location alert
2121
⋯ 204 unchanged lines
226226 - **Enable screen capture protection** = **Enable**
227227 - **Screen Capture Protection Options** = **Block screen capture on client and server**
228228
229 +## Windows 365 role assignments do not support device groups as scope groups
230 +
231 +Windows 365 role assignments do not support adding device group as a part of scope groups. It only supports user groups.
232 +
233 +### Solution
234 +
235 +Make sure to add the right user groups within the administrator's role assignment. For devices that do not have associated users (Frontline in shared mode devices or CloudApps), the scope group check is skipped.
236 +
229237 ## Windows 365 scope tags and nested groups
230238
231239 Windows 365 doesn't support nested security groups. If you apply a scope tag to the top of a nested security group, Cloud PCs in inner nested groups aren't assigned scope tags.
⋯ 105 unchanged lines
337345 #### Solution
338346
339347 Wait for the process to continue. Cloud PC serial numbers can take up to 30 minutes to appear in the status information.
348 +
349 +### Windows Autopilot Device Preparation is not currently supported for Citrix Cloud PCs
350 +
351 +Device preparation policies (DPP) aren't supported for Cloud PCs that are configured to use Citrix integration. If you assign a device preparation policy to a provisioning policy that’s used for Citrix Cloud PCs, the policy won't be applied during Cloud PC provisioning.
352 +
353 +#### Solution
354 +
355 +There is currently no workaround. To use Citrix integration, configure your Cloud PCs by using a provisioning policy that doesn’t include a device preparation policy.
340356
341357 ## Next steps
342358
⋯ 1 unchanged line

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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 22:55 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current