Reconfiguring Azure Virtual Networks

#cloudcomputing #azure #cloudskills #devops

Microsoft Azure is a cloud platform where you can run virtual computers, store data, build apps, and use AI—without needing physical servers. It's like renting powerful tech tools online to get things done faster and smarter.

What is Virtual Network (VNet)?
An Azure Virtual Network is your private space in the cloud. It lets your resources securely talk to each other and to external systems. You can define subnets, IP ranges, route traffic, and even connect to your on-prem network via VPNs.

Steps by steps in Reconfiguring Azure Virtual Network;

Step 1: Create a new subnet on an existing virtual network (vNet)

Login to Microsoft Azure at https://portal.azure.com
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.
From the guided-project-vnet blade, under settings, select Subnets.
To add a subnet, select + Subnet
For Subnet purpose leave it as Default.
For Name enter: ftpSubnet.
Leave the rest of the settings alone and select Add.
Select Home to return to the Azure portal home page.

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

Step 3: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.
Select Home to return to the Azure portal home page.

Congratulations – you’ve created a new Network security group and configured rules to allow inbound FTP traffic. Now, you’ll need to associate the new network security group with the ftpSubnet.

Step 4: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.

It prepare the network for shifting the current Linux VM to a new subnet that’s designed to handle incoming FTP traffic.

Conclusion
Reconfiguring Azure Virtual Networks is a critical step in architecting secure and scalable cloud solutions. Through the systematic creation of subnets, deployment of network security groups, configuration of access rules, and association of resources, we have demonstrated how to enhance network segmentation and control within the Azure ecosystem.

This configuration not only prepares the infrastructure for specialized workloads such as FTP access, but also reflects best practices in cloud security and operational efficiency. By leveraging Azure’s integrated tools and services, developers and IT professionals can design environments that are robust, adaptable, and aligned with enterprise requirements.

Continued refinement of your Azure network setup ensures optimal performance and security as your cloud projects evolve.