Forem: adegbola adeniyi

Azure CLI: Setup Linux VM, VNet, Storage & Key Vault with Budget Alerts—A Comprehensive Step-by-Step Infrastructure Guide.

adegbola adeniyi — Mon, 20 Apr 2026 10:10:35 +0000

Introduction

Cloud computing has revolutionized how developers and IT professionals build, deploy, and manage applications. Among the leading platforms, Microsoft Azure stands out for its flexibility, scalability, and powerful infrastructure services. Whether you’re experimenting with Linux environments, hosting applications, or designing complex network architectures, Azure provides the tools to make it seamless.

In this guide, we’ll walk through the step-by-step process of creating a Linux Virtual Machine (VM) on Azure and then configuring a Virtual Network (VNet) with a Subnet using the Azure Command-Line Interface (CLI). By the end, you’ll not only understand how to spin up a Linux VM but also how to establish secure and organized network structures that support enterprise-grade applications.

Before diving in, it’s important to understand one of Azure’s fundamental concepts: the Resource Group.

A Resource Group in Azure is a logical container that holds related resources for an application or workload. It allows you to manage and organize resources such as VMs, storage accounts, and networks collectively, making deployment, monitoring, and lifecycle management much easier. Think of it as a folder where all the components of your project live together.

This tutorial is designed for beginners and intermediate users who want hands-on experience with Azure’s infrastructure services. No prior deep knowledge of cloud networking is required—just a willingness to learn and follow along.

This tutorial is broken down into several steps:

Step 1: Installing Azure Package Manager, Logging-in Into Azure Portal and Setting up Our Subscription

winget install Microsoft.AzureCLI: Installs the Azure CLI tool using the Windows package manager (winget).

az login --use-device-code: logs you into Azure by generating a temporary device code that you enter in a browser, allowing secure authentication without needing to store credentials directly in the terminal.

az account show: displays details about the currently active Azure subscription and account context, including subscription ID, name, tenant ID, and whether it’s set as the default.

Step 2: Setting Up and Creating a Resource Group for holding, organizing and managing all related Resources meant for this Project

RG=az-cli-lab-rg: defining a shell variable named RG with the value az-cli-lab-rg.
LOCATION=eastus: defining a shell variable named LOCATION with the value eastus
az group create --name $RG --location $LOCATION: - --name $RG specifies the name of the resource group (in this case, the value stored in the variable RG, e.g., az-cli-lab-rg).
--location $LOCATION defines the Azure region where the resource group will be hosted (e.g., eastus).

az group show --name $RG:is used to retrieve and display details about an existing Azure Resource Group.

Step 3: Setting up Virtual Network, Sub Network, NSG and creating the inbound security rules(SSH and Https) and Allocating a Public IP.

az network vnet create: Creates a new Virtual Network.
--resource-group $RG: Specifies the resource group where the VNet will be placed (using the variable RG).
--name lab-vnet: Names the VNet lab-vnet
--address-prefix 10.0.0.0/16: - Defines the IP address space for the VNet. Here, it allows addresses from 10.0.0.0 to 10.0.255.255.
--location $LOCATION: Sets the Azure region where the VNet will be created (using the variable LOCATION).

az network vnet subnet create: Creates a new subnet within a specified VNet.
--resource-group $RG: Identifies the resource group where the VNet and subnet reside.
--vnet-name lab-vnet: Specifies the VNet (lab-vnet) in which the subnet will be created.
--name lab-subnet: - Names the subnet lab-subnet.
--address-prefix 10.0.1.0/24:- Defines the IP address range for the subnet. Here, it allows 256 addresses (from 10.0.1.0 to 10.0.1.255).

az network nsg create: Creates a new Network Security Group (NSG) in Azure.
--resource-group $RG: Specifies the resource group where the NSG will be created.
--name lab-nsg: Names the NSG lab-nsg.

az network nsg rule create: Adds a new rule to the NSG.
--resource-group $RG: Resource group where the NSG resides.
--nsg-name lab-nsg: Target NSG name.
--name AllowSSH / AllowHTTP: Names of the rules.
--priority 1000/1010: Determines rule order (lower = higher priority).
--destination-port-ranges 22 SSH Access /80 HTTP Access: Ports being opened
--access Allow: Grants access (instead of denying).
--protocol Tcp: Protocol type.
--direction Inbound: Applies to incoming traffic.

az network vnet subnet update*: Updates the configuration of an existing subnet.
*--resource-group $RG: Specifies the resource group where the subnet and NSG exist.
--vnet-name lab-vnet: Identifies the Virtual Network containing the subnet.
--name lab-subnet: The subnet being updated.
--network-security-group lab-nsg: - Associates the NSG (lab-nsg) with the subnet.

