Move to a larger size
Open the VM’s settings and select Resize. Review the available sizes and confirm the change when you are ready for an interruption. Resizing stops and restarts the VM; completion time depends on the operation and application startup. Before resizing, verify a suitable backup and identify any application steps needed after restart. Check the final size, status and application behavior once the operation completes.Move to a smaller size
The existing allocated disk size, not just the amount of data stored on it, constrains a downgrade. The disk cannot shrink through the resize operation. Choose an available size that accommodates the existing disk. If the desired size has a smaller disk, a snapshot does not automatically solve that constraint: snapshot restoration also requires a compatible target disk. Moving to a smaller disk requires a separately planned application/data transfer and validation before deleting the original VM.Billing considerations
Each size has its own listed compute rate. A completed resize records a rate change for that VM; earlier usage retains the rate applicable to that period. Review the selected size and your usage history after a change, and contact support if a charge does not match the operation. The monthly figures on the pricing page are estimates based on 730 hours, not subscription fees or spending caps. Stopping a VM does not save compute charges. The VM remains allocated and billable while stopped. Delete resources you no longer need only after preserving the required data; retained snapshots and volumes have separate charges.Next
Resize details
Operational steps and disk constraints.
VM pricing
Per-size rates and additional resource charges.