Azure Storage Actions: Pricing, Storage Tasks and Use Cases

Introduction

Once an Azure data estate reaches billions of blobs, consistency breaks down. Scripts drift, runbooks go stale, and someone forgets to delete the temporary data that has been billing for two years.

Azure Storage Actions is a managed service that applies conditional operations to objects in Blob Storage and Azure Data Lake Storage Gen2 through reusable storage tasks. It works on object storage, not Azure managed disks.

This guide covers how storage tasks work, what the service costs, which use cases it supports, and when Lifecycle Management or custom code is the better choice.

Key Takeaways

  • Storage Actions runs serverless, no-code tasks built from conditions, operations, and assignments.
  • Service charges are separate from transactions, tiering, retrieval, and egress costs.
  • Condition preview, managed identities, RBAC, reports, and monitoring keep runs safe.
  • Enables large-scale, conditional object management across Blob Storage and ADLS Gen2.

What Is Azure Storage Actions?

According to Microsoft's GA announcement, Azure Storage Actions became generally available on May 6, 2025. It is fully managed, serverless, and no-code, and it operates across millions of objects and multiple accounts without extra compute provisioning.

Two terms matter:

  • Storage task: defines the conditions and operations.
  • Task assignment: supplies the target account, scope, schedule, and report destination.

General Purpose v2 accounts are recommended. GPv1 and legacy Blob Storage accounts are excluded.

Supported operations

Operation What it does
SetBlobTier Moves blobs to Hot, Cool, Cold, or Archive
DeleteBlob / UndeleteBlob Deletes or restores blobs
SetBlobTags Applies tag/value pairs
SetBlobImmutabilityPolicy Sets a retention end date
SetBlobLegalHold Turns a legal hold on or off
SetBlobExpiry Sets absolute or relative expiry

Archive rehydration is supported at standard priority only. Conditions can read metadata, but setting metadata is not a listed operation.

The payoff is repeatable governance and less hand-built scanning code.

Each neighboring service does a different job:

  • Blob Lifecycle Management: applies time-based tiering and deletion rules.
  • Azure Functions: runs custom code.
  • Logic Apps: orchestrates visual workflows across systems.
  • Event Grid: routes blob creation and deletion events to handlers.
  • Blob Inventory: produces daily or weekly CSV or Parquet reports on blobs.

Storage Actions evaluates existing objects by their properties and acts on matches. It complements the others rather than replacing them. If you need real-time event handling, custom business logic, or an operation outside the task catalog, you still need Functions or Logic Apps.

How Azure Storage Tasks Work

The three-part model

Conditions pick eligible objects. Operations act on matches. Assignments configure where and when the task runs, and execution is asynchronous.

Conditions can combine these properties:

  • Name, container name, blob type, access tier
  • Metadata, container metadata, and tag values
  • Creation time, last-modified, last access time, tier change time, deleted time
  • Content length, tag count, deleted state, current-version flag

Operators include:

  • Logical: and, or, not
  • Comparisons such as equals and greater
  • String tests such as contains, startsWith, endsWith, and matches

Case-sensitive variants exist for most. Availability depends on property type, and matches does not work on metadata or tags. Conditions allow up to 10 nested clause groupings.

Azure Storage Actions condition properties and operators workflow diagram

A simple example: tier recordings to Cool when they carry a specific tag and haven't been modified in 90 days.

Preview before you commit

The condition preview is free and shows up to 5,000 matching blobs for a chosen container and optional prefix. Run it against representative production data before enabling anything destructive.

Mock runs go further. They evaluate your full scope and report without modifying blobs, but they incur execution and targeting charges.

Assignment controls

  • Target the whole account or include/exclude prefixes.
  • Run once, on a recurring schedule (in days), or as a mock.
  • Set start and end dates and a report container.
  • New assignments default to disabled; enabling one schedules execution.
  • Reuse one task across accounts through separate assignments.

Published limits include 5,000 tasks per subscription, 50 assignments per account, and one concurrent run per account. These are current figures, not launch-day quotas, so confirm the latest numbers in Azure documentation.

Security and observability

Tasks use a system-assigned managed identity by default, or a user-assigned one chosen at creation. Three roles matter:

  • Storage Actions Contributor: author tasks, with no data access.
  • Storage Actions Task Assignment Contributor: create assignments and stop runs.
  • Storage Actions Blob Data Operator: granted to the task identity for object operations.

Compressed CSV reports land in your target container with blob, operation, result, and error details. Azure Monitor tracks runs, failed runs, and successful or failed objects. Activity logs and alerts work, but resource logs aren't supported.

Azure Storage Actions Pricing and Cost Considerations

Service meters

As of November 2026, Microsoft's pricing page lists three USD meters:

Meter Rate
Task execution instance $0.25 per instance
Objects targeted $0.10 per 1M objects
Operations invoked $1.00 per 1M operations

An execution instance is one assignment run on an account. Targeting counts every object scanned or evaluated, not just those changed. Operations count API calls.

Azure Storage Actions pricing meters and billable cost components

Charges accrue to the target account's subscription. Rates vary by region, agreement, and date, and no effective date was published, so confirm before budgeting.

