Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 a Cloud PC. Resizing doesn't let you downsize disk space.
- Resize a single Cloud PC.
- Resize multiple Cloud PCs in bulk.
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 results 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.
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.
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.
Other requirements
In order to use Resize there must be available licenses in the 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.
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.
- Sign in to the windows365.microsoft.com, select Your organization's Cloud PCs > choose a device > Devices > Resize.
- 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.
- 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
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.