From Zero to Secure: Setting Up Azure Storage on My DevOps Journey

Emmanuel — Tue, 21 Apr 2026 12:03:35 +0000

Everyone starts somewhere. The goal was straightforward: Create a secure, cost-effective storage account in Azure using the guided Lab which you can find on Microsoft Learn. Think of it as setting up a digital locker where your data lives safely in the cloud.
Here is what I did, what I learned, and why it matters.

Step 1: Creating a Resource Group

Before building anything, I needed somewhere to put it. In Azure, that's a resource group essentially a logical container that keeps related resources organized and easy to manage. It is a small step, but a foundational one. Good organization now saves headaches later.

Resource group creation in Azure Portal- can be found for searching the portal and selecting it

Step 2: Setting Up the Storage Account

Next came the storage account itself the actual "locker." Azure storage accounts can hold blobs, files, queues, and tables. For this lab, I focused on understanding the configuration options: naming conventions, region selection, and performance tiers.
It is surprisingly satisfying clicking through a wizard and watching a cloud resource come to life.

Storage account created in Azure Portal with a unique name.

Step 3: Locking It Down — Security Settings

This was the most important part. I applied three key security configurations:
• Secure transfer only — enforces HTTPS, rejecting any plain HTTP connections
• Minimum TLS version — set to TLS 1.2 to block outdated, vulnerable protocols
• Shared key access disabled — forces authentication through Azure Active Directory instead of less secure key-based access

These are not optional extras — they are baseline hygiene for any cloud storage setup.

Step 4: Redundancy and Networking

Since this was a training lab, I made practical trade-offs:
• Redundancy: I chose Locally Redundant Storage (LRS), which is the most affordable option, suitable for non-critical data.
• Networking: I kept public network access enabled to allow the lab tasks to run without friction.

In a production environment, I will likely switch to geo-redundant storage and lock down network access to specific virtual networks or private endpoints. But knowing why you'd make that change is exactly what lab like this teaches you.
Redundancy and networking configuration

This lab was not about storing real data — it was about building a mental model. I now understand how to spin up a storage account, apply security best practices, and make informed trade-offs between cost, redundancy, and access control.

If you are just starting out with Azure, I would encourage you to follow along with the hands-on labs. There is no better way to learn than by actually doing.
What is next? I am moving on to Azure networking and virtual machines. Follow along if you are on a similar journey.

DEV Community: Emmanuel

From Zero to Secure: Setting Up Azure Storage on My DevOps Journey