Azure Storage prospects more and more function at huge scale, with tens of millions and even billions of things distributed throughout a number of storage accounts. As the dimensions of the information will increase, managing the information introduces a special set of challenges.
In a latest episode of Azure Storage Speak, I sat down with Shashank, a Product Supervisor on the Azure Storage Actions crew, to debate how Azure Storage Actions helps prospects automate widespread information administration duties with out writing customized code or managing infrastructure.
This put up summarizes the important thing ideas, situations, and learnings from that dialog. Hearken to the complete dialog under.
As storage estates develop, prospects typically have to:
- Apply retention or immutability insurance policies for compliance
- Shield delicate or essential information from modification
- Optimize storage prices by tiering sometimes accessed information
- Add or clear up metadata (blob index tags) for discovery and downstream processing
At this time, many shoppers deal with these wants by writing customized scripts or sustaining inside tooling. This method requires vital engineering effort, ongoing upkeep, cautious credential dealing with, and intensive testing, particularly when working throughout tens of millions of merchandise throughout a number of storage accounts.
These challenges turn out to be extra pronounced as information estates sprawl throughout areas and subscriptions.
Azure Storage Actions is a completely managed, serverless automation platform designed to carry out routine information administration operations at scale for:
- Azure Blob Storage
- Azure Information Lake Storage
It permits prospects to outline condition-based logic and apply native storage operations reminiscent of tagging, tiering, deletion, or immutability, throughout massive datasets with out deploying or managing servers. Azure Storage Actions is constructed round two most important ideas:
A storage process is an Azure Useful resource Supervisor (ARM) useful resource that defines:
- The circumstances used to guage blobs (for instance, file identify, dimension, timestamps, or index tags)
- The actions to take when circumstances are met (reminiscent of altering tiers, including immutability, or modifying tags)
The duty definition is created as soon as and centrally managed.
A process task applies a storage process to a number of storage accounts. This enables the identical logic to be reused with out redefining it for every account.
Every task can:
- Run as soon as (for cleanup or one-off processing)
- Run on a recurring schedule
- Be scoped utilizing container filters or excluded prefixes
Throughout the episode, Shashank demonstrated a real-world state of affairs involving a storage account utilized by a authorized crew.
- Establish PDF recordsdata tagged as essential
- Apply a time-based immutability coverage to stop tampering
- Transfer these recordsdata from the Scorching tier to the Archive tier to cut back storage prices
- Add a brand new tag indicating the information is protected
- Transfer all different blobs to the Cool tier for price effectivity
With out Storage Actions, this might sometimes require:
- Writing scripts to iterate by blobs
- Dealing with credentials and permissions
- Testing logic on pattern information
- Scaling execution safely throughout massive datasets
- Sustaining and rerunning the scripts over time
With Storage Actions, the administrator:
- Defines circumstances primarily based on file extension and index tags
- Chains a number of actions (immutability, tiering, tagging)
- Makes use of a built-in preview functionality to validate which blobs match the circumstances
- Executes the duty with out provisioning infrastructure
The whole workflow is authored declaratively within the Azure portal and executed by the platform.
Azure Storage Actions offers built-in observability:
- Preview circumstances permit prospects to validate logic in opposition to a subset of blobs earlier than execution
- Azure Monitor metrics observe process runs, focused objects, and profitable operations
- Execution reviews are generated as CSV recordsdata for every run, detailing:
- Blobs processed
- Actions carried out
- Execution standing for audit functions
This makes Storage Actions appropriate for situations the place traceability and evaluation are essential.
Shashank shared a number of examples of how prospects are utilizing Azure Storage Actions at the moment:
- Monetary providers: Making use of immutability and retention insurance policies to name recordings for compliance
- Airways: Value optimization by tiering or cleansing up blobs primarily based on creation time or dimension
- Manufacturing: One-time processing to reset or take away blob index tags on IoT-generated information
These situations vary from recurring automation to one-off operational duties.
Azure Storage Actions is offered in over 40 public Azure areas.
To be taught extra, take a look at:
For questions or suggestions, the crew could be reached at: storageactions@microsoft.com
