title	Quickstart: Create an Azure Virtual Network
description	Learn how to use the various deployment methods in Azure to create a virtual network.
author	asudbring
ms.author	allensu
ms.service	azure-virtual-network
ms.topic	quickstart
ms.date	07/10/2025

Quickstart: Create an Azure Virtual Network

Learn how to create an Azure Virtual Network using the Azure portal, Azure CLI, Azure PowerShell, Azure Resource Manager (ARM) template, Bicep template, and Terraform. Two virtual machines and an Azure Bastion host are deployed to test connectivity between the virtual machines in the same virtual network. The Azure Bastion host facilitates secure and seamless RDP and SSH connectivity to the virtual machines directly in the Azure portal over SSL.

:::image type="content" source="./media/quick-create-portal/virtual-network-qs-resources.png" alt-text="Diagram of resources created in the virtual network quickstart." lightbox="./media/quick-create-portal/virtual-network-qs-resources.png":::

A virtual network is the fundamental building block for private networks in Azure. Azure Virtual Network enables Azure resources such as virtual machines to securely communicate with each other and the internet.

[!VIDEO https://learn-video.azurefd.net/vod/player?id=6b5b138e-8406-406e-8b34-40bdadf9fc6d]

If you don't have an Azure account with an active subscription, create one for free.

Prerequisites

Portal

An Azure account with an active subscription. You can create an account for free.

PowerShell

An Azure account with an active subscription. You can create an account for free.
Azure Cloud Shell or Azure PowerShell.

The steps in this quickstart run the Azure PowerShell cmdlets interactively in Azure Cloud Shell. To run the commands in the Cloud Shell, select Open Cloud shell at the upper-right corner of a code block. Select Copy to copy the code, and then paste it into Cloud Shell to run it. You can also run Cloud Shell from within the Azure portal.

You can also install Azure PowerShell locally to run the cmdlets. The steps in this article require Azure PowerShell module version 5.4.1 or later. Run Get-Module -ListAvailable Az to find your installed version. If you need to upgrade, see Update the Azure PowerShell module.

If you run PowerShell locally, run Connect-AzAccount to connect to Azure.

CLI

[!INCLUDE quickstarts-free-trial-note]

[!INCLUDE azure-cli-prepare-your-environment-no-header.md]

This article requires version 2.0.28 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.

If you're running Azure CLI locally, use Azure CLI version 2.0.31 or later.

ARM template

An Azure account with an active subscription. You can create an account for free.

[!INCLUDE About Azure Resource Manager]

Bicep

An Azure account with an active subscription. You can create an account for free.
To deploy the Bicep files, either the Azure CLI or Azure PowerShell installed.

Terraform

An Azure account with an active subscription. You can create an account for free.
Installation and configuration of Terraform.

Resource values

Use the following values to replace the placeholders of resources in this article:

Setting	Placeholder	Value
Resource group	`<resource-group>`	test-rg
Region	`<region>`	East US 2
Virtual network	`<virtual-network>`	vnet-1
Subnet	`<subnet>`	subnet-1
Network security group	`<network-security-group>`	nsg-1
Bastion	`<bastion>`	bastion
Virtual machine 1	`<virtual-machine-1>`	vm-1
Virtual machine 2	`<virtual-machine-2>`	vm-2

ARM template

Review the template

The template that you use in this quickstart is from Azure Quickstart Templates.

:::code language="json" source="~/quickstart-templates/quickstarts/microsoft.network/vnet-two-subnets/azuredeploy.json" :::

The template defines the following Azure resources:

Microsoft.Network/virtualNetworks: Creates a virtual network.
Microsoft.Network/virtualNetworks/subnets: Creates a subnet.

Deploy the template

Deploy the Resource Manager template to Azure:

Select Deploy to Azure to sign in to Azure and open the template. The template creates a virtual network with two subnets.

:::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.network%2Fvnet-two-subnets%2Fazuredeploy.json":::
In the portal, on the Create a Virtual Network with two Subnets page, enter, or select the following values:
- Resource group: Select Create new, enter CreateVNetQS-rg for the resource group name, and then select OK.
- Virtual Network Name: Enter a name for the new virtual network.
Select Review + create, and then select Create.
When deployment finishes, select the Go to resource button to review the resources that you deployed.

Review deployed resources

Explore the resources that you created with the virtual network by browsing through the settings panes for VNet1:

The Overview tab shows the defined address space of 10.0.0.0/16.
The Subnets tab shows the deployed subnets of Subnet1 and Subnet2 with the appropriate values from the template.

To learn about the JSON syntax and properties for a virtual network in a template, see Microsoft.Network/virtualNetworks.

Bicep

Create the virtual network and virtual machines

This quickstart uses the Two VMs in virtual network Bicep template from Azure Resource Manager Quickstart Templates to create the virtual network, resource subnet, and virtual machines. The Bicep template defines the following Azure resources:

Microsoft.Network virtualNetworks: Creates an Azure virtual network.
Microsoft.Network virtualNetworks/subnets: Creates a subnet for the virtual machines.
Microsoft.Compute virtualMachines: Creates the virtual machines.
Microsoft.Compute availabilitySets: Creates an availability set.
Microsoft.Network networkInterfaces: Creates network interfaces.
Microsoft.Network loadBalancers: Creates an internal load balancer.
Microsoft.Storage storageAccounts: Creates a storage account.

Review the Bicep file:

:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.compute/2-vms-internal-load-balancer/main.bicep" :::

Deploy the Bicep template

Save the Bicep file to your local computer as main.bicep.

Deploy the Bicep file by using either the Azure CLI or Azure PowerShell:

CLI

az group create \
    --name TestRG \
    --location eastus

az deployment group create \
    --resource-group TestRG \
    --template-file main.bicep

PowerShell

 $rgParams = @{
     Name     = 'TestRG'
     Location = 'eastus'
 }
 New-AzResourceGroup @rgParams

 $deploymentParams = @{
     ResourceGroupName = 'TestRG'
     TemplateFile      = 'main.bicep'
 }
 New-AzResourceGroupDeployment @deploymentParams

When the deployment finishes, a message indicates the deployment succeeded.

Deploy Azure Bastion

Bastion uses your browser to connect to virtual machines in your virtual network over Secure Shell (SSH) or Remote Desktop Protocol (RDP) by using their private IP addresses. The virtual machines don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see What is Azure Bastion?

Note

[!INCLUDE Pricing]

Use the Azure Bastion as a Service Bicep template from Azure Resource Manager Quickstart Templates to deploy and configure Bastion in your virtual network. This Bicep template defines the following Azure resources:

Microsoft.Network virtualNetworks/subnets: Creates an AzureBastionSubnet subnet.
Microsoft.Network bastionHosts: Creates the Bastion host.
Microsoft.Network publicIPAddresses: Creates a public IP address for the Bastion host.
Microsoft.Network networkSecurityGroups: Controls the settings for network security groups.

Review the Bicep file:

:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.network/azure-bastion/main.bicep" :::

Deploy the Bicep template

Save the Bicep file to your local computer as bastion.bicep.

Use a text or code editor to make the following changes in the file:

Line 2: Change param vnetName string from 'vnet01' to 'VNet'.
Line 5: Change param vnetIpPrefix string from '10.1.0.0/16' to '10.0.0.0/16'.
Line 12: Change param vnetNewOrExisting string from 'new' to 'existing'.
Line 15: Change param bastionSubnetIpPrefix string from '10.1.1.0/26' to '10.0.1.0/26'.
Line 18: Change param bastionHostName string to param bastionHostName = 'VNet-bastion'.

The first 18 lines of your Bicep file should now look like this example:

@description('Name of new or existing vnet to which Azure Bastion should be deployed')
param vnetName string = 'VNet'

@description('IP prefix for available addresses in vnet address space')
param vnetIpPrefix string = '10.0.0.0/16'

@description('Specify whether to provision new vnet or deploy to existing vnet')
@allowed([
  'new'
  'existing'
])
param vnetNewOrExisting string = 'existing'

@description('Bastion subnet IP prefix MUST be within vnet IP prefix address space')
param bastionSubnetIpPrefix string = '10.0.1.0/26'

@description('Name of Azure Bastion resource')
param bastionHostName = 'VNet-bastion'

Save the bastion.bicep file.

Deploy the Bicep file by using either the Azure CLI or Azure PowerShell:

CLI

az deployment group create \
     --resource-group TestRG \
     --template-file bastion.bicep

PowerShell

$deploymentParams = @{
    ResourceGroupName = 'TestRG'
    TemplateFile      = 'bastion.bicep'
}
New-AzResourceGroupDeployment @deploymentParams

When the deployment finishes, a message indicates the deployment succeeded.

Note

Virtual machines in a virtual network with a Bastion host don't need public IP addresses. Bastion provides the public IP, and the virtual machines use private IPs to communicate within the network. You can remove the public IPs from any virtual machines in Bastion-hosted virtual networks. For more information, see Dissociate a public IP address from an Azure VM.

Review deployed resources

Use the Azure CLI, Azure PowerShell, or the Azure portal to review the deployed resources:

CLI

az resource list --resource-group TestRG

PowerShell

Get-AzResource -ResourceGroupName TestRG

Portal

In the Azure portal, search for and select resource groups. On the Resource groups page, select TestRG from the list of resource groups.
On the Overview page for TestRG, review all the resources that you created, including the virtual network, the two virtual machines, and the Bastion host.
Select the VNet virtual network. On the Overview page for VNet, note the defined address space of 10.0.0.0/16.
On the left menu, select Subnets. On the Subnets page, note the deployed subnets of backendSubnet and AzureBastionSubnet with the assigned values from the Bicep files.

Terraform

The script uses the Azure Resource Manager (azurerm) provider to interact with Azure resources. It uses the Random (random) provider to generate random pet names for the resources.

The script creates the following resources:

A resource group: A container that holds related resources for an Azure solution.
A virtual network: A fundamental building block for your private network in Azure.
Two subnets: Segments of a virtual network's IP address range where you can place groups of isolated resources.

[!INCLUDE About Terraform]

Implement the Terraform code

Note

The sample code for this article is in the Azure Terraform GitHub repo. You can view the log file that contains the test results from current and previous versions of Terraform.

For more articles and sample code that show how to use Terraform to manage Azure resources, see the documentation page for Terraform on Azure.

Create a directory in which to test and run the sample Terraform code, and make it the current directory.
Create a file named main.tf and insert the following code:

:::code language="Terraform" source="~/terraform_samples/quickstart/101-virtual-network-create-two-subnets/main.tf":::
Create a file named outputs.tf and insert the following code:

:::code language="Terraform" source="~/terraform_samples/quickstart/101-virtual-network-create-two-subnets/outputs.tf":::
Create a file named providers.tf and insert the following code:

:::code language="Terraform" source="~/terraform_samples/quickstart/101-virtual-network-create-two-subnets/providers.tf":::
Create a file named variables.tf and insert the following code:

:::code language="Terraform" source="~/terraform_samples/quickstart/101-virtual-network-create-two-subnets/variables.tf":::

Initialize Terraform

[!INCLUDE terraform-init.md]

Create a Terraform execution plan

[!INCLUDE terraform-plan.md]

Apply a Terraform execution plan

[!INCLUDE terraform-apply-plan.md]

Verify the results

Get the Azure resource group name:

resource_group_name=$(terraform output -raw resource_group_name)

Get the virtual network name:

virtual_network_name=$(terraform output -raw virtual_network_name)

Use az network vnet show to show the details of your newly created virtual network:

az network vnet show \
    --resource-group $resource_group_name \
    --name $virtual_network_name

Troubleshoot Terraform on Azure

For information about troubleshooting Terraform, see Troubleshoot common problems when using Terraform on Azure.

Connect to a virtual machine

In the search box at the top of the portal, enter Virtual machine. Select Virtual machines in the search results.
In Virtual machines, select vm-1.
Select Connect then Connect via Bastion in the Overview section.
In the Bastion connection page, enter or select the following information:

Setting Value

Authentication Type Select SSH Private Key from Local File.

Username Enter azureuser.

Local File Select the private key file you downloaded or created.
Select Connect.

Setting	Value
Authentication Type	Select SSH Private Key from Local File.
Username	Enter azureuser.
Local File	Select the private key file you downloaded or created.

Start communication between virtual machines

At the bash prompt for vm-1, enter ping -c 4 vm-2.

You get a reply similar to the following message:

azureuser@vm-1:~$ ping -c 4 vm-2
PING vm-2.3bnkevn3313ujpr5l1kqop4n4d.cx.internal.cloudapp.net (10.0.0.5) 56(84) bytes of data.
64 bytes from vm-2.internal.cloudapp.net (10.0.0.5): icmp_seq=1 ttl=64 time=1.83 ms
64 bytes from vm-2.internal.cloudapp.net (10.0.0.5): icmp_seq=2 ttl=64 time=0.987 ms
64 bytes from vm-2.internal.cloudapp.net (10.0.0.5): icmp_seq=3 ttl=64 time=0.864 ms
64 bytes from vm-2.internal.cloudapp.net (10.0.0.5): icmp_seq=4 ttl=64 time=0.890 ms

Close the Bastion session.
In the search box at the top of the portal, enter Virtual machine. Select Virtual machines in the search results.
In Virtual machines, select vm-2.
Select Connect then Connect via Bastion in the Overview section.
In the Bastion connection page, enter or select the following information:

Setting Value

Authentication Type Select SSH Private Key from Local File.

Username Enter azureuser.

Local File Select the private key file you downloaded or created.
Select Connect.

Setting	Value
Authentication Type	Select SSH Private Key from Local File.
Username	Enter azureuser.
Local File	Select the private key file you downloaded or created.

At the bash prompt for vm-2, enter ping -c 4 vm-1.

You get a reply similar to the following message:

azureuser@vm-2:~$ ping -c 4 vm-1
PING vm-1.3bnkevn3313ujpr5l1kqop4n4d.cx.internal.cloudapp.net (10.0.0.4) 56(84) bytes of data.
64 bytes from vm-1.internal.cloudapp.net (10.0.0.4): icmp_seq=1 ttl=64 time=0.695 ms
64 bytes from vm-1.internal.cloudapp.net (10.0.0.4): icmp_seq=2 ttl=64 time=0.896 ms
64 bytes from vm-1.internal.cloudapp.net (10.0.0.4): icmp_seq=3 ttl=64 time=3.43 ms
64 bytes from vm-1.internal.cloudapp.net (10.0.0.4): icmp_seq=4 ttl=64 time=0.780 ms

Close the Bastion session.

Remove-AzResourceGroup -Name <your resource group name>

Bicep

In the Azure portal, on the Resource groups page, select the TestRG resource group.
At the top of the TestRG page, select Delete resource group.
On the Delete a resource group page, under Enter resource group name to confirm deletion, enter TestRG, and then select Delete.
Select Delete again.

Terraform

[!INCLUDE terraform-plan-destroy.md]

FilesExpand file tree

quickstart-create-virtual-network.md

Latest commit

History

quickstart-create-virtual-network.md

File metadata and controls

Quickstart: Create an Azure Virtual Network

Prerequisites

Resource values

Review the template

Deploy the template

Review deployed resources

Create the virtual network and virtual machines

Deploy the Bicep template

CLI

PowerShell

Deploy Azure Bastion

Deploy the Bicep template

CLI

PowerShell

Review deployed resources

CLI

PowerShell

Portal

Implement the Terraform code

Initialize Terraform

Create a Terraform execution plan

Apply a Terraform execution plan

Verify the results

Troubleshoot Terraform on Azure

Connect to a virtual machine

Start communication between virtual machines

Clean up resources

Related content