Skip to content

Commit 0cb77ba

Browse files
committed
highlighted note
1 parent 07e3a23 commit 0cb77ba

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

includes/virtual-network-multiple-ip-addresses-intro.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ An Azure Virtual Machine (VM) has one or more network interfaces (NIC) attached
2525

2626
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. A public IP address resource has either a dynamic or static public IP address assigned to it. To learn more about IP addresses in Azure, read the [IP addresses in Azure](../articles/virtual-network/ip-services/public-ip-addresses.md) article.
2727

28-
Also note that 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](../articles/virtual-machines/windows/multiple-nics.md) article.
28+
> [!NOTE]
29+
> 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](../articles/virtual-machines/windows/multiple-nics.md) article.
2930
3031
There is a limit to how many private IP addresses can be assigned to a NIC. There is also a limit to how many public IP addresses that can be used in an Azure subscription. See the [Azure limits](../articles/azure-resource-manager/management/azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#azure-resource-manager-virtual-networking-limits) article for details.

0 commit comments

Comments
 (0)