az network public-ip create: The base command to create a public IP in Azure.
--resource-group $RG:- Specifies the resource group where the public IP will be created. $RG is a variable holding the resource group name.
--name lab-public-ip: Assigns the name lab-public-ip to the new public IP resource.
--allocation-method Static: Ensures the IP address is static, meaning it won’t change once assigned (as opposed to dynamic allocation).
--sku Standard: creates a more reliable, secure, and scalable public IP address. No zone redundancy, limited security features.

Step 4: Creating a VM, SSH into your VM & install Nginx
Creates a B1s Ubuntu VM with auto-generated SSH keys and connects it to the existing subnet and firewall.

az vm create: Creates a new virtual machine.
--resource-group $RG: Deploys the VM into the resource group stored in the variable.
--name lab-vm:- Names the VM lab-vm.
--image Ubuntu2204: Uses the Ubuntu 22.04 LTS image.
--size Standard_B1s: Chooses a small, cost-effective VM size (1 vCPU, 1 GiB RAM).
--admin-username azureuser: Sets the admin account username.
--generate-ssh-keys: Automatically generates SSH keys if none exist locally.
--vnet-name lab-vnet: Places the VM in the virtual network lab-vnet.
--subnet lab-subnet: Assigns the VM to the subnet lab-subnet.
--public-ip-address lab-public-ip: Associates the VM with the public IP resource lab-public-ip.
--nsg lab-nsg:Attaches the network security group lab-nsg for traffic rules.

az vm show: Displays information about an existing VM.
--resource-group $RG: Specifies the resource group where the VM resides.
--name lab-vm: Targets the VM named lab-vm.
--show-details: Includes additional details like networking and power state.
--query '{Name:name, State:powerState, IP:publicIps}': Uses JMESPath query syntax to filter and return only:The VM’s name, - The VM’s current power state (e.g., VM running, VM stopped), The public IP address assigned.
--output table: Formats the result into a human-readable table.

ssh -i ~/.ssh/id_rsa azureuser@102.37.12.118: Connects securely to your VM using the private
sudo apt update && sudo apt install nginx -y: Refreshes the package index and installs Nginx web server automatically ( skips confirmation).
sudo systemctl enable nginx && sudo systemctl start nginx curl http://102.37.12.118: Ensures Nginx starts on boot. Immediately starts the Nginx service.

Step 5: Create a Storage Account, Upload Files, Store Secrets in Azure Key Vault

STORAGE_NAME="labstorage$RANDOM": Creates a unique name by appending a random number to . Storage account names must be globally unique and lowercase.
az storage account create : Creates a new storage account.
--name $STORAGE_NAME : Uses the variable you defined above.
--resource-group $RG : Places the storage account in your resource
--location $LOCATION :Specifies the Azure region (e.g.,South Africa North).
--sku Standard_LRS : Chooses locally redundant storage (cost‑effective, three copies in one datacenter).
--kind StorageV2: Creates a modern general‑purpose v2 storage account (recommended for most workloads).

Create a Blob Container

az storage container create : Creates a new blob container.
--name lab-files : Names the container lab-files.
--account-name $STORAGE_NAME : Uses the storage account you created earlier.
--auth-mode login: Authenticates using your Azure CLI login credentials (instead of needing an access key).

Upload a FIle

echo 'Hello from Azure CLI Lab!' > sample.txt: Writes the string Hello from Azure CLI Lab! into a new file called in your current directory.
az storage blob upload : Uploads a file into an Azure Storage Blob container.
--account-name $STORAGE_NAME : Specifies the storage account you created earlier.
--container-name lab-files : Targets the blob container named lab-files.
--name sample.txt : Sets the blob’s name in Azure (what it will be called once uploaded).
--file sample.txt : Points to the local file you just created.
--auth-mode login: Uses your Azure CLI login credentials (Azure AD) for authentication instead of an account key.
NB: before you can upload a file, you need to assign role permission the user.

List blobs in the container

az storage blob list : Lists blobs (files) stored in a container.
--account-name $STORAGE_NAME : Specifies the storage account.
--container-name lab-files : Targets the container named lab-files.
--auth-mode login : Uses your Azure AD login credentials for authentication.
--output table: Formats the output in a clean table view.

Create a Key Vault

