DEV Community

Cover image for Introduction to Azure Storage
Wilfred Andrew Delamy
Wilfred Andrew Delamy

Posted on

Introduction to Azure Storage

What is Azure Storage?

Azure Storage is Microsoft’s cloud-based solution for storing data securely, reliably, and at scale. It provides a range of services that handle everything from unstructured files to structured tables, enabling organizations to store, access, and manage their data seamlessly across the globe.

Think of it as a digital warehouse in the cloud that is flexible enough to store massive amounts of information, yet smart enough to deliver performance, security, and redundancy.

Benefits of Azure Storage

  • Scalability: Store petabytes of data without worrying about hardware limitations.
  • High Availability: Built-in redundancy ensures your data is always accessible, even during outages.
  • Security: Encryption, role-based access, and secure transfer options protect sensitive information.
  • Cost Efficiency: Pay only for what you use, with tiered pricing models to optimize costs.
  • Global Reach: Data centers worldwide allow you to store data close to your users for faster access.

Types of Azure Storage Service

Types of Azure Storage Services

Storage Account Settings

When creating an Azure Storage account, several key settings determine how your data is stored, accessed, and protected.

Subscription: The billing container that ties your storage account to your Azure plan.

Location: Choose the Azure region where your data physically resides. This impacts latency and compliance.

Performance:

  • Standard: HDD-based, cost-effective for general workloads.
  • Premium: SSD-based, optimized for low-latency, high-performance needs.

Redundancy: Azure Storage always stores at least three copies of your data to protect it from planned and unplanned events. Redundancy ensures that your storage account meets its availability and durability targets even in the face of failures.
Options include:

  • LRS (Locally Redundant Storage): Azure keeps three copies of your data in the same data center (single location). LRS is best for backups or test data, workloads where data can be recreated, and low-cost storage needs. Some limitations of LRS are: data is not protected against data center outages, and it has the lowest durability among the options (still extremely high by global standards).
    LRS Replication

  • ZRS (Zone Redundant Storage): Azure keeps three copies of your data across three different physical datacenters (Availability Zones) within the same region. ZRS is best for production workloads that need higher availability, protection against zone-level failures, and applications that require consistent read/write access even if one AZ is down. Some limitations include the data being limited to one region and not protecting against complete regional outages.
    ZRS Replication

  • GRS (Geo-Redundant Storage): Azure keeps three copies of your data in the primary region and three synchronous copies in the paired secondary region (total of 6 copies). GRS is best for disaster recovery scenarios, ensuring durability even if the entire primary region fails, and for applications where write access doesn't need to fail over automatically. Some limitations are that the secondary region is not readable, and failover is manual (you trigger it during a disaster).
    GRS Replication

  • RA-GRS (Read-Access Geo-Redundant Storage): Azure makes 6 copies of your data as GRS, but you can read from the secondary region anytime. It is best for applications that need global read distribution, analytics reading from the secondary region and extra resiliency for read-heavy workloads. Some of its limitations are: writes still go only to the primary region, and the secondary region still requires manual failover for write access.
    RA-GRS Replication

Summary for Redundancy

  • LRS → Basic local protection
  • ZRS → Multi–data-center protection within one region
  • GRS → Protection across regions
  • RA-GRS → GRS + read access to the secondary region

Access Tier:

  • Hot tier: Frequently accessed and modified data. The Hot tier has the highest storage costs, but the lowest access costs.
  • Cool tier: Infrequently accessed or modified data that needs to be retrieved quickly. Microsoft recommends that data in the cool tier be stored for at least 30 days. The cool tier has lower storage costs but higher access costs than the hot tier.
  • Cold tier - rarely accessed or modified data that still requires fast retrieval. Microsoft recommends that data in the cold tier be stored for at least 90 days. The cold tier has lower storage costs but higher access costs than the cool tier.
  • Archive tier: Rarely accessed data, lowest cost, but retrieval takes time. Microsoft recommends that data in the archive tier be stored for at least 180 days.
  • Smart tier - Smart tier automatically moves your data between the hot, cool, and cold access tiers based on usage patterns, optimizing your costs for these access tiers automatically.

Secure Transfer Required: Enforces HTTPS connections to protect data in transit.
Virtual Networks: Restrict access to your storage account by integrating with Azure VNets, ensuring only trusted resources can connect.

Final Thoughts

Azure Storage is more than just a cloud hard drive. It is a powerful storage that supports modern applications, analytics, and enterprise workloads. By understanding its services and settings, organizations can design storage solutions that are secure, scalable, and cost-effective.

Whether you’re storing terabytes of video, managing IoT sensor data, or simply migrating shared drives to the cloud, Azure Storage has a tailored option for you.

Question of the Day:

If you had to choose just one Azure Storage service to power a global application with unpredictable traffic and diverse data types, i.e. Blog, File Share, Queue, or Table, which would you pick and why?

Top comments (3)

Collapse
 
joshua_fe9e97108ad35e33e7 profile image
Joshua

Thanks for the detailed explanation. I'll definitely checked back on this as I'm developing my project

Collapse
 
delamywa profile image
Comment deleted
Collapse
 
joshua_fe9e97108ad35e33e7 profile image
Joshua

Thank you, Wilf

Some comments may only be visible to logged-in visitors. Sign in to view all comments.