Archived data must be rehydrated before standard blob retrieval. In this case, an operator accidentally overwrites a prior blob version during copy. “Archive tier for objects requiring immediate online reads” would not satisfy that requirement; the supported action is “Enable supported blob versioning or appropriate retention before bulk updates”. Version history and retention help recover unintended overwrites.

Private blob listing is a data-plane operation that needs blob data authorization. In this case, an operator accidentally overwrites a prior blob version during copy. “Storage Blob Data Reader or equivalent scoped data permission” would not satisfy that requirement; the supported action is “Enable supported blob versioning or appropriate retention before bulk updates”. Version history and retention help recover unintended overwrites.

Infrequent online tiers trade lower storage cost for retrieval and minimum-retention considerations. In this case, an operator accidentally overwrites a prior blob version during copy. “Cool or Cold tier subject to the region and required retrieval latency” would not satisfy that requirement; the supported action is “Enable supported blob versioning or appropriate retention before bulk updates”. Version history and retention help recover unintended overwrites.

Account keys authorize far more than a one-off file upload. In this case, a company hosts rarely accessed regulatory blobs but needs eventual access without full archive delays. “Issue narrowly scoped temporary delegated access instead of the broad key” would not satisfy that requirement; the supported action is “Cool or Cold tier subject to the region and required retrieval latency”. Infrequent online tiers trade lower storage cost for retrieval and minimum-retention considerations.

A narrow SAS permits delegated upload without issuing an account-level secret. In this case, a company hosts rarely accessed regulatory blobs but needs eventual access without full archive delays. “A limited write/create SAS scoped to the required container or blob” would not satisfy that requirement; the supported action is “Cool or Cold tier subject to the region and required retrieval latency”. Infrequent online tiers trade lower storage cost for retrieval and minimum-retention considerations.

Version history and retention help recover unintended overwrites. In this case, a company hosts rarely accessed regulatory blobs but needs eventual access without full archive delays. “Enable supported blob versioning or appropriate retention before bulk updates” would not satisfy that requirement; the supported action is “Cool or Cold tier subject to the region and required retrieval latency”. Infrequent online tiers trade lower storage cost for retrieval and minimum-retention considerations.

Bulk copying can overwrite or duplicate destination objects if targets and flags are wrong. In this case, an audit cannot tolerate delayed blob rehydration. “Correct target container, object naming and overwrite strategy before execution” would not satisfy that requirement; the supported action is “Archive tier for objects requiring immediate online reads”. Archived data must be rehydrated before standard blob retrieval.

A narrow SAS permits delegated upload without issuing an account-level secret. In this case, an audit cannot tolerate delayed blob rehydration. “A limited write/create SAS scoped to the required container or blob” would not satisfy that requirement; the supported action is “Archive tier for objects requiring immediate online reads”. Archived data must be rehydrated before standard blob retrieval.

Version history and retention help recover unintended overwrites. In this case, an audit cannot tolerate delayed blob rehydration. “Enable supported blob versioning or appropriate retention before bulk updates” would not satisfy that requirement; the supported action is “Archive tier for objects requiring immediate online reads”. Archived data must be rehydrated before standard blob retrieval.

Infrequent online tiers trade lower storage cost for retrieval and minimum-retention considerations. In this case, a partner must upload exactly one export to a blob container. “Cool or Cold tier subject to the region and required retrieval latency” would not satisfy that requirement; the supported action is “A limited write/create SAS scoped to the required container or blob”. A narrow SAS permits delegated upload without issuing an account-level secret.

Archived data must be rehydrated before standard blob retrieval. In this case, a partner must upload exactly one export to a blob container. “Archive tier for objects requiring immediate online reads” would not satisfy that requirement; the supported action is “A limited write/create SAS scoped to the required container or blob”. A narrow SAS permits delegated upload without issuing an account-level secret.

A managed network share is required for coordinated file access across hosts. In this case, a partner must upload exactly one export to a blob container. “VM local disks are not managed shared SMB file services” would not satisfy that requirement; the supported action is “A limited write/create SAS scoped to the required container or blob”. A narrow SAS permits delegated upload without issuing an account-level secret.

Infrequent online tiers trade lower storage cost for retrieval and minimum-retention considerations. In this case, a contractor gets an account access key to upload a single object. “Cool or Cold tier subject to the region and required retrieval latency” would not satisfy that requirement; the supported action is “Issue narrowly scoped temporary delegated access instead of the broad key”. Account keys authorize far more than a one-off file upload.

A managed network share is required for coordinated file access across hosts. In this case, a contractor gets an account access key to upload a single object. “VM local disks are not managed shared SMB file services” would not satisfy that requirement; the supported action is “Issue narrowly scoped temporary delegated access instead of the broad key”. Account keys authorize far more than a one-off file upload.

Azure Files provides managed network file shares accessible by multiple compatible clients. In this case, a contractor gets an account access key to upload a single object. “An Azure Files SMB share mounted by both VMs” would not satisfy that requirement; the supported action is “Issue narrowly scoped temporary delegated access instead of the broad key”. Account keys authorize far more than a one-off file upload.

Blob listing can return pages rather than the entire container in one call. In this case, an SMB application needs the same shared path across two Azure VMs. “Continuation tokens for complete paged blob enumeration” would not satisfy that requirement; the supported action is “An Azure Files SMB share mounted by both VMs”. Azure Files provides managed network file shares accessible by multiple compatible clients.