KV_NAME="lab-kv-$RANDOM": Creates a variable for the Key Vault name. The suffix ensures uniqueness since Key Vault names must be globally unique.
az keyvault create : Command to create a new Azure Key Vault resource.
--name $KV_NAME : Uses the variable you defined as the Key Vault’s name.
--resource-group $RG : Places the Key Vault inside the resource group you specify.
--location $LOCATION : pecifies the Azure region (e.g., , ) where the Key Vault will be created.
--enable-rbac-authorization false: Disables Role-Based Access Control (RBAC) authorization for this Key Vault. Instead, it will use the traditional Access Policies model to control who can access secrets, keys, and certificates.

Store a Secret

az keyvault secret set : Command to create or update a secret in Azure Key Vault.
--vault-name $KV_NAME : Specifies which Key Vault to store the secret in (using the variable you defined earlier).
--name db-password : The logical name (identifier) for the secret. In this case, it’s called db-password.
--value 'SuperSecure@pass123':

Retrieve the secret

az keyvault secret show : Retrieves details of a secret stored in Azure Key Vault.
--vault-name $KV_NAME : Specifies which Key Vault to query (using the variable you defined earlier).
--name db-password : Identifies the secret you want to fetch, in this case db-password.
--query value : Filters the output to return only the secret’s value (instead of the full JSON object).
--output tsv: Formats the result as plain text (tab‑separated values), which means you’ll just see the secret string itself without extra formatting.

Assign VM a Managed Identity to access the vault

az vm identity assign :- Enables a system‑assigned managed identity for your VM.
--resource-group $RG \
--name lab-vm
PRINCIPAL_ID=$(az vm show \
--query identity.principalId \
--output tsv)
az role assignment create \
--role 'Key Vault Secrets User' \
--assignee $PRINCIPAL_ID \
--scope $(az keyvault show --name $KV_NAME --query id --output tsv).

Monitor Cost & Set a budget Alert

az consumption budget create :
--name lab-budget :The budget’s name.
--amount 100 : Spending limit (in your subscription’s currency).
--category Cost : Tracks actual cost (instead of usage).
--time-grain Monthly :Resets every month.
--start-date $(date +%Y-%m-01) : Defines the active period for the budget.
--end-date 2026-12-31 :Defines the active period for the budget.
--resource-group $RG :Scope the budget to a specific resource group.

Conclusion
By following this step‑by‑step guide, you’ve seen how the Azure CLI can be used to provision a Linux virtual machine, configure networking with VNets and subnets, set up a storage account for file management, securely store sensitive information in Azure Key Vault, and establish cost monitoring through budget alerts. Together, these tasks demonstrate the power of Azure’s integrated services: infrastructure, security, and governance working seamlessly through command‑line automation.
The process not only equips you with practical skills for deploying and managing cloud resources but also highlights best practices—such as using managed identities for secure access and leveraging budgets to maintain financial control. With these foundations in place, you can confidently expand into more advanced scenarios, knowing that your environment is secure, scalable, and cost‑aware. This holistic approach ensures that your Azure deployments remain both technically robust and operationally sustainable.

Complete Walkthrough to Setup Shared File Storage and Securing it Through a Virtual Network on Azure for Offices.

adegbola adeniyi — Mon, 09 Mar 2026 14:58:30 +0000

Introduction

Modern offices rely heavily on shared file storage to enable collaboration, streamline workflows, and ensure that critical documents are accessible to the right people at the right time. However, with increasing cyber threats and stricter compliance requirements, simply storing files in the cloud is not enough—organizations must also secure their storage environments against unauthorized access. Microsoft Azure provides a powerful platform for creating shared file storage that is both scalable and secure. By integrating Azure Files with a virtual network, businesses can enforce private connectivity, apply granular access controls, and protect sensitive data from external exposure.

This article offers a complete walkthrough of how to set up:

A storage account.
Configure a file share and directory.
Configure snapshots and practice restoring files.
Restrict access to a specific virtual network and subnet. on Azure, giving offices a reliable foundation for collaboration while maintaining the highest standards of data protection.

1. Create and configure a storage account for Azure Files.
Create a storage account for the finance department’s shared files.

In the portal, search for and select Storage accounts.

Select + Create.

For Resource group select Create new. Give your resource group a name and select OK to save your changes. Provide a Storage account name. Ensure the name meets the naming requirements. Set the Performance to Premium. Set the Premium account type to File shares. Set the Redundancy to Zone-redundant storage. Select Review and then Create the storage account. Wait for the resource to deploy.

Select Go to resource.

2. Create and configure a file share with directory.
Create a file share for the corporate office.

In the storage account, in the Data storage section, select the File shares blade. Select + File share and provide a Name.

Review the other options, but take the defaults. Select Create.

Add a directory to the file share for the finance department. For future testing, upload a file.

