DEV Community: Oladimeji Zainab

Azure Resource Cleanup: A Hands-On Guide to Managing and Deleting Resources Efficiently

Oladimeji Zainab — Fri, 03 Jul 2026 13:11:37 +0000

Introduction.

Cleaning up Azure resources is a critical part of responsible cloud administration. While creating and configuring infrastructure often receives the most attention, properly removing resources helps maintain a secure environment, prevents unnecessary costs, and ensures that cloud subscriptions remain organized.

In this guide, I walk through the process of removing resource locks and deleting Azure resources after completing a hands-on lab. The walkthrough covers verifying and removing delete locks from a virtual machine, deleting the associated resource group, and cleaning up additional resources such as the Network Watcher resource group. These are essential operational tasks that support effective Azure governance and cost management in both learning and production environments.

Remove delete locks.

From the Azure portal home page, in the search box, enter virtual machines.

Select the guided-project-vm virtual machine.

If necessary, expand the Settings submenu.

Select Locks.

Select Delete on the line for the VM-delete-lock.

The virtual doesnt conatain a lock so we can go ahead to delete our resources

Delete the project resource group

From the Azure portal home page, in the search box, enter Resource groups.

Select the guided-project-rg resource group.

Select Delete resource group.

Replicate same process to delete the Networkwatcher.

Conclusion

Resource cleanup is an often-overlooked but essential aspect of Azure administration. By verifying resource locks before deletion and removing resource groups that are no longer needed, administrators can avoid unnecessary cloud costs while maintaining a well-managed Azure environment.

Following a structured cleanup process not only improves operational efficiency but also reinforces good cloud governance practices. Whether you're completing a lab, testing a proof of concept, or decommissioning production resources, making cleanup a standard part of your workflow helps ensure that your Azure subscription remains secure, organized, and cost-effective.

I hope this walkthrough provides a practical reference for safely decommissioning Azure resources. If you have additional recommendations or preferred strategies for Azure resource lifecycle management, feel free to share them in the discussion.

Mastering Azure Storage Security: A Hands-On Guide to Controlling Storage Access

Oladimeji Zainab — Fri, 03 Jul 2026 12:37:35 +0000

Introduction.

Effective Azure Virtual Machine administration extends beyond deployment. As workloads evolve, administrators must be able to manage VM security, optimize resource utilization, maintain storage, and implement operational controls that improve both performance and cost efficiency.

In this guide, I demonstrate several essential Azure VM management tasks using the Azure portal. The walkthrough covers moving a virtual machine to a different subnet, vertically scaling the VM to accommodate changing compute requirements, attaching a managed data disk to expand storage capacity, and configuring automatic shutdown to minimize unnecessary Azure costs. These are practical operations that reflect common administrative responsibilities in enterprise Azure environments and are valuable skills for both cloud practitioners and Azure certification candidates.

Create a storage container.

From the Azure portal home page, in the search box, enter storage accounts.

Select the storage account you created in the Previous exercise. The storage account name is the hyperlink to the storage account. (Note: it should be associated with the resource group guided-project-rg.)

On the storage account blade, under the Data storage submenu, select Containers.

Select + Add container.

In the Name field, enter storage-container.

Select Create.

Upload a file to the storage container

Select the storage container you just created.

Select Upload and upload the file you prepared.

Once the file is ready for upload, select Upload.

Change the access tier

Select the file you just uploaded (the file name is a hyperlink).

Select Change tier.

Select Cold.

Select Save.

Create a file share

From the Azure portal home page, in the search box, enter storage accounts.

Select the storage account you created in the Prepare exercise. The storage account name is the hyperlink to the storage account. (Note: it should be associated with the resource group guided-project-rg.)

On the storage account blade, under the Data storage submenu, select File shares.

Select + File share.

On the Basics tab, in the name field enter file-share

On the Backup tab, uncheck Enable backup.

Select Review + create.

Select Create.

Once the file share is created, select Upload.

Upload the same file you uploaded to the blob storage or a different file, it’s up to you.

Create a shared access signature token

From the Azure portal home page, in the search box, enter storage accounts.

