Configure private IP addresses for a virtual machine (Classic) using the Azure portal
Your IaaS virtual machines (VMs) and PaaS role instances in a virtual network automatically receive a private IP address from a range that you specify, based on the subnet they are connected to. That address is retained by the VMs and role instances, until they are decommissioned. You decommission a VM or role instance by stopping it from PowerShell, the Azure CLI, or the Azure portal. In those cases, once the VM or role instance starts again, it will receive an available IP address from the Azure infrastructure, which might not be the same it previously had. If you shut down the VM or role instance from the guest operating system, it retains the IP address it had.
In certain cases, you want a VM or role instance to have a static IP address, for example, if your VM is going to run DNS or will be a domain controller. You can do so by setting a static private IP address.
Before you work with Azure resources, it's important to understand that Azure currently has two deployment models: Azure Resource Manager and classic. Make sure you understand deployment models and tools before you work with any Azure resource. You can view the documentation for different tools by clicking the tabs at the top of this article.
This article covers the classic deployment model. You can also manage a static private IP address in the Resource Manager deployment model.
To better illustrate how to configure a static IP address for a VM, this document will use the scenario below.
In this scenario you will create a VM named DNS01 in the FrontEnd subnet, and set it to use a static IP address of 192.168.1.101.
The sample steps that follow expect a simple environment already created. If you want to run the steps as they are displayed in this document, first build the test environment described in create a vnet.
How to specify a static private IP address when creating a VM
To create a VM named DNS01 in the FrontEnd subnet of a VNet named TestVNet with a static private IP of 192.168.1.101, complete the following steps:
- From a browser, navigate to https://portal.azure.com and, if necessary, sign in with your Azure account.
Select NEW > Compute > Windows Server 2012 R2 Datacenter, notice that the Select a deployment model list already shows Classic, and then select Create.
Under Create VM, enter the name of the VM to be created (DNS01 in the scenario), the local administrator account, and password.
Select Optional Configuration > Network > Virtual Network, and then select TestVNet. If TestVNet is not available, make sure you are using the Central US location and have created the test environment described at the beginning of this article.
Under Network, make sure the subnet currently selected is FrontEnd, then select IP addresses, under IP address assignment select Static, and then enter 192.168.1.101 for IP Address as seen below.
- Select OK under IP addresses, select OK under Network, and then select OK under Optional config.
Under Create VM, select Create. Notice the tile below displayed in your dashboard:
How to retrieve static private IP address information for a VM
To view the static private IP address information for the VM created with the steps above, execute the steps below.
From the Azure portal, select BROWSE ALL > Virtual machines (classic) > DNS01 > All settings > IP addresses and notice the IP address assignment and IP address as seen below.
How to remove a static private IP address from a VM
Under IP addresses, select Dynamic to the right of IP address assignment, select Save, and then select Yes, as shown in the following picture:
![Create VM in Azure portal](./media/virtual-networks-static-ip-classic-pportal/figure07.png)
How to add a static private IP address to an existing VM
- Under IP addresses, shown previously, select Static to the right of IP address assignment.
- Type 192.168.1.101 for IP address, select Save, and then select Yes.
Set IP addresses within the operating system
It’s recommended that you do not statically assign the private IP assigned to the Azure virtual machine within the operating system of a VM, unless necessary. If you do manually set the private IP address within the operating system, ensure that it is the same address as the private IP address assigned to the Azure VM, or you can lose connectivity to the virtual machine. You should never manually assign the public IP address assigned to an Azure virtual machine within the virtual machine's operating system.