In the storage account, in the Data storage section, select the File shares blade. Name the new directory finance.Notice you can Add directory to further organize your file share. Upload a file of your choosing.

3. Configure and test snapshots.
Similar to blob storage, you need to protect against accidental deletion of files.

Select your file share. In the Operations section, select the Snapshots blade. Select + Add snapshot.

The comment is optional. Select OK. Select your snapshot and verify your file directory and uploaded file are included.

Practice using snapshots to restore a file.

Return to your file share. Browse to your file directory. Locate your uploaded file and in the Properties pane select Delete. Select Yes to confirm the deletion.

Select the Snapshots blade and then select your snapshot. Navigate to the file you want to restore, Select the file and the select Restore. Provide a Restored file name. Verify your file directory has the restored file.

4. Configure restricting storage access to selected virtual networks.
This tasks in this section require a virtual network with subnet. In a production environment these resources would already be created.

Search for and select Virtual networks.

Select Create. Select your resource group. and give the virtual network a name. Take the defaults for other parameters, select Review + create.

Then Create. Wait for the resource to deploy.

Select Go to resource.

In the Settings section, select the Subnets blade. Select the default subnet. In the Service endpoints section choose Microsoft.Storage in the Services drop-down. Do not make any other changes. Be sure to Save your changes.

The storage account should only be accessed from the virtual network you just created. Learn more about using private storage endpoints..

Return to your files storage account.
In the Security + networking section, select the Networking blade.

Change the Public network access to Enabled from selected virtual networks and IP addresses. In the Virtual networks section, select Add existing virtual network. Select your virtual network and subnet, select Add. Be sure to Save your changes.

Select the Storage browser and navigate to your file share.
Verify the message not authorized to perform this operation. You are not connecting from the virtual network.

This walkthrough has shown how to provision shared file storage on Azure and lock it down using a virtual network, role-based access, and encryption—turning a basic file share into a secure, manageable service for office environments. By combining correct resource configuration, network isolation, and least-privilege access controls, you reduce exposure to external threats while preserving the performance and collaboration benefits of centralized storage.
To keep the solution resilient, adopt automation for deployment, enable logging and monitoring, and schedule regular reviews of network rules and access policies. These operational practices, together with periodic backups and patching, ensure the environment remains secure and compliant as your organization grows. Implementing the steps in this guide will give your offices a reliable, secure shared storage foundation that scales with your needs.

Steps to Provide private storage for internal company documents

adegbola adeniyi — Fri, 27 Feb 2026 20:29:37 +0000

Introduction

Securing internal company documents is a cornerstone of modern business operations. With sensitive information such as financial records, employee data, and strategic plans at stake, organizations must ensure that storage solutions are both private and compliant. Microsoft Azure offers a robust platform for building secure, scalable, and controlled environments where internal documents can be stored and accessed safely. By following structured steps—ranging from setting up private storage accounts to configuring access policies and encryption—companies can create a reliable system that protects critical data while enabling authorized collaboration.

This article outlines the essential steps to establish private storage for internal documents on Azure, helping businesses strengthen their information security posture and meet regulatory requirements with confidence.

1. Create a storage account and configure high availability.
Step 1
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.

Then Create the storage account.

Wait for the storage account to deploy, and then select Go to resource.

Step 2
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.

2. Create a storage container, upload a file, and restrict access to the file.
Step 1
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 e.g. privatect06. Ensure the Public access level **is **Private (no anonymous access). As you have time, review the Advanced settings, but take the defaults. Select Create.

Step 2
For testing, upload a file to the private container. he 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 to 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.

Step 3
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).

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.

3. Configure storage access tiers and content replication.
Step 1
To save on costs, after 30 days, move blobs from the hot tier to the cool tier.

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.

Step 2
The public website files need to be backed up to another storage account.

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 (you could create a new one or any previous storage created before) storage account. 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. Optionally, as you have time, upload a file to the public container. Return to the private storage account and refresh the backup container. Within a few minutes your public website file will appear in the backup folder.

Conclusion

Establishing private storage for internal company documents on Azure is more than a technical exercise—it is a strategic investment in organizational security and resilience. By carefully configuring storage accounts, enforcing encryption, applying role-based access controls, and leveraging private endpoints, businesses can create a secure environment that protects sensitive information from unauthorized access. Beyond compliance, this approach fosters trust among employees and stakeholders, ensuring that critical data remains both accessible and safeguarded. As companies continue to embrace digital transformation, Azure’s private storage solutions provide a scalable and reliable foundation for managing internal documents with confidence and peace of mind.

Deploying Ubuntu CLI Instance on AWS EC2: A Step-by-Step Walkthrough

