AZURE STORAGE ACCOUNT - REDUNDANCY AND REPLICATION - SECURITY AND ACCESS CONTROL
When we talk about Storage in Microsft Azure, we basically taking about wearhouse where resources are kept in the Cloud…… So it will be right to say
Azure Storage is Microsoft's cloud storage facility that’s scalable, durable and secure.
STORAGE ACCOUNT TYPES AND PERFORMANCE TIERS
When you create a Storage Account in Azure, you must choose its type and performance level. This determines what services you can use and how fast data will be accessed which are of different Types
I.⭐STANDARD - This is recommended for most (Standard General Purpose v2 (GPv2))
Blobs, Files, Queues, Tables. Perfect for almost everything: websites, backups, documents, log
II.⚡PREMIUM - High Performance Premium Block Blobs Block Blobs only. Used when you need extremely fast read and write speeds, think AI training data or video processing.
Uses Solid State Drives (SSD). Fast but cost
III.🚀 PREMIUM - Fast File Shares Premium File Shares Azure Files only. For enterprise apps
that need very low-latency access to shared files. SSD-backed file shares.
For storage to be possible, there must be a warehouse which is called (Azure Storage Account) inside which we have four(4) core data storage services which are :—
Blob - Store unstructured data (Can store anything in Cloud)
File - A fully managed cloud file share that your computers can connect to
Queue - This allows different parts of your application to send small messages to each other and
Table - Great for logging, user preferences, and lightweight datasets.
Each of the above are built to handle a completely different type of data and workload, according to there importance and priorities
NB: -
Account names must be globally unique, 3 to 24 characters, lowercase letters and numbers only, and the name becomes part of your URL.
BLOB STORAGE - Store Anything In The Cloud
The Most Versatile Storage in Azure
A Blob (Binary Large Object) is simply any file, an image, a PDF, a video, a ZIP
archive, a database backup, or even a custom binary file from your application.
Blob Storage is designed to hold massive amounts of these unstructured files.
Netflix-like video streaming services, social media platforms, and backup solutions
all rely on Blob Storage.
THE THREE-LEVEL HIERARCHY:
Blobs follow a three-level hierarchy: Storage Account → Container → Blob.
The cost lever is the access tier:
BLOB ACCESS TIERS: CONTROL YOUR COSTS
🔥HOT TIER - best for Frequently accessed data. Active images on a website, current user profile photos, data processed daily.
RETRIEVAL - Immediate
Highest storage cost, lowest access cost
❄COOL TIER - best for Infrequently accessed data stored for at least 30 days. Monthly
reports, old backup copies, archived project files.
RETRIEVAL - Immediate
Lower storage cost, slightly higher access cost.
🧊COLD TIER - Best For Rarely accessed data stored for at least 90 days. Old logs, compliance data, media files no longer in active use.
RETRIEVAL - Immediate
Very low storage cost, higher access cost
📦ARCHIVE TIER - Best For data that might never be accessed again but must be kept for legal or compliance reasons. Stored for at least 180 days.
RETRIEVAL - Hours (must rehydrate first)
Lowest storage cost, highest retrieval cost
Now lets talk about other Storage Services in Azure
FILES
Azure Files replaces that physical server with a fully managed cloud version. Your
laptop, your colleague's laptop in Lagos, and your manager's computer in London can
all connect to the same shared file location from anywhere in the world, over the
internet.
QUEUES
Queues decouple your app. A producer drops a message (up to 64 KB) in the queue, and a consumer picks it up later. Messages can be hidden while being processed, which prevents duplicate work.
TABLES
Tables store entities (rows) identified by a PartitionKey + RowKey pair. Each entity can have different properties, with no fixed schema. They're great for logs, configurations, and user data, but not for complex joins. Reach for SQL when you need those.
REDUNDANCY AND REPLICATION: (This prevent you from Data loss)
Microsoft Azure does not keep just one copy. It always keeps multiple copies to protect against hardware failure, power outages, natural disasters, and data centre fires. The number and location of copies depends on the replication option you choose when creating
your Storage Account.
🏢 LRS (Locally Redundant Storage) - Keeps 3 copies
Location: Same data centre, Three copies of your data are kept within one single data centre.
Cheapest option. Protects against hardware failure but not against a building fire or flood.
🏙 ZRS (Zone Redundant Storage) - Keeps 3 copies
Location: 3 Availability Zones, three copies are spread across three separate physical buildings (zones) within the same region (e.g., within Lagos or Johannesburg). Protects against a data centre going down.
🌍GRS (Geo-Redundant Storage ) - Copies: 6 copies
Location: 2 regions (LRS × 2) Six total copies: three in your primary region and three more in a secondary region hundreds of kilometres away. Your go-to for disaster recovery.
🌐GZRS (Geo-Zone Redundant Storage ) - Copies: 6 copies
Location: 3 zones + paired region the highest protection. Combines ZRS (zone spreading) in the primary region with geo-replication to a secondary region. Most expensive but near-zero data loss.
SECURITY AND ACCESS CONTROL:
By default, all data in Azure Storage is private. Nobody can access your blobs, files, or tables without proper authorisation.
🔑-Storage Account Keys
Full access to everything. Never share them, and rotate them.
📜-Shared Access Signatures (SAS)
Temporary, scoped URLs. You control the resource, permissions, start and expiry time, IP range, and HTTPS-only. Expired tokens return a 403.
🛡-Azure Active Directory (Entra ID)
Roles like “Storage Blob Data Reader” or “Contributor”. This is the recommended approach for internal users and apps, and it needs no keys.
🌍 - Anonymous Public Access - isabled by default, and only worth enabling on purpose (e.g. public static assets).
Bonus: Hands-on Lab/Demo hosting a static website on Blob Storage
Top comments (0)