Skip to content

Commit 3b50246

Browse files
authored
Merge pull request #214634 from roygara/standardResize
Standard resize
2 parents b745d90 + 42e54bd commit 3b50246

File tree

2 files changed

+26
-5
lines changed

2 files changed

+26
-5
lines changed

includes/virtual-machines-disks-expand-without-downtime-restrictions.md

Lines changed: 24 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,37 @@
55
author: roygara
66
ms.service: virtual-machines
77
ms.topic: include
8-
ms.date: 08/23/2022
8+
ms.date: 10/14/2022
99
ms.author: rogarana
1010
ms.custom: include file
1111
---
12+
- Only available with particular VM SKUs.
1213
- Only supported for data disks.
1314
- If a disk is 4 TiB or less, you can't expand it beyond 4 TiB without deallocating the VM. If a disk is already greater than 4 TiB, you can expand it without deallocating the VM.
14-
- Not supported for Ultra disks, Premium SSD v2 (preview) disks, or standard HDDs.
15+
- Not supported for Ultra disks or Premium SSD v2 disks.
1516
- Not supported for shared disks.
1617
- Install and use either:
1718
- The [latest Azure CLI](/cli/azure/install-azure-cli)
1819
- The [latest Azure PowerShell module](/powershell/azure/install-az-ps)
1920
- The [Azure portal](https://portal.azure.com/)
20-
- Or an Azure Resource Manager template with an API version that's 2021-04-01 or newer.
21+
- Or an Azure Resource Manager template with an API version that's `2021-04-01` or newer.
22+
23+
Use the following PowerShell script to determine which VM SKUs it's available with:
24+
25+
```azurepowershell
26+
Connect-AzAccount
27+
$subscriptionId="yourSubID"
28+
$location="desiredRegion"
29+
Set-AzContext -Subscription $subscriptionId
30+
$vmSizes=Get-AzComputeResourceSku -Location $location | where{$_.ResourceType -eq 'virtualMachines'}
31+
32+
foreach($vmSize in $vmSizes){
33+
foreach($capability in $vmSize.Capabilities)
34+
{
35+
if(($capability.Name -eq "EphemeralOSDiskSupported" -and $capability.Value -eq "True") -or ($capability.Name -eq "PremiumIO" -and $capability.Value -eq "True") -or ($capability.Name -eq "HyperVGenerations" -and $capability.Value -match "V2"))
36+
{
37+
$vmSize.Name
38+
}
39+
}
40+
}
41+
```

includes/virtual-machines-disks-shared-sizes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@
55
author: roygara
66
ms.service: virtual-machines
77
ms.topic: include
8-
ms.date: 07/19/2022
8+
ms.date: 10/14/2022
99
ms.author: rogarana
1010
ms.custom: include file
1111
---
1212

13-
For now, only ultra disks, premium SSD v2 (preview), premium SSD, and standard SSDs can enable shared disks. Different disk sizes may have a different `maxShares` limit, which you can't exceed when setting the `maxShares` value.
13+
For now, only ultra disks, premium SSD v2, premium SSD, and standard SSDs can enable shared disks. Different disk sizes may have a different `maxShares` limit, which you can't exceed when setting the `maxShares` value.
1414

1515
For each disk, you can define a `maxShares` value that represents the maximum number of nodes that can simultaneously share the disk. For example, if you plan to set up a 2-node failover cluster, you would set `maxShares=2`. The maximum value is an upper bound. Nodes can join or leave the cluster (mount or unmount the disk) as long as the number of nodes is lower than the specified `maxShares` value.
1616

0 commit comments

Comments
 (0)