adegbola adeniyi — Thu, 26 Feb 2026 13:54:09 +0000

Introduction

Cloud computing has transformed from a luxury for tech giants into a fundamental playground for developers and enthusiasts alike. Whether you're looking to host a web application, run automated scripts, or simply tinker with a powerful Linux environment, Amazon Web Services (AWS) provides the industry-standard infrastructure to make it happen.

At the heart of this infrastructure is Amazon EC2 (Elastic Compute Cloud), a service that lets you launch virtual servers in minutes. When paired with Ubuntu, arguably the most popular and user-friendly Linux distribution for servers, you get a robust, secure, and highly flexible environment managed entirely through the Command Line Interface (CLI).

In this walkthrough, we’ll skip the fluff and dive straight into the technical process of:

Provisioning a fresh Ubuntu instance within the AWS Free Tier.
Connecting to your server from your local machine using SSH.

Step 1: Access the EC2 Dashboard

Log in to your AWS Management Console.In the top search bar, type "EC2" and select the EC2 service from the dropdown. Click on Dashboard under the top features to view your current resources.

Step 2: Navigate to Running Instances

On the EC2 Dashboard, locate the Resources section. Click on Instances (running) to view your active virtual servers.

Step 3: Initialize Instance Launch

In the Instances window, click the orange Launch instances button located in the top right corner.

Step 4: Configure Name and Tags

Under the Name and tags section, provide a name for your server. In the Value field, enter a name like "AWSVNEC2".
Ensure the Resource types include Instances to apply this tag correctly.

Step 5: Select the Ubuntu OS

In the Application and OS Images section, select Ubuntu from the Quick Start icons. From the dropdown menu, select Ubuntu Server 24.04 LTS (HVM). Look for the Free tier eligible label to ensure you aren't charged for the software image.

Step 6: Choose Instance Type

In the Instance type section, select t3.micro (or t2.micro). Verify it is marked as Free tier eligible.

Step 7: Create a Security Key Pair

Click Create new key pair to open the setup window. Key pair name: Enter a name like "awsvmec2key". Key pair type: Select RSA. Private key file format: Select .pem. Click Create key pair to download the file to your computer.

Step 8: Network and Storage Settings

Under Network settings, ensure Create security group is selected and Allow SSH traffic from Anywhere (0.0.0.0/0) is checked.
Under Configure storage, keep the default 8 GiB of gp3 root volume, which is well within the 30 GB free tier limit.

Step 9: Launch and Review

Review the Summary panel on the right. Click the orange Launch instance button. Once you see the green Success banner, click the Connect to instance button.

Step 10: Access the CLI

On the Connect to instance page, select the EC2 Instance Connect tab. Ensure the username is "ubuntu" and click Connect.
A new browser window will open, providing a direct terminal interface to your live Ubuntu server.

In conclusion, deploying an Ubuntu instance on AWS EC2 is a straightforward process that provides a powerful, scalable environment for your projects. By successfully navigating the AWS Console, configuring your machine specifications, and securing your access with a private key pair, you have laid the foundation for professional cloud computing.

With your instance now active and accessible via the CLI, you are ready to install software, host applications, and explore the full potential of the Linux ecosystem in the cloud.

A Step‑by‑Step Guide to Creating a Windows Server 2025 Virtual Machine in Azure

adegbola adeniyi — Sat, 21 Feb 2026 12:19:44 +0000

Introduction

If you’ve ever felt like the Azure Portal looks more like a cockpit than a website, you’re not alone. We’ve all been there—staring at a dozen menus and wondering which button actually does what. But here’s the good news: deploying your first Windows Server 2025 VM is much easier than it looks.

> "Windows Server 2025 isn't just an incremental update; it’s a bridge between traditional on-premises reliability and the hyper-scalability of the modern cloud".

Windows Server 2025 is the newest powerhouse in Microsoft's lineup, featuring faster storage, tighter security, and a much smoother hybrid-cloud experience. While it represents the "cutting edge," you don't need to be a veteran systems administrator to get it up and running.

I’ve put this guide together to be the resource I wish I had when I first started. We’re going to skip the jargon and focus on the "why" and "how." By the end of this article, you won't just have a VM running in the cloud—you'll actually understand the settings that got you there.

Let’s dive in and get your first cloud server live!

Step 1

Type virtual machine into the search bar. Select Virtual machines from the services list to head to the compute dashboard.

Step 2

Click the + Create button in the top-left corner. Choose Azure virtual machine from the dropdown menu. This opens the main configuration form.

Step 3

Resource Group: Click Create new and name it (e.g., VmResGp). Think of this as a folder for all your project's files. Virtual machine name: Give your server a unique name like MyAzureVM. Region: Select a location close to you (e.g., South Africa North) to reduce lag.

