Windows 365 Enterprise known issues

This page's changes and edits · All guidance changes

Microsoft's edit · 5 May 20:55 UTC

Update known issues for Windows 365 Flex and Enterprise

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

11 ---

2 −title: Windows 365 Enterprise and Frontline Known issues

3 −description: Learn about known issues for Windows 365 Enterprise.

2 +title: Windows 365 Enterprise and Windows 365 Flex Known issues

3 +description: Learn about known issues for Windows 365 Enterprise and Windows 365 Flex.

44 manager: dcscontentpm

5 −ms.date: 11/17/2025

5 +ms.date: 05/05/2026

66 ms.topic: troubleshooting

7 −ms.reviewer: msft-jasonparker, stulimat, scottduf

7 +ms.reviewer: kaushika, msft-jasonparker, stulimat, scottduf

88 ms.custom:

99 - pcy:WinComm User Experience

1010 - sap:Onboarding issues

⋯ 2 unchanged lines

1313 - tier2

1414 ---

1515

16 −# Windows 365 Enterprise and Frontline known issues

16 +# Windows 365 Enterprise and Windows 365 Flex known issues

1717

18 −The following items are known issues for Windows 365 Enterprise.

18 +The following items are known issues for Windows 365 Enterprise and Windows 365 Flex.

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 −

237229 ## Windows 365 scope tags and nested groups

238230

239231 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.

⋯ 37 unchanged lines

277269

278270 - To add the WebRTC Redirector Service app to an individual Cloud PC, follow the steps in [Install the Remote Desktop WebRTC Redirector Service](/azure/virtual-desktop/teams-on-avd#install-the-remote-desktop-webrtc-redirector-service). To get the most up-to-date installer, see [https://aka.ms/msrdcwebrtcsvc/msi](https://aka.ms/msrdcwebrtcsvc/msi).

279271

280 −## Windows 365 Frontline issues

272 +## Windows 365 Flex issues

281273

282 −The following items are known issues for Windows 365 Frontline.

274 +The following items are known issues for Windows 365 Flex.

283275

284 −### Users can't access Frontline Cloud PCs that are in shared mode

276 +### Users can't access Windows 365 Flex Cloud PCs that are in shared mode

285277

286 −When Frontline Cloud PCs in shared mode are assigned to a Microsoft Entra ID group that has more than 10,000 members, some users might not receive access and don't see the Cloud PC cards in the Windows app client.

278 +When Windows 365 Flex Cloud PCs in shared mode are assigned to a Microsoft Entra ID group that has more than 10,000 members, some users might not receive access and don't see the Cloud PC cards in the Windows app client.

287279

288280 #### Solution

289281

⋯ 15 unchanged lines

305297

306298 ### Scheduled reprovisioning doesn't recover after license changes

307299

308 −When Frontline Cloud PCs are provisioned in shared mode, and licenses expire or are removed from the tenant, the Cloud PCs are deprovisioned. After you add back valid licenses, Cloud PCs provision according to the policy configurations. However, both scheduled reprovisioning and manual reprovisioning functionality remain disabled.

300 +When Windows 365 Flex Cloud PCs are provisioned in shared mode, and licenses expire or are removed from the tenant, the Cloud PCs are deprovisioned. After you add back valid licenses, Cloud PCs provision according to the policy configurations. However, both scheduled reprovisioning and manual reprovisioning functionality remain disabled.

309301

310302 #### Solution

311303

⋯ 11 unchanged lines

323315

324316 ### Can't decrease Cloud PC count due to pooled user storage limits

325317

326 −You can't reduce the number of Cloud PCs for Frontline Cloud PCs in shared mode if the operation would cause the amount of pooled user storage to exceed its limit.

318 +You can't reduce the number of Cloud PCs for Windows 365 Flex Cloud PCs in shared mode if the operation would cause the amount of pooled user storage to exceed its limit.

327319

328320 #### Solution

329321

⋯ 15 unchanged lines

345337 #### Solution

346338

347339 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.

356340

357341 ## Next steps

358342

⋯ 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.