Costs that still apply

  • Blob transactions, tagging, and tiering operations
  • Tier-specific capacity charges
  • Read and retrieval fees for warmer-tier moves and archive rehydration
  • Early deletion charges
  • Outbound bandwidth

Early deletion windows run 30 days for Cool, 90 for Cold, and 180 for Archive.

Estimation framework

Enter these into the Azure Pricing Calculator:

  1. Task runs per month
  2. Objects scanned per run
  3. Operations per object
  4. Tier transitions and retrieval volume
  5. Data-transfer needs

Controlling spend

  • Narrow conditions with prefix filters so fewer objects are scanned.
  • Roll out in stages.
  • Match schedules to how fast data actually changes.
  • Skip needless repeat scans of stable data.

None of this should weaken retention or compliance rules. Check the calculator, regional pricing, and limits right before deployment.

Azure Storage Actions Use Cases

Lifecycle and cost optimization

  • Move aging objects to Cool or Archive.
  • Delete temporary or expired data.
  • Tier by naming pattern or tag.
  • Selectively rehydrate archived objects.

Check retrieval fees and early deletion windows first. Moving data to Archive and pulling it back a month later can cost more than it saves.

Governance and data protection

Apply retention, immutability, legal holds, expiry, or consistent tags to financial records, backups, customer recordings, and research data. The task logic must match your documented policy, since a wrong condition applied at scale is hard to unwind.

Large-scale and one-time operations

  • Clean up redundant datasets.
  • Initialize tags across existing data.
  • Restore selected objects.
  • Process many accounts at once.

Microsoft's GA announcement cites two examples. PointsBet managed petabytes of backups and logs across dozens of accounts and several regions, and reported saving weeks of development.

An unnamed US state tax agency restored about 600 million objects from billions of archived objects in hours rather than days. Both are Microsoft-reported, not independent benchmarks.

Azure Storage Actions large-scale operation examples and reported outcomes

Azure Storage Actions vs. Lifecycle Management: Implementation Guidance

How to Choose the Right Azure Storage Automation

Dimension Storage Actions Lifecycle Management
Conditions Properties, metadata, tags, logic Time-based, with prefix and tag filters
Scope Reusable tasks across accounts One policy per account, 100 rules max
Actions Seven operations, including rehydration Tiering and delete; no rehydration
Schedule One-time or recurring Periodic, not user-controlled
Filters Include and exclude prefixes 10 prefixes and 10 tag conditions per rule

Microsoft's guidance is clear: use Lifecycle Management for predictable time-based tiering and retention, and Storage Actions for complex, coordinated work across accounts. Lifecycle also isn't a guaranteed 24-hour service. Large runs can take days.

Azure Storage Actions versus Lifecycle Management decision comparison

Use custom code only for what tasks cannot handle: event-driven reactions (Event Grid, Functions), external system integration (Logic Apps), and unsupported operations.

Getting Started Safely

Prerequisites:

  • An Azure subscription and a compatible GPv2 account
  • Task and storage account in the same region
  • Managed identity with the right RBAC roles
  • A container for reports
  • Naming and tagging conventions
  • Current limits and known issues reviewed (multiple assignment filters may miss some directory prefixes)

Then work in this order:

  1. Create a narrowly scoped task.
  2. Preview matching objects.
  3. Test non-destructive operations first.
  4. Enable the assignment deliberately.
  5. Monitor the first run and review the report.
  6. Document rollback steps before widening scope.

Six-step safe Azure Storage Actions deployment process

Scope note: Storage Actions manages Blob Storage and ADLS Gen2 objects. Lucidity focuses on autonomous multi-cloud block-storage visibility and optimization, including Azure Premium SSD to Standard SSD tier moves without disruption. The two can complement each other for enterprises managing both object data and cloud block volumes. They are not interchangeable.

Frequently Asked Questions

Can I host my website for free on Azure?

Partly. Azure's free account gives $200 in credit for 30 days plus selected free quantities. Static Web Apps Free and App Service F1 carry usage caps and no SLA, and costs can appear from overages, domains, or other services.

What is the difference between blob and ADLS?

ADLS Gen2 builds on Blob Storage by adding a hierarchical namespace and directory semantics. For Storage Actions, both are supported, but some hierarchical namespace restrictions, such as tag conditions, still apply.

Can I use GitHub Actions with Azure?

Yes. The Azure Login action supports OpenID Connect through a federated identity credential. That is CI/CD automation, separate from Storage Actions' object management.

What does Azure Storage Actions cost?

Three meters: $0.25 per execution instance, $0.10 per million objects targeted, and $1.00 per million operations. Underlying storage costs are separate. Confirm on the current pricing page and calculator.

What operations can Azure Storage Actions perform?

Tiering, delete and undelete, tagging, immutability policies, legal holds, expiry, and standard-priority archive rehydration. Availability can change, so check the current documentation.

How is Azure Storage Actions different from Lifecycle Management?

Lifecycle Management handles simpler time-based tiering and deletion. Storage Actions adds broader conditions, more operations, reusable assignments, validation, and reporting.