Step 4

Now we choose the "brain" and the "muscle" of the server. Image: Select Windows Server 2025 Datacenter: Azure Edition. Size: For a balance of performance and cost, a size like Standard_D2s_v3 or Standard_DS1_v2 is perfect for beginners.

Step 5
You wouldn't leave your front door unlocked; the same applies here.

Administrator account: Create a username (like AzureUser) and a strong password. Keep these safe! You'll need them to log in later.
Inbound port rules: To actually see your server's desktop, ensure RDP (3389) and HTTP (80) are selected. This allows you to connect remotely.

Step 6

Monitoring: Under the Monitoring tab, you can set Boot diagnostics to "Disable" for a simple lab setup to save on storage costs.

Step 7

Tags: Use the "Tags" tab to label your resources. For example, set a tag for Department: IT or Staff: [Your Name]. This is a lifesaver for tracking costs later.

Step 8
Almost there! Azure will now double-check your settings.

Click Review + create. Azure will run a "Validation" to make sure your settings are compatible. Once you see the green "Validation passed" checkmark, click the big blue Create button at the bottom.

Step 9
Once the deployment is complete, click Go to resource to open your VM’s overview page.

On the VM Overview page, you will see your Primary NIC public IP (e.g., 4.222.232.95).

Step 10

Click the Connect button at the top and select Connect.

Under the Native RDP section, click the Download RDP file button.

Locate the downloaded file in your browser and click Open.

Step 11

A Windows Security prompt will appear. Enter the password you created in Step 5 for the user AzureUser

If you see a certificate warning stating "The identity of the remote computer cannot be verified," simply click Yes to proceed.

Step 12

You are now logged into your Windows Server 2025 instance! You can verify the version by going to Settings > System > About, where you’ll see the Windows Server 2025 Datacenter Azure Edition branding and the version 24H2.

Congratulations! You’ve successfully navigated the Azure landscape to deploy, configure, and log into your very own Windows Server 2025 instance.
By following these steps, you’ve done more than just "click buttons"—you’ve provisioned enterprise-grade hardware in the cloud, managed secure networking, and explored the latest operating system Microsoft has to offer. Whether you’re using this VM as a sandbox for testing new features or as the first brick in a larger infrastructure project, you now have the foundational skills to scale up whenever you're ready.

Quick Cleanup Tip
Since this is a cloud environment, remember that costs are billed based on the time the VM is running. To keep your credits safe:

Stop the VM in the Azure Portal when you aren't using it.

Check that the status says "Deallocated" to ensure you aren't being charged for compute resources.

You’re now officially a cloud practitioner. Keep exploring, stay curious, and enjoy the power of Windows Server 2025!

Provide storage for the public website to Keep Our Worldwide Customers' Content Fast, Versioned, and Recoverable

adegbola adeniyi — Thu, 19 Feb 2026 22:52:09 +0000

Introduction

As our company website continues to grow rapidly, serving customers worldwide with essential product images, videos, marketing literature, and customer success stories, I knew we needed a reliable, high-performance storage solution. This content is truly mission-critical: it must load quickly with low latency no matter where users are, and we can't risk permanent data loss from accidental deletions or overwrites during frequent updates.
To address these needs head-on, I completed a hands-on skilling exercise in Azure to build a robust Blob Storage setup from scratch. Specifically, I:

Created a storage account configured for high availability
Enabled anonymous public access for seamless global delivery
Set up a dedicated blob container for all website documents
Activated soft delete to allow easy recovery of accidentally deleted files
Turned on blob versioning to automatically track and restore previous document versions

This configuration ensures fast, public access for our global audience, built-in protection against human error, and full history tracking for every asset—perfect for scaling without worry.
In the steps below, I'll walk you through exactly what I did in the Azure portal including the key choices I made and why they matter for a growing international website like ours.

Here's the step-by-step guide I followed with images:

1. Creating the high-availability storage account.

This storage requires high availability if there’s a regional outage. Additionally, i will enable read access to the secondary region.

In the portal, search for and select Storage accounts

Select + Create

For resource group select new. Give your resource group a name and select OK.
Set the Storage account name to 01pbcwebsite. Make sure the storage account name is unique by adding an identifier.
Take the defaults for other settings. Select Review and then Create. Wait for the storage account to deploy, and then select Go to resource.

2. Enabled anonymous public access for seamless global delivery.

Information on the public website should be accessible without requiring customers to login.

In the storage account, in the Data management section, select the Redundancy blade.

Ensure Read-access Geo-redundant storage is selected.

