Note
Access to this page requires authorization. You can try signing in or .
Access to this page requires authorization. You can try .
Deploy a nonzonal Premium SSD v2
Azure Premium SSD v2 is designed for I/O-intense enterprise workloads that require sub-millisecond disk latencies and high IOPS and throughput at a low cost. For conceptual information on Premium SSD v2, see Premium SSD v2.
You can deploy Premium SSD v2 nonzonal disks in select regions, including regions with and without availability zones.
Premium SSD v2 disks support a 4k physical sector size by default, but you can configure them to use a 512E sector size. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later to support 4k native disks.
Limitations
- Premium SSD v2 disks can't be used as an OS disk or with Azure Compute Gallery.
- Premium SSD v2 doesn't support host caching.
- In most regions that support availability zones, you can only attach Premium SSD v2 disks to zonal VMs. When you create a new VM, specify the availability zone you want before adding Premium SSD v2 disks to your configuration.
- In a subset of regions that support availability zones, you can attach nonzonal Premium SSD v2 disks to nonzonal VMs, which have extra limitations.
Limitations for nonzonal Premium SSD v2 in regions with availability zones
When you attach a nonzonal Premium SSD v2 to a nonzonal VM in an AZ region, Azure runs a background copy (can take up to 24 hours) to align the disk with the VM's availability zone and optimize latency.
The following additional limitations apply to nonzonal Premium SSD v2 disks:
- You can't attach a nonzonal disk created from a snapshot, including an instant access snapshot, to a nonzonal VM until the snapshot's background copy finishes. To check the snapshot's background copy status, see Check snapshot status.
- You can't resize the nonzonal disk or change customer-managed key during a background copy.
Only one background copy can run on a nonzonal disk at a time. While a background copy is in progress, attaching the nonzonal disk to a running nonzonal VM might fail. Restarting a stopped or deallocated nonzonal VM with the nonzonal disk attached might also fail, because the restart can trigger a second background copy.
Regional availability
Currently, Azure supports nonzonal Premium SSD v2 deployments in the following regions:
| Regions without Availability Zone | Three Availability Zones |
|---|---|
| - Australia Central 2 - Australia Southeast - Brazil Southeast - Canada East - Germany North - North Central US - Norway West - South India - Switzerland West - Taiwan North - UK West - US Gov Arizona - West Central US - West US |
- Australia East - Brazil South - East Asia - France Central - Germany West Central - Italy North - Korea Central - Mexico Central - New Zealand North - Norway East - Poland Central - Spain Central - South African North - Southeast Asia - Sweden Central - Switzerland North |
To learn when support for particular regions was added, see either Azure Updates or What's new for Azure Disk Storage.
Prerequisites
- Install either the latest Azure CLI or the latest Azure PowerShell module.
Determine region availability programmatically
Since not every region and zone supports Premium SSD v2 disks, use the Azure CLI or PowerShell to check region and zone support.
To find the regions and zones that support Premium SSD v2 disks, replace yourSubscriptionId with your subscription, and then run the az vm list-skus command:
az login
subscriptionId="<yourSubscriptionId>"
az account set --subscription $subscriptionId
az vm list-skus --resource-type disks --query "[?name=='PremiumV2_LRS'].{Region:locationInfo[0].location, Zones:locationInfo[0].zones}"
Now that you know the region and zone to deploy to, follow the deployment steps in this article to create a nonzonal Premium SSD v2 and attach it to a VM.
To deploy a zonal Premium SSD v2 instead, see Deploy a Premium SSD v2 managed disk.
Use a nonzonal Premium SSD v2
Create a nonzonal Premium SSD v2 by using the az disk create command. Then create a nonzonal VM in the same region that supports Premium Storage and attach the disk to it by using the az vm create command.
The following script creates a Premium SSD v2 with a 4k sector size. To create a disk with a 512 sector size, update the $logicalSectorSize parameter. Replace the values of all the variables with your own, and then run the following script:
## Initialize variables
diskName="yourDiskName"
resourceGroupName="yourResourceGroupName"
region="yourRegionName"
##Replace 4096 with 512 to deploy a disk with 512 sector size
logicalSectorSize=4096
vmName="yourVMName"
vmImage="Win2016Datacenter"
adminPassword="yourAdminPassword"
adminUserName="yourAdminUserName"
vmSize="Standard_D4s_v3"
## Create a Premium SSD v2
az disk create -n $diskName -g $resourceGroupName \
--size-gb 100 \
--disk-iops-read-write 5000 \
--disk-mbps-read-write 150 \
--location $region \
--sku PremiumV2_LRS \
--logical-sector-size $logicalSectorSize
## Create the VM
az vm create -n $vmName -g $resourceGroupName \
--image $vmImage \
--authentication-type password --admin-password $adminPassword --admin-username $adminUserName \
--size $vmSize \
--location $region \
--attach-data-disks $diskName
Next steps
Add a data disk by using either the Azure portal, Azure CLI, or PowerShell.
Use Premium SSD v2 with VMs in availability set.
Provide feedback on Premium SSD v2.
Feedback
Was this page helpful?
