Skip to content

Commit 1f21510

Browse files
authored
Merge pull request #8238 from MicrosoftDocs/v-phoebh-patch-1
Post edit "troubleshoot-windows-365-enterprise-cloud-pcs-grace-period-issue.md"
2 parents 2e6e68b + 8ed5ab0 commit 1f21510

File tree

2 files changed

+36
-36
lines changed

2 files changed

+36
-36
lines changed

support/windows-365/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ 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
24+
- name: Troubleshoot Windows 365 Enterprise Cloud PC grace period issues
2525
href: ./troubleshoot-windows-365-enterprise-cloud-pcs-grace-period-issue.md
2626
- name: Windows 365 setup issues
2727
href: ./troubleshoot-windows-365-business.md
Lines changed: 35 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,92 +1,92 @@
11
---
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.
2+
title: Troubleshoot Windows 365 Enterprise Cloud PC Grace Period Issues
3+
description: Introduces how to troubleshoot Windows 365 Enterprise Cloud PCs that are in the grace period.
44
manager: dcscontentpm
5-
ms.date: 02/20/2025
5+
ms.date: 02/18/2025
66
ms.topic: troubleshooting
77
ms.reviewer: anwill
88
---
9-
# Troubleshoot Windows 365 Enterprise Cloud PCs grace period issue
9+
# Troubleshoot Windows 365 Enterprise Cloud PC grace period issues
1010

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.
11+
Windows 365 Cloud PCs provide a seamless and scalable solution for virtual desktops. However, administrators might encounter situations where a Cloud PC enters a grace period. This guide explains how to troubleshoot Cloud PC grace period issues.
1212

13-
## Understanding grace period
13+
## Understand the grace period
1414

1515
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.
1616

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:
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 the provisioning policy is broken. This can happen in one of the following scenarios:
1818

19-
- The user account is removed from the group where the license was inherited from.
19+
- The user account is removed from the group where the license is inherited.
2020
- 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.
21+
- The user is removed from the group that is assigned to the provisioning policy used to create the Cloud PC.
2222

2323
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.
2424

25-
## Actions to address grace period
25+
## Actions to address the grace period
2626

2727
To return Cloud PCs to a provisioned state, check the following two key areas:
2828

29-
1. Original license assignments are in place.
30-
2. Connection to the relevant provisioning policy is in place.
29+
1. The original license assignments are in place.
30+
2. The connection to the relevant provisioning policy is in place.
3131

32-
The following sections provide the necessary actions to address grace period. The sections include the following steps:
32+
The following sections provide the necessary actions to address the grace period. The sections include the following steps:
3333

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.
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 that the assignments are in place.
3636

3737
## Missing Windows 365 licenses
3838

3939
There are two primary methods to reassign Windows 365 licenses to users: group-based licensing and direct assignment.
4040

4141
### Group-based licensing
4242

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:
43+
Group-based licensing allows administrators to assign licenses to users through Microsoft Entra ID groups. This method simplifies management by automating license assignments based on group membership. Follow these steps to manage group-based licensing:
4444

4545
1. Sign in to the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339) as at least a License Administrator.
4646
2. Go to the **Billing** > [Licenses](https://go.microsoft.com/fwlink/p/?linkid=842264) page.
4747
3. On the **Subscriptions** tab, select the Windows 365 license that you want to assign.
4848
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.
49+
5. In the details panel, search for the group that you want to assign licenses to, and then select its name from the **Suggested groups** list.
5050
6. To assign or remove access to specific items, select **Turn apps and services on or off**.
5151
7. When finished, select **Assign**, and then close the right pane.
5252

5353
### Direct assignment
5454

55-
Direct assignment involves manually assigning licenses to individual users. Follow these steps to manage direct assignment of licenses:
55+
Direct assignment involves manually assigning licenses to individual users. Follow these steps to manage the direct assignment of licenses:
5656

5757
1. Sign in to the [Microsoft 365 admin center](https://go.microsoft.com/fwlink/p/?linkid=2024339) as at least a License Administrator.
5858
2. Go to the **Billing** > [Licenses](https://go.microsoft.com/fwlink/p/?linkid=842264) page.
5959
3. On the **Subscriptions** tab, select the Windows 365 license that you want to assign.
6060
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.
61+
5. In the **Assign licenses to users** pane, type 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.
6262
6. To assign or remove access to specific items, select **Turn apps and services on or off**.
6363
7. When finished, select **Assign**, and then close the right pane.
6464

6565
## Disconnection from provisioning policies
6666

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.
67+
If a user is disconnected from a provisioning policy, either by being removed from the 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.
6868

6969
### Validate group membership
7070

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.
71+
Provisioning policies in Windows 365 require users to be part of specific Microsoft Entra ID groups to receive their Cloud PCs. Ensuring that users are members of these groups is crucial for proper provisioning.
7272

7373
To do so, follow these steps:
7474

7575
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then select **Groups** > **All groups**.
7676
2. Choose the relevant group associated with the provisioning policy.
77-
3. Select **Members**, and then select **Add members**.
77+
3. Select **Members** > **Add members**.
7878
4. Add the users who require Cloud PCs to this group and select **Select**.
7979

80-
### Validate group assignment to provisioning policy
80+
### Validate group assignment to provisioning policies
8181

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.
82+
If a group is removed from a provisioning policy, all Cloud PCs associated with its members enter a seven-day grace period. To resolve this issue, you need to reassign the group.
8383

8484
To do so, follow these steps:
8585

8686
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.
87+
2. Navigate to **Provisioning policies** and open the provisioning policy the Cloud PCs in the grace period were created from.
8888
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**.
89+
4. On the **Assignments** page, select **Add groups**, choose the groups you want this policy assigned to, and then select **Select**.
9090

9191
> [!NOTE]
9292
> Nested groups aren't currently supported.
@@ -95,29 +95,29 @@ To do so, follow these steps:
9595

9696
## Monitoring and verification
9797

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.
98+
After reassigning licenses and ensuring group memberships, it's important to verify that the Cloud PCs are no longer in the grace period and that users can access the virtual desktops.
9999

100100
To do so, follow these steps:
101101

102102
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), and then select **Devices** > **Windows 365**.
103103
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.
104+
3. Ensure that the Cloud PCs are in the **Provisioned** status and that the users can sign in to the Cloud PCs without issues.
105105

106-
## Ending grace period by deprovisioning Cloud PCs
106+
## End the grace period by deprovisioning Cloud PCs
107107

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.
108+
If a Cloud PC is no longer needed, you can end the grace period, thus circumventing the seven-day grace period by immediately deprovisioning the device. This process involves removing the Cloud PC from your environment and releasing the associated resources.
109109

110110
> [!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.
111+
> Deprovisioning a Cloud PC is a destructive action. This 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.
112112
113113
To do so, follow these steps:
114114

115115
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**.
116+
2. Navigate to **All Cloud PCs** and locate the Cloud PC that is in a grace period and no longer required.
117+
3. In the **Status** column of the list, select **In grace period** > **Deprovision now** > **Yes**.
118118

119-
For more information, see [End grace period for Cloud PCs in Windows 365 | Microsoft Learn](/windows-365/enterprise/end-grace-period).
119+
For more information, see [End grace period for Cloud PCs in Windows 365](/windows-365/enterprise/end-grace-period).
120120

121121
## Conclusion
122122

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.
123+
Addressing issues with Windows 365 Cloud PCs in the 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)