Version 2017-04-17

  • Article

The 2017-04-17 Azure Storage version includes the following features and updates:

  • A new Set Blob Tier API is now available.

    • Use this API to explicitly set a premium page blob (or disk) to a tier without having to resize. The blob will be provisioned and billed at the new tier. This is also the only way to use the tiers P4 and P6. For more information about premium tiers, see High-performance premium storage and managed disks for VMs.

    • You can also use this API on block blobs in Azure Blob Storage or general purpose v2 (GPv2) accounts. The available tiers for block blobs are Hot, Cool, and Archive. For detailed information about block blob tiering see Hot, cool, and archive storage tiers.

  • The Create File, Create Directory, Put Range, Set Directory Metadata, Set File Metadata, and Set File Properties operations now return the x-ms-request-server-encrypted response header. This header is set to true if the contents of the request have been successfully encrypted.

  • The Get File, Get File Properties, and Get Directory Properties operations now return the x-ms-server-encrypted response header. This header is set to true if the file data and application metadata are completely encrypted. If the file is not encrypted, or if only parts of the file or application metadata are encrypted, this header is set to false.

  • The Azure Storage analytics logs that correspond to requests that use version 2017-04-17 or later have a more detailed <request-status> instead of ClientOtherError. The new codes are the same as the error codes returned by the service.

  • Using If-Match: * to access an uncommitted blob now fails.

  • If a request is throttled because it has reached the account-level Ingress, Egress, or IOPS (input/output operations per second) limits, a new user message is returned.

  • The List Blobs API now returns the continuation token in the Marker XML element. Previously, this was a blob name.