Recovery retention ends according to the configured policy. In this case, an account has blob soft delete but not container soft delete. “The object may no longer be recoverable through soft delete” would not satisfy that requirement; the supported action is “Deleted containers may not be restorable through blob-only protection”. Blob and container soft-delete settings protect different deletion scopes.

Soft delete protects only within the configured retention period. In this case, an account has blob soft delete but not container soft delete. “The configured soft-delete retention interval has elapsed” would not satisfy that requirement; the supported action is “Deleted containers may not be restorable through blob-only protection”. Blob and container soft-delete settings protect different deletion scopes.

Blob soft delete retains recently deleted blob states for the configured interval. In this case, an account has blob soft delete but not container soft delete. “Blob soft delete with adequate retention” would not satisfy that requirement; the supported action is “Deleted containers may not be restorable through blob-only protection”. Blob and container soft-delete settings protect different deletion scopes.

Blob and container soft-delete settings protect different deletion scopes. In this case, an application deletes a single blob and needs to restore it during a seven-day window. “Deleted containers may not be restorable through blob-only protection” would not satisfy that requirement; the supported action is “Blob soft delete with adequate retention”. Blob soft delete retains recently deleted blob states for the configured interval.

Container soft delete can restore deleted eligible containers within retention. In this case, an application deletes a single blob and needs to restore it during a seven-day window. “Container soft delete” would not satisfy that requirement; the supported action is “Blob soft delete with adequate retention”. Blob soft delete retains recently deleted blob states for the configured interval.

Soft delete protects only within the configured retention period. In this case, an application deletes a single blob and needs to restore it during a seven-day window. “The configured soft-delete retention interval has elapsed” would not satisfy that requirement; the supported action is “Blob soft delete with adequate retention”. Blob soft delete retains recently deleted blob states for the configured interval.

Blob and container soft-delete settings protect different deletion scopes. In this case, a blob was deleted 40 days ago but soft delete retains seven days. “Deleted containers may not be restorable through blob-only protection” would not satisfy that requirement; the supported action is “The object may no longer be recoverable through soft delete”. Recovery retention ends according to the configured policy.

Azure Files share soft delete protects a different storage service and cannot restore the already expired Blob soft-delete retention interval. In this case, a blob was deleted 40 days ago but soft delete retains seven days. “Enable Azure Files share soft delete instead of Blob soft delete” would not satisfy that requirement; the supported action is “The object may no longer be recoverable through soft delete”. Recovery retention ends according to the configured policy.

Soft delete protects only within the configured retention period. In this case, a blob was deleted 40 days ago but soft delete retains seven days. “The configured soft-delete retention interval has elapsed” would not satisfy that requirement; the supported action is “The object may no longer be recoverable through soft delete”. Recovery retention ends according to the configured policy.

Azure Files NFS has specific protocol, tier and connectivity requirements. In this case, a company wants a folder structure with atomic directory operations and POSIX-style ACL support. “Use an appropriate NFS-enabled share and supported storage tier/network configuration” would not satisfy that requirement; the supported action is “Hierarchical namespace in an ADLS Gen2-enabled storage account”. Hierarchical namespace provides directory operations for analytics workloads over Azure Blob Storage.

Blob soft delete retains recently deleted blob states for the configured interval. In this case, a company wants a folder structure with atomic directory operations and POSIX-style ACL support. “Blob soft delete with adequate retention” would not satisfy that requirement; the supported action is “Hierarchical namespace in an ADLS Gen2-enabled storage account”. Hierarchical namespace provides directory operations for analytics workloads over Azure Blob Storage.

SMB and NFS are distinct protocols and cannot be interchanged by changing a mount string. In this case, a company wants a folder structure with atomic directory operations and POSIX-style ACL support. “NFS protocol was not selected or supported for that share” would not satisfy that requirement; the supported action is “Hierarchical namespace in an ADLS Gen2-enabled storage account”. Hierarchical namespace provides directory operations for analytics workloads over Azure Blob Storage.

SMB and NFS are distinct protocols and cannot be interchanged by changing a mount string. In this case, an analytics team expects directory ACLs from ordinary flat-namespace blobs. “NFS protocol was not selected or supported for that share” would not satisfy that requirement; the supported action is “Enable hierarchical namespace when creating a supported new account”. Hierarchical namespace changes supported namespace/permission semantics.

Azure Files NFS has specific protocol, tier and connectivity requirements. In this case, an analytics team expects directory ACLs from ordinary flat-namespace blobs. “Use an appropriate NFS-enabled share and supported storage tier/network configuration” would not satisfy that requirement; the supported action is “Enable hierarchical namespace when creating a supported new account”. Hierarchical namespace changes supported namespace/permission semantics.

Recovery retention ends according to the configured policy. In this case, an analytics team expects directory ACLs from ordinary flat-namespace blobs. “The object may no longer be recoverable through soft delete” would not satisfy that requirement; the supported action is “Enable hierarchical namespace when creating a supported new account”. Hierarchical namespace changes supported namespace/permission semantics.

Different storage services have separate lifecycle and tiering controls. In this case, a file service must mount Azure Files from Linux using NFS. “Blob lifecycle policies do not manage Azure Files share tiers” would not satisfy that requirement; the supported action is “Use an appropriate NFS-enabled share and supported storage tier/network configuration”. Azure Files NFS has specific protocol, tier and connectivity requirements.

Hierarchical namespace provides directory operations for analytics workloads over Azure Blob Storage. In this case, a file service must mount Azure Files from Linux using NFS. “Hierarchical namespace in an ADLS Gen2-enabled storage account” would not satisfy that requirement; the supported action is “Use an appropriate NFS-enabled share and supported storage tier/network configuration”. Azure Files NFS has specific protocol, tier and connectivity requirements.

