Skip to content

Commit 015036b

Browse files
Merge pull request #8174 from Deland-Han/ci3661
AB#3661: Win365 doc change request: Type - New troubleshooting doc re grace period
2 parents 22ccc68 + e5a9fc2 commit 015036b

2 files changed

Lines changed: 125 additions & 0 deletions

File tree

support/windows-365/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ items:
2121
href: ./troubleshoot-windows-365-boot.md
2222
- name: Windows 365 Boot known issues
2323
href: ./windows-365-boot-known-issues.md
24+
- name: Troubleshoot Windows 365 Enterprise Cloud PCs grace period issue
25+
href: ./troubleshoot-windows-365-enterprise-cloud-pcs-grace-period-issue.md
2426
- name: Windows 365 setup issues
2527
href: ./troubleshoot-windows-365-business.md
2628
- name: Windows 365 Switch known issues
Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
---
2+
title: Troubleshoot Windows 365 Enterprise Cloud PCs grace period issue
3+
description: Introduces how to troubleshoot Windows 365 Enterprise Cloud PCs that are in grace period.
4+
manager: dcscontentpm
5+
ms.date: 02/20/2025
6+
ms.topic: troubleshooting
7+
ms.reviewer: anwill
8+
---
9+
# Troubleshoot Windows 365 Enterprise Cloud PCs grace period issue
10+
11+
Windows 365 Cloud PCs provide a seamless and scalable solution for virtual desktops. However, administrators may encounter situations where a Cloud PC enters a grace period. This guide explains how to troubleshoot Cloud PCs in grace period issue.
12+
13+
## Understanding grace period
14+
15+
When a Windows 365 license is removed from a user account, their Enterprise Cloud PC enters a grace period. During this time, the Cloud PC remains accessible before it's deprovisioned. It's important to act promptly to avoid service disruption.
16+
17+
A Windows 365 Cloud PC can enter a grace period when a valid Windows 365 license is removed from a user or the connection between the user and provisioning policy is broken. This can happen in one of the following scenarios:
18+
19+
- The user account is removed from the group where the license was inherited from.
20+
- The direct license assignment is removed from the user.
21+
- The user is removed from a group that is assigned to the provisioning policy used to create the Cloud PC.
22+
23+
In any of these scenarios, the Cloud PC remains operational for seven days, allowing time to resolve the issue before the Cloud PC is deprovisioned.
24+
25+
## Actions to address grace period
26+
27+
To return Cloud PCs to a provisioned state, check the following two key areas:
28+
29+
1. Original license assignments are in place.
30+
2. Connection to the relevant provisioning policy is in place.
31+
32+
The following sections provide the necessary actions to address grace period. The sections include the following steps:
33+
34+
1. Reassign Windows 365 Enterprise licenses to users, via group-based licensing or direct assignment.
35+
2. Ensure the user is a member of any group assigned to a provisioning policy and the assignments are in place.
36+
37+
## Missing Windows 365 licenses
38+
39+
There are two primary methods to reassign Windows 365 licenses to users: group-based licensing and direct assignment.
40+
41+
### Group-based licensing
42+
43+
Group-based licensing allows administrators to assign licenses to users through Microsoft Entra ID groups. This method simplifies management by automating license assignment based on group membership. Follow these steps to manage group-based licensing:
44+
45+
1. Sign in to the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339) as at least a License Administrator.
46+
2. Go to the **Billing** > [Licenses](https://go.microsoft.com/fwlink/p/?linkid=842264) page.
47+
3. On the **Subscriptions** tab, select the Windows 365 license that you want to assign.
48+
4. On the **License details** page, select the **Groups** tab, and then select **Assign licenses**.
49+
5. In the details panel, search for the group that you want to assign licenses to, and then select the name from the **Suggested groups** list.
50+
6. To assign or remove access to specific items, select **Turn apps and services on or off**.
51+
7. When finished, select **Assign**, and then close the right pane.
52+
53+
### Direct assignment
54+
55+
Direct assignment involves manually assigning licenses to individual users. Follow these steps to manage direct assignment of licenses:
56+
57+
1. Sign in to the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339) as at least a License Administrator.
58+
2. Go to the **Billing** > [Licenses](https://go.microsoft.com/fwlink/p/?linkid=842264) page.
59+
3. On the **Subscriptions** tab, select the Windows 365 license that you want to assign.
60+
4. On the **License details** page, select the **Users** tab, and then select **Assign licenses**.
61+
5. In the **Assign licenses to users** pane, begin typing a name, and then choose it from the results to add it to the list. You can add up to 20 users at a time.
62+
6. To assign or remove access to specific items, select **Turn apps and services on or off**.
63+
7. When finished, select **Assign**, and then close the right pane.
64+
65+
## Disconnection from provisioning policies
66+
67+
If a user is disconnected from a provisioning policy, either by being removed from an assigned group or if the group they belong to is unassigned, any Cloud PCs created from that association enter a grace period. To resolve this issue, ensure that the correct assignments and group memberships are in place.
68+
69+
### Validate group membership
70+
71+
Provisioning policies in Windows 365 require users to be part of specific Microsoft Entra ID groups to receive their Cloud PCs. Ensure that users are members of these groups is crucial for proper provisioning.
72+
73+
To do so, follow these steps:
74+
75+
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then select **Groups** > **All groups**.
76+
2. Choose the relevant group associated with the provisioning policy.
77+
3. Select **Members**, and then select **Add members**.
78+
4. Add the users who require Cloud PCs to this group and select **Select**.
79+
80+
### Validate group assignment to provisioning policy
81+
82+
If a group is removed from a provisioning policy, all Cloud PCs associated with the members of the group enter the seven-day grace period. To resolve this issue, you need to reassign the group.
83+
84+
To do so, follow these steps:
85+
86+
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then select **Devices** > **Windows 365**.
87+
2. Navigate to **Provisioning policies** and open the provisioning policy the Cloud PCs in grace were created from.
88+
3. Under **Assignments**, select **Edit**.
89+
4. On the Assignments page, select **Add groups**, choose the groups you want this policy assigned to, and then select **Select**.
90+
91+
> [!NOTE]
92+
> Nested groups aren't currently supported.
93+
94+
5. Select **Next** and **Update**.
95+
96+
## Monitoring and verification
97+
98+
After reassigning licenses and ensuring group memberships, it's important to verify that the Cloud PCs are no longer in grace period, and users can access the virtual desktops.
99+
100+
To do so, follow these steps:
101+
102+
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then select **Devices** > **Windows 365**.
103+
2. Navigate to **All Cloud PCs** and check the status of the affected Cloud PCs.
104+
3. Ensure that the Cloud PCs are in the **Provisioned** status, and the users can sign in the Cloud PCs without issues.
105+
106+
## Ending grace period by deprovisioning Cloud PCs
107+
108+
If a Cloud PC is no longer needed, you can end the grace period, thus circumventing the seven-day period by immediately deprovisioning the device. This process involves removing the Cloud PC from your environment and releasing the associated resources.
109+
110+
> [!NOTE]
111+
> Deprovisioning a Cloud PC is a destructive act. The operation deletes the operating system and data, and the Cloud PC will no longer be available. This action is irreversible, so ensure that any necessary data is backed up before deprovisioning.
112+
113+
To do so, follow these steps:
114+
115+
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then select **Devices** > **Windows 365**.
116+
2. Navigate to **All Cloud PCs** and locate the Cloud PC that is in grace and no longer required.
117+
3. In the Status column of the list, select **In grace period** > **Deprovision now** > **Yes**.
118+
119+
For more information, see [End grace period for Cloud PCs in Windows 365 | Microsoft Learn](/windows-365/enterprise/end-grace-period).
120+
121+
## Conclusion
122+
123+
Addressing Windows 365 Cloud PCs in grace period requires prompt action to reassign licenses and ensure proper group memberships. By following this guide, administrators can efficiently manage their Windows 365 environment and avoid service disruptions. Continual monitoring and verification are essential to maintaining a seamless user experience.

0 commit comments

Comments
 (0)