Merge pull request #16207 from ErikjeMS/bizresize

Stacyrch140 · web-flow · commit ed7416a01c58 · 2024-10-02T19:31:04.000-04:00
53474119 resize biz
diff --git a/windows-365/business/media/resize-cloud-pc/resize-cloud-pc.png b/windows-365/business/media/resize-cloud-pc/resize-cloud-pc.png
diff --git a/windows-365/business/media/resize-cloud-pc/resize-options.png b/windows-365/business/media/resize-cloud-pc/resize-options.png
diff --git a/windows-365/business/resize-cloud-pc.md b/windows-365/business/resize-cloud-pc.md
@@ -0,0 +1,75 @@
+---
+# required metadata
+title: Resize a Windows 365 Business Cloud PC
+titleSuffix:
+description: Learn how to resize a Windows 365 Business Cloud PC.
+keywords:
+author: ErikjeMS  
+ms.author: erikje
+manager: dougeby
+ms.date: 10/01/2024
+ms.topic: how-to
+ms.service: windows-365
+ms.subservice: 
+ms.localizationpriority: high
+ms.assetid: 
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+
+ms.reviewer: lrayasam
+ms.suite: ems
+search.appverid: MET150
+#ms.tgt_pltfrm:
+ms.custom: intune-azure; get-started
+ms.collection:
+- M365-identity-device-management
+- tier2
+---
+
+# Resize a Windows 365 Business Cloud PC
+
+[!INCLUDE [Resize a Cloud PC intro](../includes/resize-introduction.md)]
+
+## Requirements
+
+### Role requirements
+
+To resize a Cloud PC, the admin must have certain built-in Microsoft Entra roles.
+
+For a Cloud PC provisioned with a direct assigned license, at least one of the following roles:
+
+- Windows 365 Administrator
+
+Alternatively, you can assign a custom role that includes the permissions of this built-in role.
+
+[!INCLUDE [Resize a Cloud PC IP requirements](../includes/resize-ip-address-requirements.md)]
+
+[!INCLUDE [Resize a Cloud PC other requirements](../includes/resize-other-requirements.md)]
+
+## Resize a Windows 365 Cloud PC
+
+When resizing Windows 365 Cloud PCs, the Windows 365 service automatically takes care of: 
+
+- Unassigning the original license.
+- Assigning the new license on behalf of the admin.
+
+1. Sign in to the windows365.microsoft.com, select **Your organization's Cloud PCs** > choose a device > **Devices** > **Resize**.
+![Screenshot of resize Cloud PC](./media/resize-cloud-pc/resize-cloud-pc.png)
+2. Under **Resize**, there's a list of the sizes that you can upgrade or downsize to based on the licenses available in your inventory. You can upgrade a Cloud PC’s **Processor** and **RAM**. **Storage** can only be upgraded. Select one of the available options.
+![Screenshot of resize options](./media/resize-cloud-pc/resize-options.png)
+3. Select **Resize**.
+
+If there are available licenses, the resizing starts.
+
+If there are no licenses available, then you can purchase a new license at the Windows 365 Market place. The newly purchased license will be available for upgrade soon.  
+
+## Resizing details
+
+[!INCLUDE [Resize a Cloud PC details](../includes/resize-details.md)]
+
+## Next steps
+
+[Remotely manage Windows 365 Business Cloud PCs](remotely-manage-business-cloud-pcs.md).
diff --git a/windows-365/enterprise/resize-cloud-pc.md b/windows-365/enterprise/resize-cloud-pc.md
@@ -65,7 +65,7 @@ Downsizing may impact support for nested virtualization. For more information, s
 To resize a Cloud PC, the admin must have certain built-in Microsoft Entra roles.
 
 - For a Cloud PC provisioned with a direct assigned license, at least one of the following roles
-    - Intune Service Administrator
+  - Intune Service Administrator
   - Intune Reader + Cloud PC Admin roles
   - Intune Reader + Windows 365 Administrator
 - For a Cloud PC provisioned with a group-based license, at least one of the following roles
@@ -102,7 +102,7 @@ When resizing Cloud PCs provisioned through direct assigned licenses the Windows
 - Assigning the new license on behalf of the admin.
 
 1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **All Devices** > choose a device > **Resize**.
-![Screenshot of resize a Cloud PC](./media/resize-cloud-pc/resize.png)
+![Screenshot of resize a Cloud PC.](./media/resize-cloud-pc/resize.png)
 2. Under **Resize**, there's a list of the sizes that you can upgrade or downsize to based on the licenses available in your inventory. You can upgrade/downgrade a Cloud PC’s RAM and vCPU. You can only upgrade the OS disk storage. If you're downgrading a user’s Cloud PC, options with lower storage are grayed out. Select one of the available options.
 3. Select **Resize**.
 
