Perform REST operations against page blobs with premium storage
Azure premium storage offers a solution for Azure virtual machine workloads requiring high performance and low latency. Premium disks are backed by page blobs in Azure Storage. This topic provides information about performing REST operations against page blobs in general purpose v2 (GPv2) storage accounts with premium performance. To learn more about Azure premium storage, see Premium SSD.
For information about premium block blob storage, see Azure Block Blob storage performance tiers.
For information about premium file storage, see How to create a premium Azure file share.
To create and manage accounts by using Resource Manager, see the Storage Resource Provider REST API reference. To create and manage classic accounts, see the Service Management REST API reference.
You can also access page blobs in GPv2 storage accounts via the Azure Storage Client Library for .NET.
Premium GPv2 storage accounts support page blobs only
A premium GPv2 account stores only page blobs, and only REST APIs for page blobs and their containers are supported.
Note
Premium GPv2 accounts do not support block blobs, or the File, Table, and Queue services. However, premium BlockBlobStorage accounts do support block and append blobs. For more information and to see all the various storage options, visit Types of storage accounts
A premium GPv2 endpoint cannot be mapped to a custom domain name.
REST API restrictions on a premium GPv2 account
There are certain restrictions when using the Blob service REST API against a premium GPv2 account:
Only REST operations using version 2014-02-14 and later are supported. See Versioning for the Azure Storage Services for details.
The number of snapshots per page blob is limited to 100. If that limit is exceeded, the Snapshot Blob operation returns error code 409 (SnapshotCountExceeded).
A snapshot of a page blob may be taken once every ten minutes. If that rate is exceeded, the
Snapshot Bloboperation returns error code 409 (SnapshotOperationRateExceeded).Public access to a container storing page blobs is not permitted. Calling Set Container ACL with the
x-ms-blob-public-accessheader returns error code 400 (UnsupportedHeader). You can obtain public access 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 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 following table 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 |