Skip to content

Commit eed70b3

Browse files
author
Simonx Xu
authored
Merge pull request #8968 from MicrosoftDocs/v-lianna-patch-12
AB#5916 Update known-issues-enterprise.md
2 parents 239bd34 + bd30638 commit eed70b3

1 file changed

Lines changed: 11 additions & 3 deletions

File tree

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

Lines changed: 11 additions & 3 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/23/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
@@ -269,7 +269,15 @@ If provisioning fails due to an Autopilot Device Preparation Profile (DPP) (Prev
269269
270270
#### Solution
271271
272-
Perform reprovision in the provisioning policy.
272+
Perform a reprovisioning action in the provisioning policy.
273+
274+
### Scheduled reprovisioning doesn't recover if Frontline licenses are removed or expire from a tenant and then 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 licenses are added. After the licenses are added back, the Cloud PCs will be provisioned according to the configurations defined in the provisioning policy. If you have configured a scheduled reprovisioning for a provisioning policy, the scheduled reprovisioning won't be reactivated. Manual reprovisioning action also fails.
277+
278+
#### Solution
279+
280+
To recover full functionality of manual and scheduled reprovisioning after license expiration, remove the provisioning policy assignment and then add it again.
273281
274282
## Next steps
275283

0 commit comments

Comments
 (0)