Select the storage account you created in the Prepare exercise.

On the storage account blade, select Storage browser.

Expand Blob containers.

Select the storage container you created earlier, storage-container.

Select the ellipses (three dots) on the end of the line for the image you uploaded.

Select Generate SAS

Set Signing method to Account key.

Set Signing key to Key 1.

Set Stored access policy to None.

Set Permissions to Read.

Enter a custom start and expiry time or leave the defaults.

Set Allowed protocols to HTTPS only.

Select Generate SAS token and URI.

Copy the Blob SAS URL and paste it in another window or tab of your browser. It should display the image you uploaded. Keep this tab or window open.

Rotate access keys

From the Azure portal home page, in the search box, enter storage accounts.

Select the storage account you created in the Prepare exercise.

Expand the Security + networking submenu and Select Access keys.

For Key 1, select Rotate key.

Read and then acknowledge the warning about regenerating the access key by selecting Yes.

Once you see the success message for rotating the access key, go back to the window or tab you used to check the SAS token and refresh the page. You should receive an authentication failed error.

Conclusion.

Managing Azure Virtual Machines effectively requires a balance between performance, scalability, and operational efficiency. By completing the tasks in this guide, we've explored how to reconfigure a VM's network placement, increase its compute capacity through vertical scaling, extend its storage with managed disks, and automate shutdown schedules to optimize cloud spending.

These capabilities form part of the day-to-day responsibilities of Azure administrators and cloud engineers, making them fundamental skills for maintaining reliable and cost-effective cloud infrastructure. As you continue working with Azure, incorporating these management practices into your workflow will help you build more resilient, scalable, and efficient environments.

Thank you for taking the time to read this walkthrough. If you've implemented similar VM management strategies or have additional recommendations for optimizing Azure workloads, I'd be glad to hear your thoughts in the discussion below.

Managing Azure Virtual Machines: A Hands-On Guide to Networking, Scaling, Storage, and Auto-Shutdown

Oladimeji Zainab — Fri, 03 Jul 2026 12:15:15 +0000

Introduction.

Managing virtual machines efficiently is an essential skill for anyone working with Microsoft Azure. Beyond simply creating a VM, administrators often need to modify its network configuration, scale its compute resources to meet changing workloads, expand storage capacity, and implement cost-saving measures such as automatic shutdown.

In this hands-on guide, I'll walk through the practical steps I performed to manage an Azure Virtual Machine using the Azure portal. Specifically, you'll learn how to move a VM to a different subnet, vertically scale the VM to a larger size, attach a new data disk for additional storage, and configure automatic shutdown to help reduce unnecessary Azure costs. Whether you're preparing for the AZ-104 certification or building your Azure administration skills, these tasks represent common real-world VM management operations you'll encounter in cloud environments.

Move the virtual machine network to the new subnet

From the Azure portal home page, in the search box, enter virtual machines and Select virtual machines under services.

Select the guided-project-vm virtual machine.

If the virtual machine is running, select Stop.

Wait for the Status field to update and show Stopped (deallocated).

Within the Networking subsection of the menu, select Network settings.

Select the Network interface / IP configuration hyperlink for the VM.

On the IP Configurations page, update the Subnet to ftpSubnet.

Select Apply.

Select Home to return to the Azure portal home page.

Vertically scale the virtual machine.

From the Azure portal home page, in the search box, enter virtual machines.

Select the guided-project-vm virtual machine.

Locate the Availability + scale submenu and select Size.

Select a new VM size D2s_v3 for example. (Note: If you don’t see the same size as shown in this exercise, select something similar.)

Select Resize

Attach data disks to a virtual machine

From the Azure portal home page, in the search box, enter virtual machines.

Select the guided-project-vm virtual machine.

Locate the settings submenu and select Disks.

Select Create and attach a new disk.

Leave LUN as default.

Enter ftp-data-disk for the Disk name.

Leave the Storage type as default.

Enter 20 for the Size

Select Apply to create the new storage disk and attach the disk to the machine.

Configure automatic shutdown on a virtual machine.

