Skip to content

Commit 941f524

Browse files
authored
Update resize-vm.md
Acrolinx updates (mostly "isn't")
1 parent 5ea435a commit 941f524

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/virtual-machines/resize-vm.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: devx-track-azurepowershell
1616

1717
This article shows you how to move a VM to a different [VM size](sizes.md).
1818

19-
After you create a virtual machine (VM), you can scale the VM up or down by changing the VM size. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM.
19+
After you create a virtual machine (VM), you can scale the VM up or down by changing the VM size. In some cases, you must deallocate the VM first. This can happen if the new size isn't available on the hardware cluster that is currently hosting the VM.
2020

2121
If your VM uses Premium Storage, make sure that you choose an **s** version of the size to get Premium Storage support. For example, choose Standard_E4**s**_v3 instead of Standard_E4_v3.
2222

@@ -63,7 +63,7 @@ To resize a VM, you need the latest [Azure CLI](/cli/azure/install-az-cli2) inst
6363
6464
The VM restarts during this process. After the restart, your existing OS and data disks are kept. Anything on the temporary disk is lost.
6565
66-
3. If the desired VM size is not listed, you need to first deallocate the VM with [az vm deallocate](/cli/azure/vm). This process allows the VM to then be resized to any size available that the region supports and then started. The following steps deallocate, resize, and then start the VM named `myVM` in the resource group named `myResourceGroup`:
66+
3. If the desired VM size isn't listed, you need to first deallocate the VM with [az vm deallocate](/cli/azure/vm). This process allows the VM to then be resized to any size available that the region supports and then started. The following steps deallocate, resize, and then start the VM named `myVM` in the resource group named `myResourceGroup`:
6767
6868
```azurecli-interactive
6969
# Variables will make this easier. Replace the values with your own.
@@ -105,15 +105,15 @@ List the VM sizes that are available in the region where the VM is hosted.
105105
Get-AzVMSize -ResourceGroupName $resourceGroup -VMName $vmName
106106
```
107107

108-
If the size you want is listed, run the following commands to resize the VM. If the desired size is not listed, go on to step 3.
108+
If the size you want is listed, run the following commands to resize the VM. If the desired size isn't listed, go on to step 3.
109109

110110
```azurepowershell-interactive
111111
$vm = Get-AzVM -ResourceGroupName $resourceGroup -VMName $vmName
112112
$vm.HardwareProfile.VmSize = "<newVMsize>"
113113
Update-AzVM -VM $vm -ResourceGroupName $resourceGroup
114114
```
115115

116-
If the size you want is not listed, run the following commands to deallocate the VM, resize it, and restart the VM. Replace **\<newVMsize>** with the size you want.
116+
If the size you want isn't listed, run the following commands to deallocate the VM, resize it, and restart the VM. Replace **\<newVMsize>** with the size you want.
117117

118118
```azurepowershell-interactive
119119
Stop-AzVM -ResourceGroupName $resourceGroup -Name $vmName -Force
@@ -131,7 +131,7 @@ Start-AzVM -ResourceGroupName $resourceGroup -Name $vmName
131131

132132
**Use PowerShell to resize a VM in an availability set**
133133

134-
If the new size for a VM in an availability set is not available on the hardware cluster currently hosting the VM, then all VMs in the availability set will need to be deallocated to resize the VM. You also might need to update the size of other VMs in the availability set after one VM has been resized. To resize a VM in an availability set, perform the following steps.
134+
If the new size for a VM in an availability set isn't available on the hardware cluster currently hosting the VM, then all VMs in the availability set will need to be deallocated to resize the VM. You also might need to update the size of other VMs in the availability set after one VM has been resized. To resize a VM in an availability set, perform the following steps.
135135

136136
```azurepowershell-interactive
137137
$resourceGroup = "myResourceGroup"
@@ -146,7 +146,7 @@ Get-AzVMSize `
146146
-VMName $vmName
147147
```
148148

149-
If the desired size is listed, run the following commands to resize the VM. If it is not listed, go to the next section.
149+
If the desired size is listed, run the following commands to resize the VM. If it isn't listed, go to the next section.
150150

151151
```azurepowershell-interactive
152152
$vm = Get-AzVM `
@@ -158,7 +158,7 @@ Update-AzVM `
158158
-ResourceGroupName $resourceGroup
159159
```
160160

161-
If the size you want is not listed, continue with the following steps to deallocate all VMs in the availability set, resize VMs, and restart them.
161+
If the size you want isn't listed, continue with the following steps to deallocate all VMs in the availability set, resize VMs, and restart them.
162162

163163
Stop all VMs in the availability set.
164164

@@ -193,11 +193,11 @@ The only combinations allowed for resizing are:
193193
- VM (with local temp disk) -> VM (with local temp disk); and
194194
- VM (with no local temp disk) -> VM (with no local temp disk).
195195

196-
If interested in a work around, please see [How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?](azure-vms-no-temp-disk.yml#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---)
196+
If interested in a work-around, see [How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?](azure-vms-no-temp-disk.yml#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---)
197197

198198

199199

200200

201201
## Next steps
202202

203-
For additional scalability, run multiple VM instances and scale out. For more information, see [Automatically scale machines in a Virtual Machine Scale Set](../virtual-machine-scale-sets/tutorial-autoscale-powershell.md).
203+
For more scalability, run multiple VM instances and scale out. For more information, see [Automatically scale machines in a Virtual Machine Scale Set](../virtual-machine-scale-sets/tutorial-autoscale-powershell.md).

0 commit comments

Comments
 (0)