Review the primary and secondary location information.

In the storage account, in the Settings section, select the Configuration blade. Ensure the Allow blob anonymous access setting is Enabled. Be sure to Save your changes.

3. Set up a dedicated blob container for all website documents

Since the public website has various images and documents, we need to create a storage container for the contents. Also customers should be able to view the images without being authenticated. I will configure anonymous read access for the public container blobs. For testing, i will upload a file to the public container. The type of file doesn’t matter. A small image or text file is a good choice.

In your storage account, in the Data storage section, select the Containers blade. Select + Container. Ensure the Name of the container is public. Select Create.

Select your public container.

On the Overview blade, select Change access level.

Ensure the Public access level is Blob (anonymous read access for blobs only).

Select OK

Ensure you are viewing your container. Select Upload.

Select Browse to files and Browse to a file of your choice. Select Open

Select Upload.

Close the upload window, Refresh the page and ensure your file was uploaded.

Select your uploaded file. On the Overview tab, copy the URL.Paste the URL into a new browser tab.
If you have uploaded an image file it will display in the browser. Other file types should be downloaded.

4. Activated soft delete to allow easy recovery of accidentally deleted files

It’s important that the website documents can be restored if they’re deleted. during this project i Configured blob soft delete for 21 days. Also i did a test to confirm if the configurations work.

Go to the Overview blade of the storage account. On the Properties page, locate the Blob service section. Select the Blob soft delete setting.

Ensure the Enable soft delete for blobs is checked.
Change the Keep deleted blobs for (in days) setting to 21.
Notice you can also Enable soft delete for containers.
Don’t forget to Save your changes.

Navigate to your container where you uploaded a file. Select the file you uploaded and then select Delete.

Select Delete to confirm deleting the file.

On the container Overview page, toggle the slider Show deleted blobs. This toggle is to the right of the search box.

Select your deleted file, and use the ellipses on the far right, to Undelete the file.

Refresh the container and confirm the file has been restored.

5. Turned on blob versioning to automatically track and restore previous document versions.

It’s important to keep track of the different website product document versions.

Go to the Overview blade of the storage account. In the Properties section, locate the Blob service section. Select the Versioning setting.

Ensure the Enable versioning for blobs checkbox is checked.
Notice your options to keep all versions or delete versions after.
Don’t forget to Save your changes.

In conclusion, by completing this hands-on Azure skilling project, I successfully built a high-availability Blob Storage solution that perfectly supports our rapidly expanding global company website. With geo-redundant storage ensuring reliable uptime, anonymous public access enabling fast low-latency delivery of product images, videos, marketing literature, and customer success stories to users worldwide, a dedicated container for organized assets, soft delete for quick recovery from accidental deletions, and blob versioning to preserve full document history, we've created a resilient, scalable foundation that directly addresses our mission-critical content needs. This straightforward yet powerful setup in the Azure portal delivers both performance and peace of mind as demand continues to grow—proving that thoughtful configuration can protect against human error while powering seamless global access. If you're handling similar web assets, I strongly encourage trying these features yourself.
Thanks for following along—feel free to share your thoughts, questions, or your own Azure experiences below!

Sandbox Essentials: Designing Azure Storage for Hands-On Learning

adegbola adeniyi — Wed, 18 Feb 2026 18:04:56 +0000

Introduction

Before any cloud solution hits production, it needs a reliable staging ground where ideas can be stress-tested and skills can be sharpened. Deploying a dedicated storage account for testing and training isn't just a technical prerequisite; it’s a strategic move that allows you to experiment with data redundancy, lifecycle policies, and access tiers without risking live assets or blowing the budget. By establishing this foundational sandbox, you create a low-stakes environment where developers and students alike can master the nuances of Azure Storage, ensuring that by the time a system goes live, every edge case has been explored and every configuration is battle-hardened.

Below are the steps to create an Azure storage:

Step 1

In the Azure portal, search for and select Storage accounts.

Step 2

Select + Create.

Step 3

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. Select Review, and then Create.

Step 4

Select Create button.

Step 5

Wait for the storage account to deploy and then Go to resource.

Ultimately, a well-provisioned storage account serves as the heartbeat of any successful lab environment, transforming abstract cloud concepts into hands-on expertise. By isolating your testing and training data, you protect your production integrity while fostering a culture of fearless experimentation and continuous improvement. As your project evolves from a sandbox prototype to a full-scale deployment, the lessons learned within this controlled environment will serve as the blueprint for a more resilient, cost-effective, and secure cloud infrastructure.

How to Create a Resource Group on Azure Portal

adegbola adeniyi — Wed, 18 Feb 2026 07:13:12 +0000

