Blob Storage feature support in Azure Storage accounts

This article shows whether a feature is fully supported (generally available), supported at the preview level, or is not yet supported. Support levels are impacted by storage account type, and whether certain capabilities or protocols are enabled on the account.

The items that appear in these tables will change over time as support continues to expand.

Standard general-purpose v2 accounts

Storage feature Blob Storage (default support) Data Lake Storage Gen2 1 NFS 3.0 1
Access tier - archive Yes Yes Yes
Access tier - cold Yes Yes Yes
Access tier - hot Yes Yes Yes
Anonymous public access Yes Yes Yes
Azure Active Directory security Yes Yes No
Blob inventory Yes Yes 2 Yes 2
Blob index tags Yes No No
Blob snapshots Yes Yes 2 No
Blob Storage APIs Yes Yes 3 Yes 3
Blob Storage Azure CLI commands Yes Yes Yes
Blob Storage events Yes Yes 3 No
Blob Storage PowerShell commands Yes Yes Yes
Blob versioning Yes No No
Blobfuse Yes Yes Yes
Change feed Yes No No
Custom domains Yes Yes 2 Yes 2
Customer-managed account failover Yes No No
Customer-managed keys (encryption) Yes Yes Yes
Customer-provided keys (encryption) Yes No No
Data redundancy options Yes Yes Yes
Encryption scopes Yes No No
Immutable storage Yes Yes 2 Yes 2
Last access time tracking for lifecycle management Yes Yes No
Lifecycle management policies (delete blob) Yes Yes Yes
Lifecycle management policies (tiering) Yes Yes Yes
Logging in Azure Monitor Yes 2 Yes 2 Yes 2
Metrics in Azure Monitor Yes Yes Yes
Object replication for block blobs Yes No No
Page blobs Yes No No
Point-in-time restore for block blobs Yes No No
Soft delete for blobs Yes Yes 2 3 No
Soft delete for containers Yes Yes No
Static websites Yes Yes Yes
Storage Analytics logs (classic) Yes Yes 3 No
Storage Analytics metrics (classic) Yes Yes Yes

1 Data Lake Storage Gen2 and the Network File System (NFS) 3.0 protocol both require a storage account with a hierarchical namespace enabled.

2 Feature is supported at the preview level.

3 See Known issues with Azure Data Lake Storage Gen2. These issues apply to all accounts that have the hierarchical namespace feature enabled.

Premium block blob accounts

Storage feature Blob Storage (default support) Data Lake Storage Gen2 1 NFS 3.0 1
Access tier - archive No No No
Access tier - cold No No No
Access tier - hot No No No
Anonymous public access Yes Yes Yes
Azure Active Directory security Yes Yes No
Blob inventory Yes Yes 2 Yes 2
Blob index tags No No No
Blob snapshots Yes Yes 2 No
Blob Storage APIs Yes Yes 3 Yes 3
Blob Storage Azure CLI commands Yes Yes Yes
Blob Storage events Yes 3 Yes 3 No
Blob Storage PowerShell commands Yes Yes Yes
Blob versioning Yes No No
Blobfuse Yes Yes Yes
Change feed No No No
Custom domains Yes Yes 2 Yes 2
Customer-managed account failover No No No
Customer-managed keys (encryption) Yes Yes Yes
Customer-provided keys (encryption) Yes No No
Data redundancy options Yes Yes Yes
Encryption scopes Yes No No
Immutable storage Yes Yes 2 Yes 2
Last access time tracking for lifecycle management Yes Yes No
Lifecycle management policies (delete blob) Yes Yes Yes
Lifecycle management policies (tiering) No No No
Logging in Azure Monitor Yes 2 Yes 2 Yes 2
Metrics in Azure Monitor Yes Yes 2 Yes 2
Object replication for block blobs Yes No No
Page blobs Yes No No
Point-in-time restore for block blobs No No No
Soft delete for blobs Yes Yes 2 3 No
Soft delete for containers Yes Yes No
Static websites Yes Yes Yes
Storage Analytics logs (classic) Yes Yes 2 3 No
Storage Analytics metrics (classic) Yes Yes Yes

1 Data Lake Storage Gen2 and the Network File System (NFS) 3.0 protocol both require a storage account with a hierarchical namespace enabled.

2 Feature is supported at the preview level.

3 See Known issues with Azure Data Lake Storage Gen2. These issues apply to all accounts that have the hierarchical namespace feature enabled.

See also