Skip to content

Commit 3be6b9f

Browse files
authored
AB#5916 Update known-issues-enterprise.md
1 parent 7719d24 commit 3be6b9f

1 file changed

Lines changed: 10 additions & 2 deletions

File tree

support/windows-365/known-issues-enterprise.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22
title: Known issues for Windows 365 Enterprise and Frontline
33
description: Learn about known issues for Windows 365 Enterprise.
44
manager: dcscontentpm
5-
ms.date: 01/20/2025
5+
ms.date: 05/21/2025
66
ms.topic: troubleshooting
7-
ms.reviewer: ivivano, erikje
7+
ms.reviewer: ivivano, erikje, scottduf
88
ms.custom: get-started
99
ms.collection:
1010
- M365-identity-device-management
@@ -271,6 +271,14 @@ If provisioning fails due to an Autopilot Device Preparation Profile (DPP) (Prev
271271
272272
Perform reprovision in the provisioning policy.
273273
274+
### Scheduled reprovisioning does not recover if Frontline licenses are removed or expire from a tenant and the are added back
275+
276+
If Frontline Cloud PCs are provisioned in shared mode and then licenses expire or are removed from the tenant, the Cloud PCs will be deprovisioned until valid liceses are added. After adding licenses back, the Cloud PCs will be provisioned according to the configurations defined in the Provisioning Policy. If you have configured a scheduled reprovision for a provisioning policy, it will not be re-activated. Manual reprovision action will also fail.
277+
278+
#### Solution
279+
280+
To recover full functionality of manual and scheduled reprovision after license expiration you should remove and then re-add the provisioning policy assignment.
281+
274282
## Next steps
275283
276284
[Troubleshoot Windows 365 Enterprise Cloud PC](/windows-365/enterprise/troubleshooting)

0 commit comments

Comments
 (0)