Azure Files is a great solution when you need shared file storage in the cloud — just like a network file share, but hosted and managed by Azure. In this guide, I’ll walk you through how to:
- Create a Premium Storage Account for Azure Files
- Set up a File Share with directories and uploaded files
- Enable Snapshots for recovery
- Restrict access using Virtual Networks
This is a perfect setup for teams like Finance, who need secure, high-performance, and recoverable shared storage.
📦 Step 1: Create the Azure Storage Account
- Go to the Azure Portal.
- Search for and select Storage accounts.
- Click + Create.
- Create a new resource group (e.g.,
storage-rg
). - Enter a unique name for the storage account (e.g.,
ezekielstorageaccount
). - Set:
- Performance: Premium
- Premium account type: File shares
-
Redundancy: Zone-redundant storage (ZRS)
- Click Review + Create, then Create.
- After deployment, click Go to resource.
✅ Why Premium? Premium storage gives low-latency and high-throughput — perfect for file sharing.
📁 Step 2: Create a File Share and Add Directory
- In your storage account, go to File shares under Data storage.
- Click + File share.
- Enter a name like
ezekiel-file-share
and click Create. - Once created, click the file share, then + Add directory.
- Name the directory
finance
.
💡 You can organize your file shares using folders, just like on a traditional file server.
⬆️ Step 3: Upload a File
- Open the
finance
directory. - Click Upload and choose any test file (e.g., a .txt or .pdf).
- Upload the file.
Now, your file share has a folder and a test file — ready to be backed up and secured.
🕒 Step 4: Enable and Test Snapshots
Snapshots in Azure Files help you restore previous versions of files or recover deleted files.
- Go to the file share → select the Snapshots tab under Operations.
- Click + Add snapshot → click OK.
- Select the snapshot and ensure your
finance
folder and file are included.
🧪 Test Restoring a File from Snapshot
- Go back to your file share → open the
finance
folder. - Delete the uploaded file (click the file → Delete → Yes).
- Return to the Snapshots tab → open the snapshot.
- Navigate to the deleted file → click Restore.
- Give it a new name (e.g.,
my-upload
) and restore. - Go back to your file share and confirm the restored file is there.
📌 Snapshots are point-in-time copies — great for protecting against accidental deletion.
🔐 Step 5: Restrict Access Using Virtual Network
Let’s now restrict access so that only users within a specific virtual network (VNet) can connect to this storage account.
🌐 Create a Virtual Network
- In the portal, search for Virtual networks → click + Create.
- Use your storage account’s resource group.
- Name it something like
storage-vnet
. - Click Review + Create, then Create.
🔁 Add a Service Endpoint
- After deployment, go to your VNet → Subnets.
- Click on the
default
subnet. - Under Service endpoints, select Microsoft.Storage.
- Click Save.
This allows the VNet to securely connect to Azure Storage.
🔒 Limit Access in the Storage Account
- Go back to your storage account → go to Networking under Security + networking.
- Set Public network access to: ➤ Enabled from selected virtual networks and IP addresses
- In the Virtual networks section, click Add existing virtual network.
- Choose
storage-vnet
and its default subnet → click Add. - Save your changes.
🔍 Step 6: Test the Security
Try accessing the file share from the Storage browser in the portal. You should see an error like:
❌ “Not authorized to perform this operation.”
This confirms your restriction is working — access is allowed only from inside your VNet.
✅ Summary
Here’s what we achieved:
Feature | Configuration |
---|---|
Storage Type | Premium, ZRS |
File Share |
corporate-share with finance folder |
Upload File | Test file uploaded |
Snapshots | Enabled and tested file recovery |
VNet Restriction | Access allowed only from finance-vnet
|
File Recovery | Manual restore from snapshot tested |
Azure Files is powerful when you want cloud-based shared folders with backup, access control, and high availability — all without managing servers. This setup is a great starting point for securely storing and managing corporate documents.
Top comments (0)