🧠 Introduction
In cloud engineering, storage is one of the most essential building blocks. Whether it’s hosting application data, training environments, or prototypes, every department needs flexible and secure storage options that can adapt to their needs.
In this exercise, I worked on a hands-on project for an IT department that needed a simple and changeable storage setup for testing and training purposes. The data wasn’t business-critical — meaning backups and recovery weren’t a major concern — but the goal was to prototype different storage scenarios and train new personnel efficiently.
To achieve this, I designed a lightweight cloud storage configuration using Microsoft Azure Storage, focusing on three key steps:
- Establishing a consistent **naming co…
🧠 Introduction
In cloud engineering, storage is one of the most essential building blocks. Whether it’s hosting application data, training environments, or prototypes, every department needs flexible and secure storage options that can adapt to their needs.
In this exercise, I worked on a hands-on project for an IT department that needed a simple and changeable storage setup for testing and training purposes. The data wasn’t business-critical — meaning backups and recovery weren’t a major concern — but the goal was to prototype different storage scenarios and train new personnel efficiently.
To achieve this, I designed a lightweight cloud storage configuration using Microsoft Azure Storage, focusing on three key steps:
- Establishing a consistent naming convention,
- Creating a storage account, and
- Configuring basic security and networking settings.
This project helped me understand how easy it is to create flexible, scalable storage in the cloud — and why good naming and security practices are crucial even for test environments.
Create and deploy a resource group to hold all your project resources
-
In the Azure portal, search for and select Resource groups
-
Select + Create.
-
Give your resource group a name. For example, storagerg and Select a region. Use this region throughout the project.
-
Select Review and create to validate the resource group
-
Select Create to deploy the resource group.
Create and deploy a storage account to support testing and training.
In the Azure portal, search for and select Storage accounts. 1.
Select + Create.
-
On the Basics tab, select your Resource group.
-
Provide a Storage account name( The storage account name must be unique in Azure), Set the Performance to Standard and Select Review, and then Create.
-
Wait for the storage account to deploy and then Go to resource.
Configure simple settings in the storage account The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired.
-
In your storage account, in the Data management section, select the Redundancy blade.
-
Select Locally-redundant storage (LRS) in the Redundancy drop-down.
-
Be sure to Save your changes.
-
Refresh the page and notice the content only exists in the primary location.
The storage account should only accept requests from secure connections.
- In the Settings section, select the Configuration blade.
- Ensure Secure transfer required is Enabled.
Developers would like the storage account to use at least TLS version 1.2.
- In the Settings section, select the Configuration blade.
- Ensure the Minimal TLS version is set to Version 1.2.
Until the storage is needed again, disable requests to the storage account
- In the Settings section, select the Configuration blade.
- Ensure Allow storage account key access is Disabled.
- Be sure to Save your changes.
Ensure the storage account allows public access from all networks
- In the Security + networking section, select the Networking blade.
- Ensure Public network access is set to Enabled from all networks
- Be sure to Save your changes.
Completing this exercise helped me strengthen my understanding of Azure storage fundamentals. Each step — from naming conventions to configuring security — brought me closer to thinking like a cloud engineer.
Stay tuned for Exercise 2, where I’ll take the next step in my cloud journey!