This content originally appeared on DEV Community and was authored by Oladosu Ibrahim
Introduction
In today’s digital workplace, managing internal company data securely and efficiently is just as important as keeping a public website online. Businesses rely on cloud storage not just for hosting static web content but for storing sensitive internal documents, sharing files with trusted partners, and optimizing storage costs over time.
Azure Storage makes all this possible with a few well-configured features. With the right setup, you can protect your files from regional outages, grant partners temporary access without risking your entire storage account, automate cost savings by moving rarely used data to cooler tiers, and even replicate files across accounts for backup.
In this guide, you’ll learn how to use Azure Storage to store and protect internal company documents with high availability, configure secure file sharing for partners, back up public website files, and manage storage costs with lifecycle policies. By the end, you’ll understand how to build a secure, redundant, and cost-effective storage solution all from the Azure portal.
Architecture Diagram
At its core, the setup includes:
- A private Azure Storage Account for sensitive company documents.
- Containers to organize files securely.
- Shared Access Signatures (SAS) to give partners temporary and limited file access.
- Object Replication to back up public website files into the private storage.
-
Lifecycle Management Rules to move old files to cheaper storage tiers automatically.
Skilling Tasks Overview
Here’s what you’ll accomplish:
- Create a storage account with high availability for private documents.
- Configure redundancy to handle regional failures.
- Restrict access using private containers.
- Generate secure shared access for partners.
- Back up public website files into the private account.
- Set up lifecycle rules to optimize storage costs.
Step 1: Create a Storage Account with High Availability
To start, create a storage account dedicated to your company’s private documents:
In the Azure portal, search for Storage accounts and select + Create.
Use the Resource group from your previous setup (e.g., from Lab 02a).
Name the storage account something unique, like privatecompanydocs123.
Click Review + Create, then Create.
Once deployed, select Go to resource.
Next, configure geo-redundancy to protect against regional outages:
- In your storage account, go to Data management > Redundancy.
- Choose Geo-redundant storage (GRS).
- Review the primary and secondary locations and Save.
This ensures your files remain available even if an entire Azure region fails.
Step 2: Create a Private Container and Upload a Test File
To store files securely:
- In your storage account, under Data storage, select Containers.
- Click + Container, name it sudais, and set Public access level to Private (no anonymous access).
- Click Create.
Upload a test file:
- Open the private container.
Click Upload, choose any small file (like an image or text file), and upload it.
Copy the file’s URL from its Overview tab, paste it into a browser, you should see an error. This confirms the file isn’t publicly accessible.
Step 3: Grant Secure Partner Access with a Shared Access Signature (SAS)
Suppose an external partner needs temporary read or write access to this file for the next 24 hours:
- In the container, select the uploaded file.
- Go to the Generate SAS tab.
- Set Permissions to only Read.
- Set the Start and Expiry times to cover the next 24 hours.
Click Generate SAS token and URL.
Copy the SAS URL and test it in a browser, you should be able to view or download the file.
A SAS URL limits what the partner can do and for how long — keeping your storage secure.
Step 4: Configure Lifecycle Management to Optimize Costs
Older files that aren’t frequently accessed shouldn’t stay in expensive storage tiers. Automate cost savings by moving them to the Cool tier:
In the storage account, check that the Default access tier is Hot.
Go to Data management > Lifecycle management.
Click Add rule, name it movetocool.
Scope: Apply to all blobs in the storage account.
Set Last modified > More than 30 days ago.
Action: Move to cool storage.
Click Add.
Now, files older than 30 days will automatically move to a cheaper tier — saving you money without manual work.
Step 5: Back Up Public Website Files with Object Replication
Finally, secure your public website by replicating its files into your private storage account:
- In your private storage account, create a new container named backup.
- Navigate to your publicwebsite storage account, this was created previously.
- Go to Data management > Object replication.
- Click Create replication rules.
- Set Destination storage account to your private account.
- Source container: public.
- Destination container: backup.
- Save the rule.
Optionally, upload a file to the public website’s container. After a few minutes, it will appear automatically in the private backup container — giving you peace of mind.
Conclusion
With Azure Storage, securing internal documents doesn’t require a complex setup. By combining geo-redundancy, private containers, shared access signatures, object replication, and lifecycle rules, you protect sensitive files, collaborate securely with partners, and keep storage costs under control.
This simple yet powerful configuration shows how cloud storage isn’t just for public websites, it’s an essential backbone for protecting your company’s most valuable files.
This content originally appeared on DEV Community and was authored by Oladosu Ibrahim