From the Azure portal home page, in the search box, enter virtual machines.

Select the guided-project-vm virtual machine.

Under the Operations submenu, select Auto-shutdown.

In order to let late uploads finish, set the Scheduled shutdown to 7:15:00 PM.

![format(https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/iv6apbtk2ah284fntbvt.png)

Select Save.

Conclusion.

Successfully managing Azure Virtual Machines goes far beyond deployment—it involves continuously optimizing networking, performance, storage, and operational costs. In this walkthrough, we covered how to migrate a VM to a new subnet, resize it to accommodate increased workloads, attach additional storage using a managed data disk, and configure automatic shutdown to avoid unnecessary compute charges.

These are fundamental Azure administration tasks that every cloud engineer should be comfortable performing. Mastering them not only improves your understanding of Azure infrastructure but also prepares you for real-world production environments where virtual machines must be maintained efficiently and cost-effectively.

I hope this guide helps you follow along with your own Azure lab or learning journey. If you found it useful, feel free to leave a comment, share your experience, or connect with me here on Dev.to. Happy learning and happy building!

Azure Networking Fundamentals: How to Create and Secure Subnets with Network Security Groups

Oladimeji Zainab — Thu, 18 Jun 2026 06:05:17 +0000

Introduction

Network segmentation and access control are critical components of a secure cloud environment. In Microsoft Azure, subnets help organize resources within a virtual network, while Network Security Groups (NSGs) provide granular control over inbound and outbound traffic.

In this guide, I will walk through the process of creating a dedicated subnet, configuring a Network Security Group, defining an inbound security rule, and associating the NSG with the subnet. These steps demonstrate how to strengthen network security and establish controlled access to resources within an Azure Virtual Network.

From the Azure portal home page, in the search box, enter virtual networks.

Select the guided-project-vnet virtual network.

From the guided-project-vnet blade, under settings, select Subnets.

For Subnet purpose leave it as Default.
For Name enter: ftpSubnet

Leave the rest of the settings alone and select Add.

Create a network security group

From the Azure portal home page, in the search box, enter virtual networks.

Select virtual networks under services

Select Network security groups.

Select + Create.

Verify the subscription is correct.

Select the guided-project-rg resource group.

Enter ftpNSG for the network security group name.

Select Review + create.

Once the validation is complete, select Create.

Wait for the screen to refresh and display Your deployment is complete.

Select Go to resource.

Create an inbound security rule

Under settings, select Inbound security rules.

Select + Add.

Change the Destination port ranges from 8080 to 22.

Select TCP for the protocol.

Set the name to ftpInbound.

Select Add.

Associate a network security group to a subnet

From the Azure portal home page, in the search box, enter virtual networks.

Select virtual networks under services.

Select the guided-project-vnet virtual network.

Under settings, select Subnets.

Select the ftpSubnet you created.

On the Edit subnet page, under the Security section heading, update the Network security group field to ftpNSG.

Select Save.

Conclusion

By completing these configurations, you have successfully created a dedicated subnet, deployed a Network Security Group, configured an inbound security rule, and associated the NSG with the subnet. This setup enhances the security posture of your Azure environment by allowing only authorized traffic to reach resources within the network.

Understanding and implementing network segmentation and security controls are essential cloud administration skills. As you continue your Azure journey, these foundational concepts will help you design more secure, scalable, and resilient cloud infrastructures.

Azure Infrastructure Setup Guide: Creating Resource Groups, Virtual Networks, Virtual Machines, and Storage Accounts

Oladimeji Zainab — Thu, 18 Jun 2026 01:32:00 +0000

Introduction

In this guide, we will walk through the process of setting up essential Azure resources required for a cloud infrastructure environment. The setup includes creating a Resource Group, Virtual Network, Virtual Machine, and Storage Account using the Microsoft Azure Portal.

These foundational resources are critical building blocks for deploying, managing, and scaling cloud workloads effectively. By following the step-by-step instructions outlined in this guide, you will gain hands-on experience with Azure resource provisioning and develop a solid understanding of core cloud infrastructure components.

Create a resource group

Select Create.

Enter guided-project-rg in the Resource group name field.

The Region field will automatically populate. Leave the default value.

Select Review + create.

Select Create.

Return to the home page of the Azure portal by selecting Home.

Create a virtual network with one subnet

From the Azure portal home page, in the search box, enter virtual networks.

Select Create

Scroll down to the Instance details section and enter guided-project-vnet for the Virtual network name.

Select Review + create.

Select Create.

Wait for the screen to refresh and show Your deployment is complete.

Create a virtual machine

From the Azure portal home page, in the search box, enter virtual machines.

Select Create and then select Virtual machine

Select guided-project-rg for the Resource group.

Enter guided-project-vm for the Virtual machine name.

For the Image, select one of the Ubuntu Server options. (For example, Ubuntu Server 24.04 LTS - x64 Gen2)

Continue further on the Basics page to the Administrator account section and Select Password for authentication type.

Enter guided-project-admin for the admin Username.

Enter a password for the admin account.

Confirm the password for the admin account.

Leave the rest of the settings as default settings. You can review the settings if you like, but shouldn’t change any.

Select Review + create

Select Create to confirm the resource cost and create the virtual machine.

Create a Storage account

From the Azure portal home page, in the search box, enter storage accounts.

Select Create

Scroll down to the Instance details section and enter a name for the storage account. Storage accounts must be globally unique, so you may have to try a few different times to get a storage account name.

Select Review + create.

Select Create.

Wait for the screen to refresh and show Your deployment is complete.

Conclusion

Congratulations on successfully completing the setup process. In this exercise, you provisioned key Azure resources, including a Resource Group, Virtual Network, Virtual Machine, and Storage Account. These services form the foundation of many cloud-based solutions and are essential for deploying, managing, and securing applications in Microsoft Azure.

Through this practical implementation, you have gained valuable experience navigating the Azure Portal and creating core infrastructure components. This knowledge serves as a strong foundation for more advanced cloud engineering, DevOps, and infrastructure management tasks as you continue your Azure learning journey.

Provision of Storage for a new Company App

Oladimeji Zainab — Mon, 25 May 2026 09:40:23 +0000

Introduction

In today’s cloud-driven environments, securing data at rest and ensuring controlled access are critical components of any robust architecture. Microsoft Azure provides a comprehensive set of tools that enable organizations to build secure, scalable, and compliant storage solutions.

In this guide, we walk through the end-to-end process of provisioning a storage account and enhancing its security using managed identities, role-based access control (RBAC), and customer-managed encryption keys. Beyond basic configuration, this setup demonstrates how to enforce least-privilege access, integrate secure key management with Azure Key Vault, and apply advanced data protection features such as immutable storage and encryption scopes.

By the end of this walkthrough, you will have a secure and production-ready storage configuration that aligns with modern cloud security best practices.

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 is unique and meets the naming requirements.

Move to the Encryption tab.

Check the box for Enable infrastructure encryption.

Notice the warning, This option cannot be changed after this storage account is created.

Select Review + Create

Wait for the resource to deploy.

Provide a managed identity for the web app to use.

Search for and select Managed identities.

Select Create

Select your resource group.

Give your managed identity a name.

Select Review and create, and then Create.

Assign the correct permissions to the managed identity. The identity only needs to read and list containers and blobs.

Search for and select your storage account.

Select the Access Control (IAM) blade.

Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Storage Blob Data Reader role.

On the Members page, select Managed identity.

Select Select members, in the Managed identity drop-down select User-assigned managed identity.

Select the managed identity you created in the previous step.

Click Select and then Review + assign the role.

Select Review + assign a second time to add the role assignment.

Your storage account can now be accessed by a managed identity with the Storage Data Blob Reader permissions.

Secure access to the storage account with a key vault and key

In the portal, search for and select Resource groups.

Select your resource group, and then the Access Control (IAM) blade.

Select your resource group, and then the Access Control (IAM) blade.

Select Add role assignment (center of the page).

On the Job functions roles page, search for and select the Key Vault Administrator role.

On the Members page, select User, group, or service principal.

Select Select members.

Search for and select your user account. Your user account is shown in the top right of the portal.

Click Select and then Review + assign.

Select Review + assign a second time to add the role assignment.

You are now ready to continue with the lab.

Create a key vault to store the access keys.

In the portal, search for and select Key vaults.

Select Create.

Select your resource group.

Provide the name for the key vault. The name must be unique.

Ensure on the Access configuration tab that Azure role-based access control (recommended) is selected.

Select Review + create.

Wait for the validation checks to complete and then select Create.

After the deployment, select Go to resource.

On the Overview blade ensure both Soft-delete and Purge protection are enabled.

Create a customer-managed key in the key vault.

In your key vault, in the Objects section, select the Keys blade.

Select Generate/Import and Name the key.

Take the defaults for the rest of the parameters, and Create the key.

Configure the storage account to use the customer managed key in the key vault.

In the portal, search for and select Resource groups.

Select your resource group, and then the Access Control (IAM) blade.

Select Add role assignment (center of the page)

On the Job functions roles page, search for and select the Key Vault Crypto Service Encryption User role.

On the Members page, select Managed identity.

Select Select members, in the Managed identity drop-down select User-assigned managed identity.

Select your managed identity.

Click Select and then Review + assign.

Select Review + assign a second time to add the role assignment.

Configure the storage account to use the customer managed key in your key vault.

Return to your the storage account.

In the Security + networking section, select the Encryption blade.

Select Customer-managed keys.

Select a key vault and key. Select your key vault and key.

Select to confirm your choices.

Ensure the Identity type is User-assigned.

Select an identity.

Select your managed identity then select Add.

Save your changes.

If you receive an error that your identity does not have the correct permissions, wait a minute and try again.

Configure an time-based retention policy and an encryption scope.

Navigate to your storage account.

In the Data storage section, select the Containers blade.

Create a container called hold. Take the defaults. Be sure to Create the container.

Upload a file to the container.

In the Settings section, select the Access policy blade.

In the Immutable blob storage section, select + Add policy.

For the Policy type, select time-based retention.

Set the Retention period to 5 days.

Be sure to Save your changes.

Try to delete the file in the container and Verify you are notified failed to delete blobs due to policy.

The developers require an encryption scope that enables infrastructure encryption.

Navigate back to your storage account.

In the Security + networking blade, select Encryption.

In the Encryption scopes tab, select Add.

Give your encryption scope a name.

The Encryption type is Microsoft-managed key.

Set Infrastructure encryption to Enable.

Create the encryption scope.

Return to your storage account and create a new container and in the advanced section select the Encryption scope you created and apply it to all blobs in the container.

Conclusion

This implementation goes beyond simply creating a storage account—it establishes a strong security foundation for managing sensitive data in the cloud. By leveraging managed identities, assigning precise RBAC roles like Storage Blob Data Reader, and integrating with Azure Key Vault for customer-managed keys, you ensure that access to your storage resources is both controlled and auditable.

Additionally, the use of infrastructure encryption, immutable blob storage policies, and encryption scopes demonstrates how to meet higher compliance and data protection requirements. These practices are essential for organizations operating in regulated environments or handling critical business data.

Adopting these configurations not only improves security posture but also aligns your architecture with industry standards for cloud governance, making your solutions more resilient, scalable, and enterprise-ready.

Provision of shared file storage for the company offices

Oladimeji Zainab — Fri, 22 May 2026 05:43:28 +0000

Introduction

In today’s data-driven enterprise environment, the need for secure, scalable, and highly available file storage solutions is critical to supporting business operations across distributed teams. Microsoft Azure provides a robust platform for building such solutions through its managed storage services.

This guide walks through the end-to-end process of provisioning a premium file storage solution using Azure Storage Accounts, configuring file shares for organizational use, and implementing data protection through snapshots. It also demonstrates how to enhance security by restricting access to selected virtual networks, ensuring that corporate data remains protected while still being accessible to authorized resources.

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(It must be globally unique).

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.

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.

Select your file share and select + Add directory.

Name the new directory finance.

Select Browse and then select the finance directory.

Notice you can Add directory to further organize your file share.

Upload a file of your choosing.

Similar to blob storage, you need to protect against accidental deletion of files. You decide to use snapshots.

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.

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, and 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.

Conclusion

By completing this deployment, a secure and enterprise-grade file storage infrastructure has been successfully established using Azure’s native capabilities. The implementation not only enables centralized file sharing for departments such as finance but also incorporates critical safeguards including snapshot-based recovery and network-level access controls.

This approach reflects best practices in cloud storage architecture—balancing performance, resilience, and security. As organizations continue to scale in the cloud, leveraging these capabilities within Azure ensures operational efficiency, data integrity, and controlled access across business units.

Creating A virtual Machine using Linux Operating System

Oladimeji Zainab — Tue, 19 May 2026 01:48:48 +0000

Introduction

Deploying a virtual machine in Microsoft Azure provides a flexible and scalable way to run applications, host services, and simulate real-world infrastructure without the need for physical hardware. This guide walks through the end-to-end process of provisioning a Linux-based virtual machine using the Azure portal from creating a resource group and selecting an operating system, to configuring access and connecting via SSH. By following these steps, you will gain hands-on experience in setting up a secure and functional cloud environment, as well as performing basic system administration tasks such as updating packages and installing a web server.

on the azure portal search and select virtual machine

select + create

Create a new resource group and assign it an appropriate name. For the purpose of this project, the resource group is named fragnantplantrg.

Specify a name for the virtual machine.

Select a region

Select an image (operating system) for the virtual machine. In this case, Ubuntu is chosen as the preferred Linux distribution for deployment.

For the authentication method, select Password as the administrative credential type.

Enter user name and password for the virtual machine

Select the inbound port for the virtual machine

Navigate to the Monitoring tab and disable boot diagnotics

Click on Review and create

Once the deployment is complete, navigate to the resource.

Select the IP address and configure the idle timeout setting to 30 minutes.

Click on apply

Navigate back to your Virtual machine and click on the connect button

Click on check access

Copy and paste the SSH command into a terminal in the windows power shell

After entering the SSH Command, Type yes to continue on the windows power shell

Enter password. Please note that linux doesnt show password, so you need to be sure of what you are typing.

Virtual machine is now live

To run the Virtual Machine as an administrator(root user), use the Sudo SU command

Try updating the virtual machine to the latest version "apt Update" please note that "apt" is the package manager for linux

Try and install nginx using the command "apt install nginx"

Conclusion

By successfully completing this deployment, I have established a fully functional Linux virtual machine within Azure and connected to it securely using SSH. Beyond provisioning, I also performed essential post-deployment configurations, including updating the system and installing Nginx, demonstrating how cloud resources can be immediately utilized for real-world applications. This process not only reinforces core cloud computing concepts but also builds a solid foundation for more advanced tasks such as automation, scaling, and hosting production-grade applications in Azure.

End-to-End Deployment of Virtual Machine Infrastructure in Microsoft Azure

Oladimeji Zainab — Mon, 18 May 2026 02:17:26 +0000

Introduction

In today’s cloud-driven environment, the ability to efficiently provision and manage infrastructure is a critical skill for IT professionals and cloud engineers. Platforms like Microsoft Azure provide a robust and scalable ecosystem for deploying resources with speed, flexibility, and cost control.

This project demonstrates a practical, end-to-end approach to deploying a virtual machine within Azure, starting from the creation of a resource group to configuring connectivity and access via Remote Desktop Protocol (RDP). Beyond the technical setup, it also highlights key considerations around cost optimization, including the use of spot pricing and resource management strategies to prevent unnecessary charges.

The objective is to provide a clear, structured guide that not only walks through the deployment process but also reinforces best practices for managing cloud resources effectively in a real-world scenario.

Go to azure portal, search and select resource group
Select + create

Provide a name for the resource group; for this project, the resource group is named fragnantplant.

Select a region

Select review + create

Go to azure portal, search and select virtual machine

click + create

On the Basics tab, select the previously created resource group (fragnantplant).

Navigate to the Instance details and give the Virtual machine a name

select an availability options, kindly note for this project no infrastructure redundancy required because the azure account is currently on free trial

On the image tab select a compactible operating system, in this project windows 10 will be used as the azure account is currently on free trial

The Spot discount option represents a key cost optimization strategy. For interruptible workloads, such as batch processing tasks, leveraging Spot pricing can significantly reduce monthly costs, as illustrated by the noticeable difference in pricing compared to standard deployment options.

input user name and password

In order to enable connection and networking select the a compatible inbound port

Click on the licensing box

For best practice navigate to the monitoring tab and disable boot diagnostics

select review and create

Go to resource

click on the IP Address and set the idle time to 30 minutes

_ click on apply

For cost optimization purposes, it is important to note that stopping a virtual machine does not automatically halt all associated charges. To fully eliminate costs for unused resources, the public IP address must be disassociated from the virtual machine. This step is demonstrated for instructional purposes; however, in this project, the IP address was not disassociated.
To do this, on your azure portal search for and select IP

Select the virtual machine IP

Then you click on disassociate

Back to the scope of this project

Navigate back to your virtual machine and click on connect

click on check access

Download Remote Desktop Protocol(RDP)

Click on Connect

Insert Password

The virtual machine has been successfully deployed and is now operational.

Conclusion

The successful deployment of a virtual machine in Microsoft Azure goes beyond simply creating resources—it requires a thoughtful approach to configuration, accessibility, and cost management. This project illustrates how foundational components such as resource groups, virtual machines, networking, and monitoring settings come together to form a functional and efficient cloud environment.

Equally important is the emphasis on financial accountability in the cloud. Understanding how billing works—particularly around compute resources and public IP addresses—enables better decision-making and prevents avoidable costs. Simple actions, such as deallocating resources or disassociating IP addresses when not in use, can have a significant impact on overall expenditure.

As organizations continue to adopt cloud technologies, mastering these deployment and optimization techniques becomes essential. This hands-on implementation serves as a solid foundation for building more advanced, scalable, and cost-efficient cloud solutions in Azure.

Provision of private storage for internal company documents

Oladimeji Zainab — Thu, 14 May 2026 07:05:14 +0000

Introduction

In today’s digital landscape, securing sensitive corporate data is a critical responsibility for every organization. Businesses require storage solutions that not only protect confidential documents from unauthorized access but also ensure high availability and disaster recovery in the event of regional outages. Microsoft provides powerful cloud storage capabilities through Azure Storage Account, enabling organizations to build scalable, secure, and resilient storage infrastructures.

In this guide, I will walk through the step-by-step process of provisioning private storage for internal company documents using Azure Storage Accounts. The tutorial covers configuring geo-redundant storage (GRS) for high availability, creating secure private containers, generating Shared Access Signatures (SAS) for controlled external collaboration, implementing lifecycle management policies to optimize storage costs, and configuring object replication for backup and business continuity. By the end of this project, you will have a secure and enterprise-ready storage solution tailored for corporate document management.

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 privatestrg001. 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.

Be sure to save and click refresh to ensure that it is saved

Review the primary and secondary location information.

Create a storage container, upload a file, and restrict access to the file.

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

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.

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.

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.

Navigate to your fragnantstrg 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

Provisioning secure and highly available storage is an essential part of modern cloud infrastructure management. In this project, we successfully configured a private Azure Storage Account with geo-redundant storage to ensure resilience during regional outages, secured sensitive corporate files through private container access, and implemented Shared Access Signatures (SAS) to enable temporary and controlled external collaboration.

Additionally, we optimized long-term storage costs by configuring lifecycle management policies to automatically transition blobs from the hot tier to the cool tier after 30 days. Finally, we enhanced data protection and business continuity by setting up object replication between storage accounts for automated backup of public website content.

This hands-on implementation demonstrates how Microsoft cloud storage solutions can help organizations maintain security, scalability, availability, and operational efficiency while managing critical internal documents in the cloud.

Provision of storage for the public website.

Oladimeji Zainab — Wed, 13 May 2026 21:36:46 +0000

Introduction

In today’s cloud-driven environment, organizations require storage solutions that are secure, scalable, and highly available to ensure uninterrupted access to business-critical data. Public websites, in particular, rely heavily on reliable storage infrastructure for hosting images, documents, and other digital assets that must remain accessible even during regional outages.

In this project, I provisioned and configured an Azure Storage Account designed to support a public website with high availability and disaster recovery capabilities. The implementation included configuring Read-access Geo-redundant Storage (RA-GRS), enabling anonymous blob access, creating public blob containers, configuring blob soft delete for data recovery, and enabling blob versioning for document tracking and restoration.

This hands-on exercise demonstrates practical experience with Microsoft Azure Storage services, cloud infrastructure configuration, data protection strategies, and business continuity best practices.

Create a storage account to support the public website.

In the portal, search for and select

Select + Create.

For resource group select new. Give your resource group a name and select OK.

Set the Storage account name to plantstrg. 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.

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

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

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

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.

Create a blob storage container with anonymous read access

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.

Customers should be able to view the images without being authenticated. Configure anonymous read access for the public container blobs.

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.

Practice uploading files and testing access.

Ensure you are viewing your container.

Select Upload.

Browse to files and select a file. Browse to a file of your choice

Select Upload.

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

Determine the URL for your uploaded file. Open a browser and test the URL.

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.

It’s important that the website documents can be restored if they’re deleted. Configure blob soft delete for 21 days.

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.

If something gets deleted, you need to practice using soft delete to restore the files

Navigate to your container where you uploaded a file.

Select the file you uploaded and then select Delete.

Select OK 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.

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.

Conclusion

This project demonstrates how Azure Storage Accounts can be configured to provide a resilient, scalable, and secure storage solution for public-facing web applications. By implementing high availability through RA-GRS redundancy, enabling controlled public access to blobs, configuring soft delete for recovery, and activating blob versioning, I established a storage environment capable of supporting reliable website operations while minimizing the risk of data loss.

Beyond simply provisioning storage resources, this exercise highlights the importance of designing cloud infrastructure with availability, recovery, and long-term maintainability in mind. These are critical considerations for modern organizations seeking to build dependable cloud-native solutions using Microsoft Azure.

Provision of storage for IT department testing and training

Oladimeji Zainab — Tue, 12 May 2026 13:26:59 +0000

Introduction

In modern IT environments, the ability to efficiently manage, test, and secure data infrastructure is essential for supporting innovation, technical training, and operational excellence. Cloud storage solutions have become a critical component in enabling organizations to build flexible and scalable environments for development, testing, and learning activities without impacting production systems.

This project focuses on the provision and configuration of a secure and cost-effective storage solution using Microsoft Azure. The implementation process involves creating a dedicated resource group and deploying a storage account tailored to support IT department testing and training requirements. In addition to deployment, the project emphasizes essential configuration practices such as redundancy management, secure transfer enforcement, TLS 1.2 compliance, network accessibility, and access control optimization.

By following these step-by-step procedures, organizations can establish a reliable cloud storage environment that balances performance, security, accessibility, and cost efficiency while providing a practical foundation for hands-on IT training and system testing activities.

Create and deploy a resource group to hold all your project resources.

In the Azure portal, search for and select

Select + Create.

Give your resource group a name. In this case the resource group is named Fragnantplant

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

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.

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.

Conclusion

The successful deployment and configuration of a storage account for IT department testing and training demonstrates the importance of combining scalability, security, and cost optimization in cloud infrastructure management. Through the creation of a resource group and the implementation of key storage configurations, this project establishes a secure and efficient environment suitable for development, experimentation, and technical learning.

By configuring features such as Locally Redundant Storage (LRS), secure transfer requirements, TLS version 1.2, controlled access settings, and public networking permissions, the project highlights best practices in Azure storage administration while maintaining operational simplicity and affordability.

Overall, this implementation provides a strong foundation for supporting IT training and testing activities in a controlled cloud environment. It also reinforces the value of cloud technologies in enhancing organizational readiness, improving technical skills, and enabling modern infrastructure management practices in today’s digital landscape.