@@ -113,13 +113,13 @@ If there are available licenses, the resizing starts.
 1. Create a new target Microsoft Entra group. Add the users from the source Microsoft Entra group that you want to resize. Alternately, you can use existing Microsoft Entra groups if you're mapping the groups to individual Windows 365 license types.
 2. Assign the existing provisioning policy targeting the original source Microsoft Entra group to the new target Microsoft Entra group. You only need to do this step if you don't have a discrete Microsoft Entra group for your provisioning policy assignment. If you have discrete Microsoft Entra groups to manage your provisioning policy assignments, you can omit this step.
 3. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **All Devices** > choose the device that you want added to the Microsoft Entra target group > **Resize**.
-![Screenshot of resize a Cloud PC](./media/resize-cloud-pc/resize.png)
+![Screenshot of resize a Cloud PC.](./media/resize-cloud-pc/resize.png)
 4. A list is displayed with all the possible SKUs that you can upgrade or downsize to based on the licenses that you have available in your inventory. You can upgrade/downgrade a Cloud PC’s RAM and vCPU. You can only upgrade the OS disk storage. If you're downsizing a user’s Cloud PC, options with lower storage are grayed out. Select one of the available options.
 5. Select **Resize**.
 6. The user’s Cloud PC is placed in the **Resize pending license** state as can be seen in the Windows 365 provisioning blade.
 7. Select **Users** > search for the user name assigned to the Cloud PC and select it > **Groups**.
 8. To retrieve the old license, remove the users from the original source Microsoft Entra group. If you don’t perform this step, a new Cloud PC will be provisioned with the original source license after you assign the target license.
-    - When using Microsoft Entra ID hybrid in your environment, after removing the user from the original group, you must wait until Microsoft Entra Connect synchronizes  your on-premises Active Directory with with your Microsoft Entra ID. This can take up to 30 minutes. Then you can add the user to the new group.
+    - When using Microsoft Entra ID hybrid in your environment, after removing the user from the original group, you must wait until Microsoft Entra Connect synchronizes  your on-premises Active Directory with your Microsoft Entra ID. This can take up to 30 minutes. Then you can add the user to the new group.
 9. Assign the target license to the new target Microsoft Entra group. The resizing process now begins.
 
 ## Bulk resizing Cloud PCs
@@ -159,7 +159,7 @@ Up to 5,000 Cloud PCs can be resized at a time.
 7. Under **Select groups to include**, choose the groups containing the users who own the devices that you want to resize > **Next**.
 8. On the **Review + create** page, select **Create**. The user’s Cloud PC is placed in the **Resize pending license** state as can be seen in the Windows 365 provisioning blade.
 9. To retrieve the old license, remove the users from the original source Microsoft Entra group. If you don’t perform this step, a new Cloud PC will be provisioned with the original source license after you assign the target license.
-    - When using Microsoft Entra ID hybrid in your environment, after removing the user from the original group, you must wait until Microsoft Entra Connect synchronizes  your on-premises Active Directory with with your Microsoft Entra ID. This can take up to 30 minutes. Then you can add the user to the new group.
+    - When using Microsoft Entra ID hybrid in your environment, after removing the user from the original group, you must wait until Microsoft Entra Connect synchronizes  your on-premises Active Directory with your Microsoft Entra ID. This can take up to 30 minutes. Then you can add the user to the new group.
 10. Assign the target license to the new target Microsoft Entra group. The resizing process now begins.
 
 ## Resizing details
@@ -172,12 +172,12 @@ If the source license isn't removed first, and the new license is assigned to th
 
 If the source license isn't removed, and the target license isn't assigned within 48 hours, the device returns to the **Provisioned** state.
 
+If you have a combination of paid and trial licenses, the resize feature uses your paid licenses first. After these licenses run out, the resize operation uses your trial licenses.
+
 When resizing starts, the user is automatically disconnected from their Cloud PC and any unsaved work might be lost.
 
 Resizing can take from 15 to 20 minutes before the user can access their Cloud PC again. You can monitor the status in the Windows 365 provisioning blade. Users can see their Cloud PC status at https://windows365.microsoft.com.
 
