At exactly 9:42 AM, I got a message I’ve seen too many times:
“Please… I think I just deleted the finance report.”
Three weeks of teamwork gone in seconds.
No recycle bin, no undo button, report is gone.
The finance team was already preparing for a review meeting. That file wasn’t optional; it was everything.
And in that moment, you realize something:
It’s not about storage.
It’s about what happens when things go wrong.
Luckily, this wasn’t luck.
This was design.
Let me show you exactly how I built a system where mistakes don’t become disasters and how you can do the same.
Before we go hands-on, let’s break down a few key terms (in plain English):
Storage Account → Your cloud “hard drive” where everything lives.
Azure Files → A shared folder in the cloud that multiple people can access.
File Share → The main folder everyone connects to.
Directory → Subfolders to keep things organized (like “Finance”).
Snapshots → Backup copies of your data at a specific moment in time.
Virtual Network (VNet) → Your private, secure space in Azure.
Subnet → A smaller section inside your network.
Zone-redundant storage (ZRS) → Keeps copies of your data in different locations so you don’t lose it.
Now that you understand the “why,” let’s build the “how.”
Step 1: Creating the Foundation (Storage Account)
We start by creating the backbone of everything: our storage account.
In the Azure portal:
- Search for Storage accounts
- Click + Create
We create one for the finance team:
Resource Group — Your Project Container
A Resource Group is simply a logical container for your resources.
Naming the Storage Account
This must be globally unique (Azure requirement).
Performance Matters
Set performance to Premium.
Why? Because finance workloads need:
- Low latency
- High reliability
Account Type
We choose file shares because we’re building a shared file system—not blob storage.
Data Protection (Redundancy)
Set to Zone-redundant storage (ZRS).
This ensures:
- Your data exists in multiple physical locations
- Even if one zone fails, your data survives
Deploy
Review and create.
Wait for deployment, then go to the resource.
Step 2: Creating a Shared Space for the Corporate Office
Now we create a File Share—this is where collaboration happens.
Inside the storage account:
- Go to File shares
- Click + File share
Provide a name and create:
Step 3: Organizing with Directories
Now we create a finance directory.
Why? Because structure matters.
Navigate into it:
You can keep nesting directories:
Upload a test file:
Step 4: The Mistake (Why Snapshots Matter)
Here’s where reality hits.
Someone deletes a file.
No backup. No recovery.
This is where Snapshots save the day.
Creating a Snapshot
Snapshots are point-in-time backups.
Add snapshot:
Verify contents:
Step 5: Simulating Disaster (File Deletion)
Let’s delete the file:
Step 6: Recovery (The Hero Moment)
Go back to snapshot:
Restore the file:
And just like that…
Crisis avoided. Finance team happy. Reputation intact.
Step 7: Locking Down Access (Security First)
Now we enforce controlled access using a Virtual Network.
Create Virtual Network
Deploy it:
Go to resource:
Configure Subnet
Select default subnet:
Enable Microsoft.Storage service endpoint:
Restrict Storage Access
Now we allow access only from our VNet.
Add the virtual network:
Now:
- No public access
- Only trusted network traffic
- Finance data stays protected
