A cloud-themed Azure dashboard connects institutional buildings above a hot-to-cool-to-cold data tiering diagram.
Smart tier for Azure Blob Storage and Azure Data Lake Storage is now generally available in Azure Government and in Azure China. That China cloud is Microsoft Azure operated by 21Vianet. Azure Updates listed the change as "Launched" on November 17, 2026. Microsoft's own definition of that label is fully released and production-ready.

The announcement is an availability expansion. It brings no new tiering behavior and no new API. For administrators in sovereign clouds, it moves a cost-automation feature from preview to production, so the account and tooling checks below now matter.

A cloud-themed Azure dashboard connects institutional buildings above a hot-to-cool-to-cold data tiering diagram. What changed, and what the evidence doesn't say​

Microsoft confirmed general availability of smart tier for Blob Storage and Data Lake Storage on April 14, 2026. That announcement covered nearly all zonal public cloud regions, and it excluded Israel Central, Qatar Central and UAE North. At that time, Azure Government and Azure China stayed in public preview, along with those three regions.

The November 17 listing closes that gap for the two sovereign clouds. The live Azure Updates page didn't show the announcement text when I looked, so the listing title is the only evidence for the exact scope. Microsoft Learn's smart tier documentation matches it. It says smart tier is generally available in all regions with zone redundancy across Azure public cloud, Azure Government, and Azure in China.

The documentation doesn't name individual regions or give a separate rollout date. Don't assume every redundancy option is available in every region. Check your own region first.

How smart tier behaves​

Smart tier manages objects across the hot, cool and cold capacity tiers, and it doesn't support the archive tier. The rules are simple:

  • Start: objects begin in the hot tier.
  • Hot to cool: an object moves to cool after 30 days with no access operation.
  • Cool to cold: it moves to cold after 60 more days without access, 90 days in total.
  • Reset: an access operation moves the object back to hot and restarts its tiering cycle.
  • Small objects: blobs under 128 KiB stay in hot, and normal tiering applies once they reach 128 KiB or more.

Not every read resets the clock. Get Blob and Put Blob count as access operations. Get Blob Properties, Get Blob Metadata and Get Blob Tags don't. That means monitoring or inventory scripts that only read metadata won't keep cold data warm.

Eligibility checklist​

Smart tier has firm requirements, so check them before you plan a migration:

  • Account type: it needs a Standard general-purpose v2 account. Legacy GPv1 and premium accounts aren't supported.
  • Redundancy: it needs ZRS, GZRS or RA-GZRS.
  • Blob type: it works only on block blobs. Page and append blobs aren't supported.
  • Redundancy conversions: converting to LRS or GRS isn't supported if you want to keep using smart tier.
  • Failover: if a GZRS account fails over, convert the resulting LRS account back to zone-redundant within 60 days to keep smart tier support.

Zone redundancy is the part most likely to catch sovereign-cloud teams out. Many existing accounts there may be on LRS or GRS, so adopting smart tier could mean a redundancy change first. That has its own cost and planning implications, which are my own inference rather than something Microsoft's documentation states.

Enabling it​

Smart tier is controlled by the account's default access tier.

In the Azure portal, for a new account:

  1. Under Storage accounts, select Create and fill in the Basics tab.
  2. On the Advanced tab, under Blob storage, set Access tier to Smart.
  3. Select Review + Create.

In the Azure portal, for an existing account:

  1. Open the storage account and go to Settings, then Configuration.
  2. Change Blob access tier (default) to Smart. The default is Hot if it was never set.
  3. Save.

With PowerShell:

Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account-name> -AccessTier Smart

With Azure CLI:

az storage account update --resource-group <resource-group> --name <storage-account-name> --access-tier Smart

Microsoft lists these minimum tool versions:

ToolMinimum version
REST API2025-08-01
.NET1.7.0
Java2.56.0
Python25.0.0
JavaScript20.0.0
PowerShell (Az.Storage)9.7.0
Azure CLI2.87.0

On an existing account, blobs without an explicit tier move to smart tier. Blobs with an explicit tier stay where they are. Moving an object out of smart tier by assigning a different online tier is a one-way trip, because it can't be tiered back into smart tier. Also, tracking starts after enablement, so the first tiering event happens 30 days later. Savings won't show up on day one.

Billing​

Smart tier has no capacity price of its own. You pay the rate for whichever tier an object currently sits in. Microsoft documents these billing rules:

  • Monitoring fee: a monthly monitoring operation charge applies to each smart-managed object over 128 KiB. Objects of 128 KiB or smaller carry no fee.
  • Free transitions: moves between tiers inside smart tier aren't charged as tier transitions.
  • No retrieval or early deletion fees: objects in smart tier don't incur early-deletion or data-retrieval charges.
  • Access operations: these are billed at hot-tier rates.
  • Leaving smart tier: moving an object out costs one cool write transaction per object.
  • Versions and snapshots: these are billed at full content length.

The monitoring fee is per object, so the savings depend on your data. A container with millions of mid-sized objects that are rarely touched could pay a meaningful monitoring bill. Large, rarely read files are the best fit. Microsoft doesn't promise lower bills for every account, so model your object count, object sizes and access frequency before you switch.

Lifecycle management and other caveats​

Existing lifecycle policies won't control smart-managed objects. Blob lifecycle management doesn't affect tiering for smart tier objects, though it still acts on delete operations. Storage actions can't influence smart tier transitions either. Soft-deleted objects keep moving toward cooler tiers until their deletion expiry period ends. If you run tier-down rules today, work out which ones will go quiet after you enable smart tier.

Monitoring what it does​

Metrics are free in the Azure portal under Monitoring, then Metrics. To see how objects are distributed:

  1. Set Metric Namespace to Blob.
  2. Choose Blob Count or Blob Capacity.
  3. Set Aggregation to Avg.
  4. Apply splitting by Blob tier and Blob type.

The smart-specific tier values are SmartHot, SmartCool, SmartCold and SmartHot-small. BlockBlob, Smart shows the total objects eligible for the monitoring fee. Objects with an explicit tier still appear as plain Hot, Cool or Cold.

Bottom line​

For Government and China-cloud administrators, this is a supported production option instead of a preview. A sensible rollout looks like this:

  1. Confirm the account is GPv2 with zone redundancy, holds block blobs only, and sits in a supported region.
  2. Estimate the monitoring fee from your object count and size distribution.
  3. Pilot on one non-critical account.
  4. Watch the SmartHot, SmartCool and SmartCold metrics for at least 90 days to see the full tiering cycle.

Microsoft's documentation was last updated June 22, 2026, before this announcement, so recheck the region list before you commit.

 

References

  1. (Launched) Generally Available: Smart Tier (Azure Blob and Data Lake Storage) in Azure Government and China regions Azure Updates 2026-11-17T20:00:32Z
  2. Optimize Azure Blob Storage costs with smart tier - Azure Storage learn.microsoft.com
  3. Azure Smart Tier: How to Save Money with Automated Tiering - SCHNEIDER IT MANAGEMENT schneider.im