Blob Storage feature support in Azure storage accounts (original) (raw)

Feature support is impacted by the type of account that you create and the settings that enable on that account. You can use the tables in this article to assess feature support based on these factors. The items that appear in these tables will change over time as support continues to expand.

How to use these tables

Each table uses the following icons to indicate support level:

Icon	Description
✅	Fully supported
🟦	Supported at the preview level
⬤	Not yet supported

This table describes the impact of enabling the capability and not the specific use of that capability. For example, if you enable the Network File System (NFS) 3.0 protocol but never use the NFS 3.0 protocol to upload a blob, a check mark in the NFS 3.0 enabled column indicates that feature support is not negatively impacted by merely enabling NFS 3.0 support.

Even though a feature is not be negatively impacted, it might not be compatible when used with a specific capability. For example, enabling NFS 3.0 has no impact on Microsoft Entra authorization. However, you can't use Microsoft Entra ID to authorize an NFS 3.0 request. See any of these articles for information about known limitations:

Standard general-purpose v2 accounts

The following table describes whether a feature is supported in a standard general-purpose v2 account when you enable a hierarchical namespace (HNS), NFS 3.0 protocol, or SFTP.

Important

This table describes the impact of enabling HNS, NFS, or SFTP and not the specific use of those capabilities.

Storage feature	Default	HNS	NFS	SFTP
Access tiers (hot, cool, cold, and archive)	✅	✅	✅	✅
Microsoft Entra security	✅	✅	✅1	✅1
Azure DNS Zone endpoints (preview)	✅	✅	✅	✅
Blob inventory	✅	✅	✅	✅
Blob index tags	✅	⬤	⬤	⬤
Blob snapshots	✅	🟦	🟦	🟦
Blob Storage APIs	✅	✅	✅	✅
Blob Storage Azure CLI commands	✅	✅	✅	✅
Blob Storage events	✅	✅	✅	✅
Blob Storage PowerShell commands	✅	✅	✅	✅
Blob versioning	✅	⬤	⬤	⬤
Blobfuse	✅	✅	✅	✅
Change feed	✅	⬤	⬤	⬤
Custom domains	✅	🟦	🟦	🟦
Customer-managed planned failover (preview)	🟦	🟦	⬤	🟦
Customer-managed (unplanned) failover	✅	✅	⬤	✅
Customer-managed keys with key vault in the same tenant	✅	✅	✅	✅
Customer-managed keys with key vault in a different tenant (cross-tenant)	✅	✅	⬤	⬤
Customer-provided keys	✅	⬤	⬤	⬤
Data redundancy options	✅	✅	✅2	✅
Encryption scopes	✅	✅	✅	✅
Immutable storage	✅	✅	⬤	⬤
Last access time tracking for lifecycle management	✅	✅	✅	✅
Lifecycle management policies (delete blob)	✅	✅	✅	✅
Lifecycle management policies (tiering)	✅	✅	✅	✅
Logging in Azure Monitor	✅	✅	✅	✅
Metrics in Azure Monitor	✅	✅	✅	✅
Object replication for block blobs	✅	⬤	⬤	⬤
Point-in-time restore for block blobs	✅	⬤	⬤	⬤
Prevent anonymous read access	✅	✅	✅	✅
Soft delete for blobs	✅	✅	✅	✅
Soft delete for containers	✅	✅	✅	✅
Static websites	✅	✅	🟦	✅
Storage Analytics logs (classic)	✅	✅	⬤	✅
Storage Analytics metrics (classic)3	⬤	⬤	⬤	⬤

1 Requests that clients make by using NFS 3.0 or SFTP can't be authorized by using Microsoft Entra security.

2 Only locally redundant storage (LRS) and zone-redundant storage (ZRS) are supported.

3 Storage Analytics metrics is retired. See Transition to metrics in Azure Monitor.

Premium block blob accounts

The following table describes whether a feature is supported in a premium block blob account when you enable a hierarchical namespace (HNS), NFS 3.0 protocol, or SFTP.