Windows 365: resize without rebuilding your Cloud PC

Content reviewed: 5 November 2026

A user needs more memory for an accounting application. They have their own settings, several locally installed tools and documents in progress. The admin interface offers resizing, restoring and reprovisioning. Confusing those actions can turn a routine performance upgrade into a rebuild of the entire working environment.

Use Resize to change the supported resources of an existing Cloud PC. It preserves user and disk data, but it cannot save unsaved work in a disconnected session. Reinstallation and Reprovision serve a different purpose and have a different impact. The Windows 365 resizing overview explains the supported changes and licensing process.

This guide distinguishes Windows 365 Enterprise from the documented procedure for directly licensed Windows 365 Business. Edition migrations, GPU devices and shared modes are not simply variations of the same instructions.

Resize, Restore and Reprovision produce different outcomes

Microsoft explicitly describes Reprovision as wiping and rebuilding. The Restore and Reset documentation warns that restoring loses newer changes and resetting removes data. Do not choose these actions simply because Resize is temporarily unavailable.

Write down the required outcome in one sentence first. 'Increase memory and keep applications' is a different task from 'deploy a new base image'. If a new image is genuinely required, plan data transfer and application recovery. Resizing will not meet that requirement.

You can grow the disk, but cannot shrink it with Resize

Resize supports increasing or decreasing CPU and RAM within supported configurations, but storage can only increase. Even an almost empty disk does not make a smaller disk size selectable. GPU Cloud PCs do not support Resize. Check the scope of supported changes before buying the target configuration.

This matters when cutting costs after a project ends. Consider a Cloud PC with a 256 GB disk that uses only 70 GB. Lower utilisation does not make a resize to 128 GB supported. If a smaller disk is essential, plan a move to a new environment with verified data transfer rather than treating it as a routine downgrade of this device.

Record two sizes in the decision: allocated disk size and actual used space. The first determines the action's restriction; the second helps plan a transfer and establish whether a smaller destination disk is sensible. Confusing these figures is a common cause of an unsuitable purchase.

Windows 365 Business supports resizing too

Older discussions and guides can suggest that Business always requires a new computer. Current documentation describes Resize for this edition as well. For a single directly licensed device, Microsoft documents selecting the user, then Devices and Resize in the Microsoft 365 admin centre. Available targets depend on unallocated licences in inventory. Follow the Windows 365 Business procedure rather than importing Enterprise instructions without checking the edition.

During this operation, the service removes the original licence and assigns the target licence itself. Microsoft warns against manually assigning the target licence and accidentally creating another Cloud PC. A greyed-out action can be caused by the original subscription entering a warning state after expiry. Restore an active licensing state before retrying. The guidance for an unavailable Resize action supplements the procedure.

For Business, this article recommends the documented process for a single directly licensed device. The group-based licensing steps below apply to Enterprise; similarly named controls do not confirm identical support across editions.

Enterprise: direct and group-based licences need different handling

For a directly assigned licence, the service handles licence reassignment during Resize. With group-based assignment, you must complete the transition between the source and target licence. Operational risk is especially apparent when the same group controls both licensing and provisioning-policy targeting.

Microsoft recommends separating those groups. A configuration change then need not remove the user from the policy targeting that provides their Cloud PC. The single Enterprise device requirements also describe the necessary permissions and Provisioned state.

What Resize pending license means

For a group-licensed device, first initiate Resize and confirm Resize pending license. Only then change licensing-group membership. Microsoft's group-based licensing procedure warns that membership changes before this state can cause unwanted provisioning of another computer or entitlement problems.

The current overview requires both removal of the original licence and assignment of the target licence before resizing starts. The order of those two licensing changes does not matter, but both must actually complete. The pending state lasts 48 hours. If you remove the source and do not assign the target in time, the device enters a grace period. Pending-state behaviour is therefore not a reason to troubleshoot a delay by randomly assigning products again and again.

We recommend recording the original SKU, target SKU, assignment source and times of both changes in the change log. For groups, inspect the user's actual effective licences, not just whether you removed them from one group. If the same licence arrives through another assignment path, the intended state may not yet exist.

First establish whether performance is really the problem

A larger Cloud PC will not fix every delay. Before ordering, measure the application's opening time, CPU, memory and disk utilisation, and remote-connection behaviour in the actual work scenario. If only a network application is slow while local work behaves normally, check its server and connectivity before increasing memory for an entire group.

This recommended check is not a licensing condition. It gives the change a measurable target. After resizing, repeat the same task using the same document and account. Without a comparable test, 'it feels better now' is weak evidence that the additional monthly cost was worthwhile.

An inventory model for twelve Cloud PCs

The following inventory is our own hypothetical example. It is not a set of supported SKU combinations or a commercial offer; verify the actual targets against the tenant's available inventory.

Of twelve requests, eight can therefore proceed to resize preparation, two need a decision about the smaller disk and two need subscription repair. Immediately 'relicensing' all twelve would hide three different causes and make recovery harder.

How many changes to run concurrently

An Enterprise Cloud PC using hybrid join and your own network needs a second available subnet IP address for resizing. Microsoft allows operations to be staggered according to address availability. Do not automatically apply this condition to every Windows 365 network model. The resize networking prerequisites are scenario-specific.

If the eight Enterprise devices in our example all use that network model and the subnet has only three free addresses, this condition alone permits at most three concurrent operations. For our own operational headroom, we would choose two at a time and leave one address free. That produces four waves of two devices.

This is a scheduling proposal for the assumed inputs, not a service limit. If other processes consume the spare addresses in the meantime, recalculate the plan. Before each subsequent wave, confirm that the previous one has completed and check the current network headroom.

What to check before and after the change

Microsoft gives an indicative 15–20 minutes of unavailability during resizing. That is not a guaranteed maintenance window; allow separately for licence and group checks and subsequent acceptance. The Business procedure and Enterprise overview both warn about disconnection and potential loss of unsaved work.

Before intervening, also establish which data is genuinely synchronised. A document in Downloads or a local application database may not use the same mechanism as work documents in OneDrive. Microsoft recommends keeping user data independent of the device, for example through OneDrive known folders; the extent of application-settings synchronisation varies.

Even verified synchronisation is not a reason to substitute Reprovision for Resize. For a possible recovery, you need to know what can be recovered and to which point in time. A smaller disk, a restored system state and a performance change are separate decisions.

If your question is how many people need a Cloud PC simultaneously rather than performance, our Windows 365 Flex concurrency licensing guide covers that topic. For a resize assessment, instead prepare an inventory of specific devices, disks, licences and required target configurations.