Large listings require segmented retrieval and prefix filters when appropriate. In this case, an SMB application needs the same shared path across two Azure VMs. “List blobs using a prefix and pagination or continuation tokens” would not satisfy that requirement; the supported action is “An Azure Files SMB share mounted by both VMs”. Azure Files provides managed network file shares accessible by multiple compatible clients.

Account keys authorize far more than a one-off file upload. In this case, an SMB application needs the same shared path across two Azure VMs. “Issue narrowly scoped temporary delegated access instead of the broad key” would not satisfy that requirement; the supported action is “An Azure Files SMB share mounted by both VMs”. Azure Files provides managed network file shares accessible by multiple compatible clients.

Blob listing can return pages rather than the entire container in one call. In this case, a team uses a VM's local disk as a multi-VM shared file path. “Continuation tokens for complete paged blob enumeration” would not satisfy that requirement; the supported action is “VM local disks are not managed shared SMB file services”. A managed network share is required for coordinated file access across hosts.

Large listings require segmented retrieval and prefix filters when appropriate. In this case, a team uses a VM's local disk as a multi-VM shared file path. “List blobs using a prefix and pagination or continuation tokens” would not satisfy that requirement; the supported action is “VM local disks are not managed shared SMB file services”. A managed network share is required for coordinated file access across hosts.

Account keys authorize far more than a one-off file upload. In this case, a team uses a VM's local disk as a multi-VM shared file path. “Issue narrowly scoped temporary delegated access instead of the broad key” would not satisfy that requirement; the supported action is “VM local disks are not managed shared SMB file services”. A managed network share is required for coordinated file access across hosts.

Policies need precise scope and cannot override enforced retention or holds. In this case, a container has millions of small objects and a developer requests a prefix-based list. “Lifecycle filters, version predicates and immutability restrictions” would not satisfy that requirement; the supported action is “List blobs using a prefix and pagination or continuation tokens”. Large listings require segmented retrieval and prefix filters when appropriate.

Retention safeguards can make automatic deletion ineligible. In this case, a container has millions of small objects and a developer requests a prefix-based list. “An immutability policy, legal hold or incompatible lifecycle condition” would not satisfy that requirement; the supported action is “List blobs using a prefix and pagination or continuation tokens”. Large listings require segmented retrieval and prefix filters when appropriate.

A managed network share is required for coordinated file access across hosts. In this case, a container has millions of small objects and a developer requests a prefix-based list. “VM local disks are not managed shared SMB file services” would not satisfy that requirement; the supported action is “List blobs using a prefix and pagination or continuation tokens”. Large listings require segmented retrieval and prefix filters when appropriate.

Policies need precise scope and cannot override enforced retention or holds. In this case, a client assumes the first list response contains every blob and misses objects. “Lifecycle filters, version predicates and immutability restrictions” would not satisfy that requirement; the supported action is “Continuation tokens for complete paged blob enumeration”. Blob listing can return pages rather than the entire container in one call.

Retention safeguards can make automatic deletion ineligible. In this case, a client assumes the first list response contains every blob and misses objects. “An immutability policy, legal hold or incompatible lifecycle condition” would not satisfy that requirement; the supported action is “Continuation tokens for complete paged blob enumeration”. Blob listing can return pages rather than the entire container in one call.

A managed network share is required for coordinated file access across hosts. In this case, a client assumes the first list response contains every blob and misses objects. “VM local disks are not managed shared SMB file services” would not satisfy that requirement; the supported action is “Continuation tokens for complete paged blob enumeration”. Blob listing can return pages rather than the entire container in one call.

Blob listing can return pages rather than the entire container in one call. In this case, a storage account uses a blob lifecycle rule to delete old versions after a retention period. “Continuation tokens for complete paged blob enumeration” would not satisfy that requirement; the supported action is “Lifecycle filters, version predicates and immutability restrictions”. Policies need precise scope and cannot override enforced retention or holds.

Storage subresources need matching private connectivity, not a blob-only endpoint. In this case, a storage account uses a blob lifecycle rule to delete old versions after a retention period. “A private endpoint and DNS for the file subresource as required” would not satisfy that requirement; the supported action is “Lifecycle filters, version predicates and immutability restrictions”. Policies need precise scope and cannot override enforced retention or holds.

Large listings require segmented retrieval and prefix filters when appropriate. In this case, a storage account uses a blob lifecycle rule to delete old versions after a retention period. “List blobs using a prefix and pagination or continuation tokens” would not satisfy that requirement; the supported action is “Lifecycle filters, version predicates and immutability restrictions”. Policies need precise scope and cannot override enforced retention or holds.

Storage subresources need matching private connectivity, not a blob-only endpoint. In this case, a protected object is still present after a lifecycle deletion date. “A private endpoint and DNS for the file subresource as required” would not satisfy that requirement; the supported action is “An immutability policy, legal hold or incompatible lifecycle condition”. Retention safeguards can make automatic deletion ineligible.

Azure Files uses its file endpoint and share protocol/authentication settings. In this case, a protected object is still present after a lifecycle deletion date. “The file service endpoint with appropriate authentication and networking” would not satisfy that requirement; the supported action is “An immutability policy, legal hold or incompatible lifecycle condition”. Retention safeguards can make automatic deletion ineligible.

Blob listing can return pages rather than the entire container in one call. In this case, a protected object is still present after a lifecycle deletion date. “Continuation tokens for complete paged blob enumeration” would not satisfy that requirement; the supported action is “An immutability policy, legal hold or incompatible lifecycle condition”. Retention safeguards can make automatic deletion ineligible.