-If you have a combination of paid and trial licenses, the resize feature uses your paid licenses first. After these licenses run out, the resize operation uses your trial licenses.
-
 If there are no licenses in your inventory, the resizing fails. To request more licenses, contact your procurement admin. After you purchase the license and added to the inventory in the Microsoft 365 admin center, you can retry the resize operation. Licenses can be purchased from various channels: EA, CSP, MCA, and Web Direct.
 
 Devices with a state of **Resize not supported** aren't resized. The status message and details can help you identify the issue. You can still proceed with a bulk resize even if you have devices in the list that are marked as **Resize not supported**.
diff --git a/windows-365/includes/resize-details.md b/windows-365/includes/resize-details.md
@@ -0,0 +1,18 @@
+---
+title: include file
+description: include file
+author: ErikjeMS  
+ms.service: windows-365
+ms.topic: include
+ms.date: 09/25/2024
+ms.author: erikje
+ms.custom: include file
+---
+
+When resizing starts, the user is automatically disconnected from their Cloud PC and any unsaved work might be lost.
+
+Resizing can take from 15 to 20 minutes before the user can access their Cloud PC again. You can monitor the status in the Windows 365 provisioning blade. Users can see their Cloud PC status at https://windows365.microsoft.com.
+
+If there are no licenses in your inventory, the resizing fails. To request more licenses, contact your procurement admin. After you purchase the license and added to the inventory in the Microsoft 365 admin center, you can retry the resize operation. Licenses can be purchased from various channels: EA, CSP, MCA, and Web Direct.
+
+Devices with a state of **Resize not supported** aren't resized. The status message and details can help you identify the issue. You can still proceed with a bulk resize even if you have devices in the list that are marked as **Resize not supported**.
diff --git a/windows-365/includes/resize-introduction.md b/windows-365/includes/resize-introduction.md
@@ -0,0 +1,35 @@
+---
+title: include file
+description: include file
+author: ErikjeMS  
+ms.service: windows-365
+ms.topic: include
+ms.date: 09/25/2024
+ms.author: erikje
+ms.custom: include file
+---
+
+The **Resize** remote action, which preserves user and disk data, lets you:
+
+- Upgrade the RAM, CPU, and storage size of a Cloud PC.
+- Downgrade the RAM and CPU of Cloud PC. Resizing doesn't let you downsize disk space.
+
+These operations don't require reprovisioning of the Cloud PC.
+
+You might consider resizing a Cloud PC when a user needs:
+
+- Higher RAM and VCPU cores to run CPU intensive applications.
+- More disk space for file storing.
+- Less RAM and vCPU cores to run their current workload applications.
+
+Resizing supports:
+
+- Direct and group-based licenses.
+- Paid, preview, and trial licenses.
+- Bulk and single device operations.
+
+Resizing doesn't support:
+
+- GPU Cloud PCs. GPU Cloud PCs might show up in the resize flow, but trying to resize a GPU Cloud PC will result in an error.
+
+Resizing automatically disconnects the user from their session and any unsaved work might be lost. Therefore, it's best to coordinate any resizing with the user before you begin. Contact your end users and have them save their work and sign out before you begin resizing.
diff --git a/windows-365/includes/resize-ip-address-requirements.md b/windows-365/includes/resize-ip-address-requirements.md
@@ -0,0 +1,23 @@
+---
+title: include file
+description: include file
+author: ErikjeMS  
+ms.service: windows-365
+ms.topic: include
+ms.date: 09/25/2024
+ms.author: erikje
+ms.custom: include file
+---
+
+## IP address requirements
+
+When you resize a Microsoft Entra hybrid join bring-your-own-network Cloud PC, a second IP address must be available in the subnet for the Cloud PC to be resized.
+
+During the resizing operation, a second IP address is used when moving to the new size. This precaution makes sure that the Cloud PC can be rolled back to the original should an issue occur.
+
+To account for this precaution, you can:
+
+- Make sure that adequate IP addresses are available in the vNET for all Cloud PCs to be resized, or
+- Stagger your resize operations to make sure that the address scope is maintained.
+
+If inadequate addresses are available, resize failures can occur.
diff --git a/windows-365/includes/resize-other-requirements.md b/windows-365/includes/resize-other-requirements.md
@@ -0,0 +1,16 @@
+---
+title: include file
+description: include file
+author: ErikjeMS  
+ms.service: windows-365
+ms.topic: include
+ms.date: 09/25/2024
+ms.author: erikje
+ms.custom: include file
+---
+
+### Other requirements
+
+In order to use **Resize** there must be available licenses in inventory for the resized Cloud PC configuration.
+
+To **Resize** a Cloud PC, it must have a status of **Provisioned** in the Windows 365 provisioning node.
