Version 2019-02-02
The 2019-02-02 Azure Storage version includes the following features and updates:
A new API, Blob Batch, allows multiple requests to be sent within a single request body.
Data transfer APIs accept CRC64 as a transactional data-integrity mechanism as an alternative to MD5. Note that this calculation requires a specific polynomial.
Responses for all Azure Blob Storage, Azure Table Storage, and Azure Queue Storage APIs return the
x-ms-client-request-id
that was passed in thanks to requests for better code debugging.You can encrypt data by using a
Customer-Provided Key
or anEncryption Scope
.The Copy Blob, Put Block List, and Put Blob APIs support the
x-ms-access-tier
header for block blobs, to set the tier on the result without needing a second API call.The Copy Blob and Set Blob Tier APIs support the
x-ms-rehydrate-priority
header to allow for faster retrieval of archived blobs.A new Create Permission API lets you create a security descriptor at the file share level. This descriptor can be used for files and directories in the share.
A new Get Permission API lets you retrieve the security descriptor that's set on a share.
A new Lease File SPI gives you an exclusive write lock lease on a file to be acquired, changed, released, or broken.
Certain Azure Files APIs (Set Directory Properties, Set File Properties, Create File, and Create Directory) require a new set of headers. These headers are
x-ms-file-permission
,x-ms-file-permission-key
,x-ms-file-attributes
,x-ms-file-creation-time
andx-ms-file-last-write-time
. These headers are also returned on the corresponding Get APIs.