Using Blob Service Operations with Azure Premium Storage

Azure Premium Storage offers a world-class cloud storage solution for Azure Virtual Machine workloads requiring high performance and low latency. To learn more about Azure Premium Storage, see Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads.

Premium Storage disks are backed by page blobs in Azure Storage. This topic provides information about performing REST operations against page blobs in Premium Storage accounts using the Azure Storage Services REST API.

To create and manage Resource Manager Premium storage accounts, please see the Storage Resource Provider REST API reference. To create and manage classic Premium storage accounts, please see the Service Management REST API reference

You can also access page blobs in Premium Storage via the Azure Storage Client Library for .NET.

Premium Storage Accounts Support Page Blobs Only

Premium Storage Accounts currently support only Azure Virtual Machine disks backed by page blobs. A premium storage account stores only page blobs, and only REST APIs for page blobs and their containers are supported. Any API called on a Premium Storage account must be of version 2014-02-14 or later. Premium Block blobs can be created in BlockBlobStorage accounts.


Azure block blobs and the File, Table, and Queue services are not currently supported in premium storage accounts. However, Premium BlockBlobStorage accounts do support block and append blobs. For more information and to see all the various storage options in a table, visit Types of storage accounts

A premium storage account endpoint cannot be mapped to a custom domain name.

REST API Restrictions on Premium Storage

There are certain restrictions to bear in mind when using the Blob service REST API against a Premium Storage account:

  • Only REST operations using version 2014-02-14 and later are supported for Premium Storage. See Versioning for the Azure Storage Services for details.

  • The number of snapshots per page blob in a Premium Storage account is limited to 100. If that limit is exceeded, the Snapshot Blob operation returns error code 409 (SnapshotCountExceeded).

  • A snapshot of a page blob in a Premium Storage account may be taken once every ten minutes. If that rate is exceeded, the Snapshot Blob operation returns error code 409 (SnaphotOperationRateExceeded).

  • Public access to a container containing page blobs in Premium Storage is not permitted. Calling Set Container ACL with the x-ms-blob-public-access header returns error code 400 (UnsupportedHeader). You can, however, obtain public access for Premium Storage by creating a SAS URI with the right permissions and an infinite expiration time.

For additional error information, see Blob Service Error Codes.

Restrictions on REST API Operations Against Disks Attached to a Virtual Machine

When a disk backed by a page blob in Premium Storage is attached to an Azure Virtual Machine, certain REST API operations are not permitted. These operations are permitted against the disk only if it is detached from the Virtual Machine. If a restricted operation is called against an attached disk, the service returns error code 409 (SystemInUse).

The table below shows operations that are restricted for attached disks.

Operation Type Restricted Operations for Attached Disks
Read operations Get Blob

Get Page Ranges
Write operations Put Blob

Put Page

Set Blob Properties

Set Blob Metadata
Delete operations Delete Blob
Lease operations Lease Blob

See Also

Blob Service Error Codes