Introduction

When working with Microsoft Azure, organizing your resources effectively is just as important as creating them. That’s where Resource Groups come in. A resource group acts as a logical container that holds related resources for an Azure solution, making it easier to manage, monitor, and control costs. Whether you’re deploying virtual machines, databases, or web apps, grouping them together ensures better governance and streamlined administration.

In this guide, we’ll walk through the step-by-step process of creating a resource group using the Azure Portal. By the end, you’ll not only understand how to set one up but also why resource groups are a foundational element in building scalable and well-structured cloud environments.

Step 1

In the Azure portal, search for and select Resource groups.

Step 2

Select + Create

Step 3

Give your resource group a name. For example, storageresgp. Select a region. Use this region throughout the project.

Step 4

Select Review and create to validate the resource group.

Step 5

Select Review, and then Create.

Step-6

Wait for the storage account to deploy and then Go to resource.

With this setup in place, you’re ready to deploy, manage, and grow your applications confidently—knowing that your resources are organized and easy to maintain.

Unlocking the Cloud: A Beginner's Guide to 7 Essential Cloud Computing Concepts

adegbola adeniyi — Sat, 07 Feb 2026 10:55:06 +0000

INTRODUCTION

Ever wonder how your favorite online services manage millions of users, stay reliably online, and roll out new features at lightning speed? The secret often lies in cloud computing—a powerful paradigm that’s reshaping the digital world. And understanding it isn’t just for IT professionals; it’s for anyone curious about the magic behind modern technology.

Let’s start with the basics.

Cloud computing is the delivery of computing services—such as servers, storage, databases, networking, software, analytics, and even artificial intelligence—over the internet (“the cloud”) rather than relying on local infrastructure. Think of it as renting IT resources on demand, with flexible, pay-as-you-go pricing.

Now, let’s break down these core ideas and explore how they power the digital experiences we rely on every day.

1. What is Virtualization?
Virtualization creates virtual versions of computing resources (like servers, storage, or networks) on top of physical hardware. It allows multiple virtual machines (VMs) to run on a single physical server, each with its own operating system and applications. A hypervisor (software layer) manages this separation.
This improves hardware utilization, enables easier management, and reduces costs.
There are two main types:

Type 1 (bare-metal, runs directly on hardware — more efficient).
Type 2 (hosted, runs on top of a host OS — easier for desktops).

2. Scalability
Scalability is the ability of a system to handle increased load by adding resources. There are two main approaches:

Vertical scaling (scaling up): Add more power (CPU, RAM) to an existing server.
Horizontal scaling (scaling out): Add more servers/instances and distribute the load.

NB
Horizontal scaling is preferred in cloud environments because it's more flexible and has fewer limits.

3. Agility
Agility refers to how quickly and easily a business or team can respond to changes, launch new features, or adapt to market needs. In cloud computing, agility comes from rapid provisioning of resources (minutes instead of weeks), self-service portals, automation, and DevOps practices.
It enables faster experimentation, shorter development cycles, and quicker time-to-market.

4. High Availability
High availability (HA) ensures a system remains operational and accessible with minimal downtime (often aiming for 99.9%+ uptime). It uses redundancy (e.g., multiple servers across availability zones), load balancers, and automatic failover to handle component failures without interrupting service.

5. Fault Tolerant
Fault tolerance goes beyond high availability — the system continues operating correctly even when one or more components fail completely, with no interruption and ideally zero data loss. It requires stronger redundancy (e.g., fully replicated systems with real-time synchronization) and is more expensive.
High availability often allows brief failover time, while fault tolerance aims for seamless continuation.

6. Global Reach
Global reach means deploying applications and services across multiple geographic regions and data centers worldwide. Cloud providers have regions and edge locations globally, allowing low-latency access, data residency compliance, disaster recovery, and serving users from the nearest location.

7. What is the difference between Elasticity and Scalability?

Scalability: Ability to increase capacity to handle growth (usually focused on scaling up/out for higher demand). It can be manual or planned.
Elasticity: Goes further — automatically and dynamically scales resources up and down in real-time based on actual demand. It matches resources precisely to workload (no over-provisioning waste), ideal for unpredictable traffic (e.g., auto-scaling groups).

Scalability is "grow when needed"; elasticity is "grow and shrink automatically and efficiently."

Bringing It All Together
These concepts are the building blocks of modern cloud infrastructure. They enable businesses of all sizes to innovate faster, serve customers globally, reduce operational costs, and build incredibly resilient and powerful applications that are always available, no matter what.

Understanding them is the first step to truly appreciating the power and potential of the cloud!