Tiering Actions - Cost Reduction via Tier Changes

Cloud Storage Manager lets you change the access tier of individual blobs or sets of blobs without leaving the tool. Moving old, infrequently-accessed data from Hot tier to Cool or Archive reduces your Azure bill without changing what is available — the data is still there, just at a lower-cost tier with different access characteristics.

Azure tier recap

Azure Blob Storage offers three access tiers:

• Hot — most expensive storage cost per GB, cheapest retrieval. Use for actively-accessed data.
• Cool — about half the storage cost of Hot, higher retrieval cost, 30-day minimum storage duration. Use for data accessed less than once a month.
• Archive — cheapest storage by an order of magnitude, expensive and slow to retrieve (hours), 180-day minimum storage duration. Use for compliance archives, backups, audit data.

Microsoft publishes the per-GB pricing for each tier on the Azure storage pricing page — exact rates vary by region. The pattern is consistent: storage cost decreases sharply as you move toward Archive, retrieval cost increases.

What permissions are needed

To change blob tier, your signed-in Azure account needs Storage Blob Data Contributor (or higher) on the storage account. The Reader role used for scanning is not enough for tier changes.

Change tier on a single blob

1. Find the blob in Storage Account Explorer, top 100 blobs, or search.
2. Right-click the blob → Change tier.
3. Pick the target tier (Hot / Cool / Archive).
4. Confirm. The change is queued to Azure and reflected within seconds.

Bulk-change tier

1. Open the Storage Account Explorer or a search result list.
2. Select multiple blobs (Ctrl+click or Shift+click).
3. Right-click the selection → Change tier.
4. Pick the target tier.
5. Review the summary (number of blobs, total size, estimated monthly cost change) and click Apply.

Bulk changes are queued to Azure and processed in parallel. Progress is shown in the bottom status bar; you can continue using the tool while the changes apply.

A typical cost-reduction workflow

1. Open top 100 blobs. Sort by Tier ascending, then Size descending. Result: largest blobs still in Hot tier at the top.
2. For each candidate: check Last accessed. If older than 30 days → move to Cool. Older than 180 days → consider Archive (if retrieval delay is acceptable).
3. Select all matching candidates. Bulk Change tier to Cool.
4. Estimated monthly cost change is shown in the confirmation dialog.
5. Apply.

Repeat monthly as new old data accumulates, or set Azure lifecycle policies on the storage accounts to handle the rule going forward.

Considerations

• Minimum storage duration applies. Moving a blob to Cool means a 30-day minimum at that tier — if you move it back to Hot within 30 days, Azure charges an early-deletion penalty. Same for Archive (180 days). Move only data you are confident is genuinely cold.
• Archive retrieval is slow. Promoting a blob from Archive back to Hot can take hours. Archive only data you are unlikely to need urgently.
• Lifecycle policies are often better for ongoing automation. For a "move blobs to Cool when 30 days old" rule, configure it as an Azure lifecycle policy on the storage account rather than running manual tier changes through Cloud Storage Manager every month. Cloud Storage Manager is best for the initial cleanup pass; lifecycle policies handle steady state.

Undoing a tier change

A tier change is reversible — right-click the blob → Change tier → pick a different tier. Beware the minimum-storage-duration penalties described above.

See also

• Top reports — for finding tier-change candidates.
• Storage Account Explorer — for browsing and right-click actions.

Need help? support@smikar.com.