Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Premium SSD v2 is designed for I/O-intensive enterprise workloads that require submillisecond disk latency, high IOPS, and high throughput at a low cost. Premium SSD v2 is suited for workloads such as SQL Server, Oracle, MariaDB, SAP, Cassandra, MongoDB, big data and analytics, and gaming on virtual machines or stateful containers. For conceptual information on Premium SSD v2, see Premium SSD v2.
You can deploy Premium SSD v2 disks as zonal resources or as nonzonal resources. Use a zonal disk when your workload runs in an availability zone. Use a nonzonal disk for a nonzonal VM or in a region 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.
Premium SSD v2 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.
Regional availability
Zonal disks
Currently only available in the following regions:
| Three Availability Zones |
|---|
| Austria East Australia East Brazil South Canada Central Central India China North 3 East Asia North Europe, West Europe France Central Germany West Central Indonesia Central Israel Central Italy North Japan East, Japan West Korea Central Malaysia West Mexico Central New Zealand North Norway East Poland Central South African North Southeast Asia Spain Central Sweden Central Switzerland North UAE North UK South Central US, East US, East US 2, South Central US, West Central US, West US 2, West US 3 US Gov Virginia |
To learn when support for particular regions was added, see either Azure Updates or What's new for Azure Disk Storage.
Nonzonal disks
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
Because 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}"
After you identify a supported region and zone, choose the deployment type that matches your VM.
Deploy a zonal Premium SSD v2
Zonal Premium SSD v2 disks are available in select regions with availability zones.
Create a Premium SSD v2 in an availability zone by using the az disk create command. Then create a VM in the same region and availability zone 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 deploy one with a 512 sector size, update the $logicalSectorSize parameter. Replace the values of all the variables with your own, then run the following script:
## Initialize variables
diskName="yourDiskName"
resourceGroupName="yourResourceGroupName"
region="yourRegionName"
zone="yourZoneNumber"
##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 \
--zone $zone \
--sku PremiumV2_LRS \
--logical-sector-size $logicalSectorSize
## Create the VM
az vm create -n $vmName -g $resourceGroupName \
--image $vmImage \
--zone $zone \
--authentication-type password --admin-password $adminPassword --admin-username $adminUserName \
--size $vmSize \
--location $region \
--attach-data-disks $diskName
Deploy a nonzonal Premium SSD v2
Deploy a nonzonal disk for a nonzonal VM in a supported region, including regions with and without availability zones.
Additional limitations for nonzonal disks in regions with availability zones
When you attach a nonzonal Premium SSD v2 disk to a nonzonal VM in a region with availability zones, Azure runs a background copy to align the disk with the VM's availability zone and optimize latency. The copy can take up to 24 hours.
The following additional limitations apply during the background copy:
- You can't attach a nonzonal disk created from a snapshot, including an instant access snapshot, to a nonzonal VM until the copy finishes. To check the copy status, see Performance impact of background copy.
- You can't resize the disk or change its customer-managed key.
Only one background copy can run on a nonzonal disk at a time. While a background copy is in progress, attaching the disk to a running nonzonal VM might fail. Restarting a stopped or deallocated nonzonal VM with the disk attached might also fail because the restart can trigger a second background copy.
Create a nonzonal Premium SSD v2 disk by using the az disk create command. Then create a nonzonal VM in the same region that supports Premium Storage and attach the disk by using the az vm create command.
The following script creates a Premium SSD v2 disk with a 4k sector size. To create a disk with a 512E sector size, change the logicalSectorSize value to 512. Replace the variable values with your own before you run the script.
## Initialize variables
diskName="yourDiskName"
resourceGroupName="yourResourceGroupName"
region="yourRegionName"
logicalSectorSize=4096
vmName="yourVMName"
vmImage="Win2016Datacenter"
adminPassword="yourAdminPassword"
adminUserName="yourAdminUserName"
vmSize="Standard_D4s_v3"
## Create a Premium SSD v2 disk
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 and attach the disk
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
Adjust disk performance
You can adjust the performance of a Premium SSD v2 four times within a 24 hour period. Creating a disk counts as one of these times, so for the first 24 hours after creating a Premium SSD v2 you can only adjust its performance up to three times.
For conceptual information on adjusting disk performance, see Premium SSD v2 performance.
Use the az disk update command to change the performance configuration of your Premium SSD v2. For example, you can use the disk-iops-read-write parameter to adjust the max IOPS limit, and the disk-mbps-read-write parameter to adjust the max throughput limit of your Premium SSD v2.
The following command adjusts the performance of your disk. Update the values in the command, and then run it:
az disk update --subscription $subscription --resource-group $rgname --name $diskName --disk-iops-read-write=5000 --disk-mbps-read-write=200
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.