Check Blob lifecycle rules before changing access tiers

Why this is worth a look

Azure documents separate cost components for moving data out of Archive: the Set Blob Tier call is billed as an Archive read operation, retrieval is charged per GB moved to an online tier, and data moved before 180 days can incur a prorated early-deletion fee. Lifecycle policies are free, but their Set Blob Tier operations have standard operation costs. A policy can cover one storage account, selected containers, or blobs matched by prefixes or blob-index tags. Multiple filters in one rule use logical AND. A new or updated policy can take up to 24 hours to take effect, while processing the actions can take longer depending on account size and operations.

Run this portal checklist before a tier change. It uses Azure Cost Analysis for the selected subscription scope and the storage account's lifecycle policy for scope and support checks. It makes no resource changes.

1. In Azure portal, open Cost Management + Billing, then Cost management > Cost analysis. Set the subscription scope you are authorized to view.
2. Add the Service name filter and choose Storage. Add a filter for the target storage account when the view offers one. Record the current costs shown for the selected subscription scope.
3. Open the target storage account's lifecycle policy. Confirm whether rules cover the entire account, selected containers, or blobs selected by name prefixes or blob-index tags. If a rule has multiple filters, check their combined logical-AND scope.
4. Confirm the target data and account fit the documented limits: setting a tier is allowed only for Block Blobs; lifecycle tiering is not supported in premium block blob accounts and is not allowed for Append or Page Blobs in other accounts. Lifecycle policies cannot rehydrate Archive blobs to an online tier.
5. For an Archive move, record the possible Archive read operation, per-GB retrieval fee, and prorated early-deletion fee when the source data has been in Archive for less than 180 days. After a policy change, allow up to 24 hours for it to take effect, then allow additional processing time that varies with account size and operations.

How to confirm it

1. 01

   Open the supported cost view

   In Azure portal, open Cost Management + Billing, choose Cost management > Cost analysis, set the authorized subscription scope, and filter Service name to Storage. Add a filter for specific storage accounts when available. This review does not modify Blob resources.

2. 02

   Review current costs

   Record the current costs shown for the selected subscription scope. For Blob Storage capacity, a bill line expressed in GB uses Azure's binary GB convention, so 1 GB on that line corresponds to 1 GiB.

3. 03

   Check lifecycle targeting

   Inspect the target account's lifecycle policy. Confirm whether it covers the whole account, selected containers, or blobs matched by prefixes or blob-index tags, and remember that multiple filters in one rule are combined with logical AND.

4. 04

   Validate the planned move

   Confirm the blob and account types support the planned action. For Archive data, include the Archive read, per-GB retrieval, and possible prorated early-deletion charges. Lifecycle policy activation can take up to 24 hours, with action processing taking longer when the account or workload is larger.

Primary sources