freshness

Author: halkazwini

articles/virtual-network/ip-services/virtual-network-multiple-ip-addresses-powershell.md

@@ -1,14 +1,15 @@
 ---
-title: Multiple IP addresses for Azure virtual machines - Azure PowerShell
+title: Assign multiple IP addresses to VMs - Azure PowerShell
 titleSuffix: Azure Virtual Network
 description: Learn how to create a virtual machine with multiple IP addresses with Azure PowerShell.
 services: virtual-network
 author: asudbring
 ms.service: virtual-network
 ms.subservice: ip-services
 ms.topic: how-to
-ms.date: 09/09/2022
+ms.date: 12/12/2022
 ms.author: allensu
+ms.custom: template-how-to, engagement-fy23
 ---
 
 # Assign multiple IP addresses to virtual machines using Azure PowerShell
@@ -23,14 +24,14 @@ Assigning multiple IP addresses to a VM enables the following capabilities:
 
 * The ability to add any of the private IP addresses for any of the NICs to an Azure Load Balancer back-end pool. In the past, only the primary IP address for the primary NIC could be added to a back-end pool. For more information about load balancing multiple IP configurations, see [Load balancing multiple IP configurations](../../load-balancer/load-balancer-multiple-ip.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
 
-Every NIC attached to a VM has one or more IP configurations associated to it. Each configuration is assigned one static or dynamic private IP address. Each configuration may also have one public IP address resource associated to it. To learn more about IP addresses in Azure, read the [IP addresses in Azure](../../virtual-network/ip-services/public-ip-addresses.md) article.
+Every NIC attached to a VM has one or more IP configurations associated to it. Each configuration is assigned one static or dynamic private IP address. Each configuration may also have one public IP address resource associated to it. To learn more about IP addresses in Azure, see [IP addresses in Azure](../../virtual-network/ip-services/public-ip-addresses.md).
 
 > [!NOTE]
-> All IP configurations on a single NIC must be associated to the same subnet.  If multiple IPs on different subnets are desired, multiple NICs on a VM can be used.  To learn more about multiple NICs on a VM in Azure, read the [Create VM with Multiple NICs](../../virtual-machines/windows/multiple-nics.md) article.
+> All IP configurations on a single NIC must be associated to the same subnet.  If multiple IPs on different subnets are desired, multiple NICs on a VM can be used.  To learn more about multiple NICs on a VM in Azure, see [Create VM with Multiple NICs](../../virtual-machines/windows/multiple-nics.md).
 
 There's a limit to how many private IP addresses can be assigned to a NIC. There's also a limit to how many public IP addresses that can be used in an Azure subscription. See the [Azure limits](../../azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#azure-resource-manager-virtual-networking-limits) article for details.
 
-This article explains how to add multiple IP addresses to a virtual machine using the Azure portal. 
+This article explains how to add multiple IP addresses to a virtual machine using PowerShell. 
 
 ## Prerequisites
 
@@ -43,14 +44,14 @@ This article explains how to add multiple IP addresses to a virtual machine usin
 - Ensure your Az. Network module is 4.3.0 or later. To verify the installed module, use the command Get-InstalledModule -Name "Az.Network". If the module requires an update, use the command Update-Module 
 -Name "Az. Network" if necessary.
 
-If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 5.4.1 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-Az-ps). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
+If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 5.4.1 or later. Run `Get-InstalledModule -Name Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-Az-ps). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
 > [!NOTE]
 > Though the steps in this article assigns all IP configurations to a single NIC, you can also assign multiple IP configurations to any NIC in a multi-NIC VM. To learn how to create a VM with multiple NICs, see [Create a VM with multiple NICs](../../virtual-machines/windows/multiple-nics.md).
 
   :::image type="content" source="./media/virtual-network-multiple-ip-addresses-portal/multiple-ipconfigs.png" alt-text="Diagram of network configuration resources created in How-to article.":::
 
-  *Figure: Diagram of network configuration resources created in How-to article.*
+  *Figure: Diagram of network configuration resources created in this How-to article.*
 
 ## Create a resource group
 
@@ -70,7 +71,7 @@ New-AzResourceGroup @rg
 
 In this section, you'll create a virtual network for the virtual machine.
 
-Use [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork) and [New-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/new-azvirtualnetworksubnetconfig) to create a virtual network.
+Use [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork) and [New-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/new-azvirtualnetworksubnetconfig) to create a virtual network with one subnet.
 
 ```azurepowershell-interactive
 ## Create backend subnet config ##
@@ -81,18 +82,18 @@ $subnet = @{
 $subnetConfig = New-AzVirtualNetworkSubnetConfig @subnet 
 
 ## Create the virtual network ##
-$net = @{
+$vnet = @{
     Name = 'myVNet'
     ResourceGroupName = 'myResourceGroup'
     Location = 'eastus2'
     AddressPrefix = '10.1.0.0/16'
     Subnet = $subnetConfig
 }
-New-AzVirtualNetwork @net
+New-AzVirtualNetwork @vnet
 
 ```
 
-## Create primary public IP address
+## Create a primary public IP address
 
 Use [New-AzPublicIpAddress](/powershell/module/az.network/new-azpublicipaddress) to create a primary public IP address.
 
@@ -141,9 +142,9 @@ $nsg = @{
 New-AzNetworkSecurityGroup @nsg
 ```
 
-### Create network interface
+## Create a network interface
 
-You'll use [New-AzNetworkInterface](/powershell/module/az.network/new-aznetworkinterface) and [New-AzNetworkInterfaceIpConfig](/powershell/module/az.network/new-aznetworkinterfaceipconfig) to create the network interface for the virtual machine. The public IP addresses and the NSG created previously are associated with the NIC. The network interface is attached to the virtual network you created previously.
+Use [New-AzNetworkInterface](/powershell/module/az.network/new-aznetworkinterface) and [New-AzNetworkInterfaceIpConfig](/powershell/module/az.network/new-aznetworkinterfaceipconfig) to create a network interface (NIC) for the virtual machine. The public IP address and network security group created previously are associated with the network interface. The network interface is attached to the virtual network you created previously.
 
 ```azurepowershell-interactive
 ## Place the virtual network into a variable. ##
@@ -167,7 +168,7 @@ $pub1 = @{
 }
 $pubIP1 = Get-AzPublicIPAddress @pub1
 
-## Create primary configuration for NIC. ##
+## Create a primary IP configuration for the network interface. ##
 $IP1 = @{
     Name = 'ipconfig1'
     Subnet = $vnet.Subnets[0]
@@ -176,7 +177,7 @@ $IP1 = @{
 }
 $IP1Config = New-AzNetworkInterfaceIpConfig @IP1 -Primary
 
-## Create tertiary configuration for NIC. ##
+## Create a secondary IP configuration for the network interface. ##
 $IP3 = @{
     Name = 'ipconfig3'
     Subnet = $vnet.Subnets[0]
@@ -185,7 +186,7 @@ $IP3 = @{
 }
 $IP3Config = New-AzNetworkInterfaceIpConfig @IP3
 
-## Command to create network interface for VM ##
+## Command to create a network interface. ##
 $nic = @{
     Name = 'myNIC1'
     ResourceGroupName = 'myResourceGroup'
@@ -199,7 +200,7 @@ New-AzNetworkInterface @nic
 > [!NOTE]
 > When adding a static IP address, you must specify an unused, valid address on the subnet the NIC is connected to.
 
-### Create virtual machine
+## Create a virtual machine
 
 Use the following commands to create the virtual machine:
 
@@ -301,7 +302,7 @@ $net = @{
 }
 $nic = Get-AzNetworkInterface @net
 
-## Create secondary configuration for NIC. ##
+## Create a secondary IP configuration for the network interface. ##
 $IPc2 = @{
     Name = 'ipconfig2'
     Subnet = $vnet.Subnets[0]
@@ -319,3 +320,9 @@ $nic | Set-AzNetworkInterface
 ```
 
 [!INCLUDE [virtual-network-multiple-ip-addresses-os-config.md](../../../includes/virtual-network-multiple-ip-addresses-os-config.md)]
+
+## Next steps
+
+- Learn more about [public IP addresses](public-ip-addresses.md) in Azure.
+- Learn more about [private IP addresses](private-ip-addresses.md) in Azure.
+- Learn how to [Configure IP addresses for an Azure network interface](virtual-network-network-interface-addresses.md?tabs=nic-address-powershell).