In this lab, I demonstrate how to deploy and configure a Virtual Machine (VM) using the Microsoft Azure portal. I walk through the full setup process—from creating the VM to configuring availability zones, security settings, and network components.
I also attach and configure additional disks, manage inbound and outbound network access, and ensure that associated resources like public IPs and network interfaces (NICs) are properly cleaned up when the VM is deleted. This lab showcases my ability to manage Azure compute resources with precision and best practices.
-
I explored the importance of deploying virtual machines in Microsoft Azure to support scalable and secure cloud infrastructure.
-
I learned how to create a VM using the Azure portal, configuring key settings such as availability zones, operating system, and authentication methods.
-
I gained hands-on experience attaching and configuring additional disks to enhance storage performance and flexibility.
-
I managed network access by configuring inbound and outbound rules, ensuring secure connectivity to and from the VM.
-
I verified that associated resources—such as public IP addresses and network interfaces (NICs)are properly removed when the VM is deleted, maintaining clean resource hygiene.
Selected “Create a resource” from the Azure portal homepage to begin provisioning a new cloud service or infrastructure component.
Selected the “Windows Server 2019 Datacenter” image from the Azure Marketplace to begin provisioning a new virtual machine.
Selected the resource group dropdown to choose or create a logical container for the new virtual machine.
Clicked into the “Virtual machine name” field to define a unique identifier for the new VM being provisioned.
Entered SRV01 as the virtual machine name to uniquely identify the new deployment within the selected resource group.
Selected the availability configuration to define redundancy and uptime settings for the SRV01 virtual machine.
Selected “Availability Zone” from the redundancy options to enhance fault tolerance and ensure high availability for virtual machine SRV01.
Selected a specific Availability Zone to deploy SRV01 into a physically isolated datacenter within East US, enhancing resilience and uptime.
Selected zone “1” from the Availability Zone list to physically isolate SRV01 within East US for enhanced fault tolerance and service continuity.
Selected the security type for SRV01 to define baseline protections and compatibility with trusted launch or standard deployment options. This step helps shape the VM’s security posture — a key decision for compliance and workload integrity
Opted for “Standard” security to apply baseline protections for virtual machine SRV01, ensuring compatibility across trusted hardware and common workloads. This step balances security and flexibility — perfect for general-purpose deployments.
Opened the VM size selector to choose the appropriate CPU and memory configuration for SRV01, balancing performance needs with cost efficiency. This step locks in the compute profile for your deployment — a key decision for lab performance and budget control
Chosen the Standard_D4s_v3 VM size to allocate 4 vCPUs and 16 GiB of memory to SRV01, balancing performance requirements with budget considerations. This step locks in a solid compute profile — ideal for heavier workloads or multi-role lab setups.
Clicked into the “Username” field to begin setting up the administrator account for managing virtual machine SRV01. This step initiates secure access setup — a key move for remote management and control.
Entered vmadmin as the administrator username for virtual machine SRV01, establishing secure access credentials for remote management. This step sets the foundation for authenticated control — a key part of your VM deployment flow.
Opened the inbound ports dropdown during VM creation to configure public access rules such as RDP (port 3389) or HTTP (port 80). This step is key for enabling secure remote access or web traffic — perfect for setting up connectivity during deployment.
Opened the inbound ports dropdown during VM creation and selected RDP (3389) to enable secure Remote Desktop access to the Windows virtual machine. This step is essential for remote administration — perfect for labs, testing, or production environments.
%20%20VM%20Deployment.png)
Advanced to the Disks configuration tab during VM creation to define OS disk type, attach data disks, and set encryption options before deployment. This step transitions you into storage setup — perfect for customizing performance, redundancy, or backup strategy.
Selected the OS disk size dropdown during VM creation to choose between image default 127GiB balancing performance, cost, and redundancy. This step is key for tailoring disk performance to your workload — whether you're optimizing for speed or budget
Selected the default OS disk size of 127 GiB during VM creation, which matches the base image size (Windows Server 2019 Datacenter). This disk accommodates the OS, system updates, and essential runtime dependencies. For workloads requiring additional storage, data disks can be attached separately.
Selected the OS disk type dropdown during VM creation to choose between storage tiers like Premium SSD, Standard SSD, Standard HDD, or Ultra Disk — balancing performance, durability, and cost for the operating system volume.
Chosen “Standard HDD” as the OS disk type during VM creation to minimize cost. This tier offers reliable, low-cost storage ideal for light workloads, testing environments, or non-critical applications.
Selected the option to create and attach a new data disk during VM setup to expand storage capacity for application files, logs, or persistent datasets beyond the OS volume.
Entered “DatBo1” as the disk name during creation to label and organize the new resource within the selected resource group. Naming conventions help ensure clarity across deployments and backups.
Opened the disk size selector during new disk creation to adjust capacity based on workload needs. Selected 32 GiB for Premium SSD — suitable for fast boot volumes, app binaries, or small databases.
Opened the storage type selector to compare disk tiers like Premium SSD, Standard SSD, and Ultra Disk. Each tier offers different IOPS, throughput, and burst capabilities tailored to workload performance needs.
Selected “Standard HDD” from the storage type dropdown during disk creation to prioritize cost-efficiency. This tier offers reliable, low-throughput storage ideal for infrequent access workloads like backups, logs, or archival data.
Selected the P4 disk tier with 32 GiB capacity under Premium SSD (LRS). This option provides balanced performance with 120 IOPS and 25 MBps throughput — suitable for lightweight workloads or boot volumes.
Checked the “Delete disk with VM” box to ensure the disk named Data01 is automatically removed when the virtual machine is deleted. This helps prevent orphaned resources and unnecessary storage costs.
Confirmed the creation of a new 32 GiB Premium SSD disk named Data01 by clicking the OK button. This action finalizes disk settings including encryption, resource group, and source type, preparing it for attachment to a VM.
Advanced to the Networking tab in the VM creation wizard to configure virtual network, subnet, public IP, and network security group settings. This step transitions from basic VM setup to defining connectivity and access controls.
Advanced to the Monitoring tab in the VM creation wizard after configuring management options like boot diagnostics, identity, Defender for Cloud, and backup. The next blade focuses on telemetry, metrics, and logging setup for operational visibility.
Proceeded to the Advanced tab in the VM creation wizard after configuring monitoring options like boot diagnostics and guest-level telemetry. The next blade allows fine-tuning of extensions, custom scripts, and host-level settings.
Advanced to the Tags tab in the VM creation wizard after configuring advanced options like host group, capacity reservation, and proximity placement. The next blade enables metadata tagging for resource organization, cost tracking, and automation.
Advanced to the Review + create tab in the VM creation wizard after assigning tags for resource organization. This final blade summarizes all configuration choices before deployment — including image, size, networking, disks, and estimated cost.
Scrolled down the VM creation blade to access additional configuration options such as disks, networking, management, and monitoring. This ensures all setup parameters are reviewed before deployment.
Selected the Create button to deploy the virtual machine with validated configuration. This action provisions the VM using the selected image, size, network, and management settings — initiating resource allocation and startup.
Selected the “Go to resource” button after the successful deployment of WindowsServer-201-2409172304371. This marks the end of a long, deliberate journey — from subnetting and tagging to disk provisioning and diagnostics — each step taken with clarity, patience, and purpose.
By clicking this, I now enter the VM’s overview blade — the control center where I’ll monitor performance, configure networking, and begin real workload setup.
This isn’t just a resource. It’s the reflection of every deliberate choice, every quiet breakthrough, and every moment I refused to rush what mattered.
Thank you for walking this path with me. The lab is complete — but the learning continues. Onward.
For hours, I wrestled with Git misfires, remote mismatches, authentication loops, and nested repo confusion—all while navigating the delicate structure of my Azure VM lab folder. Each error felt like a wall, but I treated every one as a lesson. I reconfigured remotes, corrected branch paths, and retraced my steps until the push finally landed. What began as a technical task became a test of patience and persistence. Now, my project lives on GitHub—not just as code, but as proof that I don’t quit when things get hard. I troubleshoot, I learn, and I finish strong.