Securing Corporate Data: Azure Storage Private Access & Lifecycle Management
Introduction
In cloud architecture, managing internal company documents requires a different strategy than public assets. You must prioritize high availability while strictly limiting access to authorized users. This guide covers how to set up a private storage account with Geo-redundant storage (GRS), implement temporary access using Shared Access Signatures (SAS), and optimize costs using automated lifecycle management. By the end, you will also learn how to create an automated backup using Object Replication between storage accounts.
Create a storage account and configure high availability.
Create a storage account for the internal private company documents.
In the portal, search for and select Storage accounts.
Select + Create.
Select the Resource group created in the previous lab.
Set the Storage account name to private. Add an identifier to the name to ensure the name is unique.
Select Review, and then Create the storage account.
Wait for the storage account to deploy, and then select Go to resource.
- This storage requires high availability if there’s a regional outage. Read access in the secondary region is not required. Configure the appropriate level of redundancy.
In the storage account, in the Data management section, select the Redundancy blade.
Ensure Geo-redundant storage (GRS) is selected.
Refresh the page.
Review the primary and secondary location information.
Save your changes.
Create a storage container, upload a file, and restrict access to the file.
- Create a private storage container for the corporate data.
In the storage account, in the Data storage section, select the Containers blade.
Select + Container.
Ensure the Name of the container is private.
Ensure the Public access level is Private (no anonymous access).
As you have time, review the Advanced settings, but take the defaults.
Select Create.
- For testing, upload a file to the private container. The type of file doesn’t matter. A small image or text file is a good choice. Test to ensure the file isn’t publically accessible.
Select the container.
Select Upload.
Browse for files and select a file.
Upload the file.
Select the uploaded file.
On the Overview tab, copy the URL.
Paste the URL into a new browser tab.
Verify the file doesn’t display and you receive an error.
- An external partner requires read and write access to the file for at least the next 24 hours. Configure and test a shared access signature (SAS). Learn more about Shared Access Signatures.
Select your uploaded blob file and move to the Generate SAS tab.
In the Permissions drop-down, ensure the partner has only Read permissions.
Verify the Start and expiry date/time is for the next 24 hours.
Select Generate SAS token and URL.
Copy the Blob SAS URL to a new browser tab.
Verify you can access the file. If you have uploaded an image file it will display in the browser. Other file types will be downloaded.
Configure storage access tiers and content replication.
- To save on costs, after 30 days, move blobs from the hot tier to the cool tier. Learn more how manage the Azure Blob storage lifecycle.
- Return to the storage account.
In the Overview section, notice the Default access tier is set to Hot.
In the Data management section, select the Lifecycle management blade.
Select Add rule.
Set the Rule name to movetocool.
Set the Rule scope to Apply rule to all blobs in the storage account.
Select Next.
Ensure Last modified is selected.
Set More than (days ago) to 30.
In the Then drop-down select Move to cool storage.
As you have time, review other lifecycle options in the drop-down.
Add the rule.
- The public website files need to be backed up to another storage account. Learn more about object replication.
In your storage account, create a new container called backup. Use the default values. Refer back to Lab 02a if you need detailed instructions.
Navigate to your publicwebsite storage account. This storage account was created in the previous exercise.
In the Data management section, select the Object replication blade.
Select Create replication rules.
Set the Destination storage account to the private storage account.
Set the Source container to public and the Destination container to backup.
-
Create the replication rule.
Conclusion
By following these steps, you have secured your corporate documents while maintaining a cost-effective and resilient architecture. Implementing GRS ensures your data survives regional incidents, while Private access levels and SAS tokens ensure only authorized parties can view sensitive content. Additionally, with Lifecycle Management and Object Replication in place, your data is now both cost-optimized and backed up automatically. These settings form a professional foundation for enterprise-grade storage management in Azure.
Top comments (1)
Nice