Hierarchical namespace changes supported namespace/permission semantics. In this case, a file service must mount Azure Files from Linux using NFS. “Enable hierarchical namespace when creating a supported new account” would not satisfy that requirement; the supported action is “Use an appropriate NFS-enabled share and supported storage tier/network configuration”. Azure Files NFS has specific protocol, tier and connectivity requirements.

Different storage services have separate lifecycle and tiering controls. In this case, a share is configured only for SMB and a Linux NFS client fails to mount. “Blob lifecycle policies do not manage Azure Files share tiers” would not satisfy that requirement; the supported action is “NFS protocol was not selected or supported for that share”. SMB and NFS are distinct protocols and cannot be interchanged by changing a mount string.

Hierarchical namespace changes supported namespace/permission semantics. In this case, a share is configured only for SMB and a Linux NFS client fails to mount. “Enable hierarchical namespace when creating a supported new account” would not satisfy that requirement; the supported action is “NFS protocol was not selected or supported for that share”. SMB and NFS are distinct protocols and cannot be interchanged by changing a mount string.

Lifecycle policies can transition eligible blobs between supported online tiers. In this case, a share is configured only for SMB and a Linux NFS client fails to mount. “A Blob lifecycle management rule based on last-modified age” would not satisfy that requirement; the supported action is “NFS protocol was not selected or supported for that share”. SMB and NFS are distinct protocols and cannot be interchanged by changing a mount string.

Time-based retention prevents deletion or modification during the configured WORM period. In this case, a storage container should move old objects from Hot to Cool after 45 days. “Time-based immutable storage policy for eligible blobs” would not satisfy that requirement; the supported action is “A Blob lifecycle management rule based on last-modified age”. Lifecycle policies can transition eligible blobs between supported online tiers.

Azure Files NFS has specific protocol, tier and connectivity requirements. In this case, a storage container should move old objects from Hot to Cool after 45 days. “Use an appropriate NFS-enabled share and supported storage tier/network configuration” would not satisfy that requirement; the supported action is “A Blob lifecycle management rule based on last-modified age”. Lifecycle policies can transition eligible blobs between supported online tiers.

Ordinary owner privileges do not override active immutability requirements. In this case, a storage container should move old objects from Hot to Cool after 45 days. “The operation is denied until relevant retention controls permit deletion” would not satisfy that requirement; the supported action is “A Blob lifecycle management rule based on last-modified age”. Lifecycle policies can transition eligible blobs between supported online tiers.

Azure Files NFS has specific protocol, tier and connectivity requirements. In this case, a lifecycle rule targets block blobs but a team expects Azure Files shares to cool automatically. “Use an appropriate NFS-enabled share and supported storage tier/network configuration” would not satisfy that requirement; the supported action is “Blob lifecycle policies do not manage Azure Files share tiers”. Different storage services have separate lifecycle and tiering controls.

Share snapshots represent point-in-time read-only copies of eligible share content. In this case, a lifecycle rule targets block blobs but a team expects Azure Files shares to cool automatically. “Take an Azure Files share snapshot” would not satisfy that requirement; the supported action is “Blob lifecycle policies do not manage Azure Files share tiers”. Different storage services have separate lifecycle and tiering controls.

SMB and NFS are distinct protocols and cannot be interchanged by changing a mount string. In this case, a lifecycle rule targets block blobs but a team expects Azure Files shares to cool automatically. “NFS protocol was not selected or supported for that share” would not satisfy that requirement; the supported action is “Blob lifecycle policies do not manage Azure Files share tiers”. Different storage services have separate lifecycle and tiering controls.

Lifecycle policies can transition eligible blobs between supported online tiers. In this case, a legal archive must keep objects until at least a defined retention date. “A Blob lifecycle management rule based on last-modified age” would not satisfy that requirement; the supported action is “Time-based immutable storage policy for eligible blobs”. Time-based retention prevents deletion or modification during the configured WORM period.

Snapshots support point-in-time retrieval of previously recorded share content. In this case, a legal archive must keep objects until at least a defined retention date. “Restore eligible data from an earlier file share snapshot” would not satisfy that requirement; the supported action is “Time-based immutable storage policy for eligible blobs”. Time-based retention prevents deletion or modification during the configured WORM period.

Different storage services have separate lifecycle and tiering controls. In this case, a legal archive must keep objects until at least a defined retention date. “Blob lifecycle policies do not manage Azure Files share tiers” would not satisfy that requirement; the supported action is “Time-based immutable storage policy for eligible blobs”. Time-based retention prevents deletion or modification during the configured WORM period.

Snapshots support point-in-time retrieval of previously recorded share content. In this case, an admin attempts to delete an object protected by active immutability. “Restore eligible data from an earlier file share snapshot” would not satisfy that requirement; the supported action is “The operation is denied until relevant retention controls permit deletion”. Ordinary owner privileges do not override active immutability requirements.

Share snapshots represent point-in-time read-only copies of eligible share content. In this case, an admin attempts to delete an object protected by active immutability. “Take an Azure Files share snapshot” would not satisfy that requirement; the supported action is “The operation is denied until relevant retention controls permit deletion”. Ordinary owner privileges do not override active immutability requirements.

Different storage services have separate lifecycle and tiering controls. In this case, an admin attempts to delete an object protected by active immutability. “Blob lifecycle policies do not manage Azure Files share tiers” would not satisfy that requirement; the supported action is “The operation is denied until relevant retention controls permit deletion”. Ordinary owner privileges do not override active immutability requirements.