Microsoft recommends disallowing Shared Key authorization for the storage account when possible. For more information, see Prevent authorization with Shared Key. Remarks

Sealed bottles have an applied glass seal on the shoulder or side of the bottle. The seal is a molten blob of glass that has been stamped with an embossed symbol, name or initials, and often it included a date. Collectors of bottles sometimes refer to them as Applied seals, Blob seals or Prunt seals. After you seal a blob, you can still update properties, blob index tags, and metadata. Soft-deleting a sealed blob preserves the sealed state. You can overwrite sealed blobs. Listed below are the RBAC action necessary for a Microsoft Entra user, group, or service principal to call the Append Blob Seal operation, and the least privileged built-in Azure RBAC role that includes this action: The Append Blob Seal operation supports Shared Key authorization. Authorizing with account keys is not recommended for most scenarios, as it's less secure.

A new XML element will be added to the ListBlob response, named Sealed. The value can be either true or false. You can construct the Append Blob Seal request as follows. HTTPS is recommended. Replace myaccount with the name of your storage account. PUT method request URI 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

However to get to that stage, all of our artefacts need to be cleaned – this is where our amazing community volunteers come into the process - a big thank you to them." 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 Optional. False by default. If the blob is sealed, this header is included in the response when you seal and get properties of a blob. This header should appear in GetBlob, GetBlobProperties, AppendBlobSeal, and ListBlobs for append blobs.To learn more about assigning roles using Azure RBAC, see Assign an Azure role for access to blob data.