About this deal
Over the course of the past year, tens of thousands of finds have been recovered, cleaned, catalogued and analysed by specialists.
A new XML element will be added to the ListBlob response, named Sealed. The value can be either true or false.
This includes details of the seal's legs, body, tail, nose, eyes, whiskers, and even its spots.
The purpose of the Append Blob Seal operation is to allow users and applications to seal append blobs, marking them as read-only. This document outlines the proposed REST API specs for this feature. Request
Pricing requests can originate from clients that use Blob Storage APIs, either directly through the Blob Storage REST API, or from an Azure Storage client library. These requests accrue charges per transaction. The type of transaction affects how the account is charged. For example, read transactions accrue to a different billing category than write transactions. The following table shows the billing category for Append Blob Seal requests based on the storage account type: Operation
When you copy a sealed blob, the sealed flag is propagated by default. A header is exposed that allows the flag to be overwritten. Calling the Append Blob Seal operation using a SAS token delegated to a container or blob resource requires the Write (w) permission as part of the user delegation SAS token.