Merge pull request #42184 from iainfoulds/patch-4

[VMSS] Fixes MicrosoftDocs/azure-docs#8330

Author: PRMerger10

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-networking.md

@@ -210,7 +210,10 @@ Example output:
 Every NIC attached to a VM in a scale set can have one or more IP configurations associated with it. Each configuration is assigned one private IP address. Each configuration may also have one public IP address resource associated with it. To understand how many IP addresses can be assigned to a NIC, and how many public IP addresses you can use in an Azure subscription, refer to [Azure limits](../azure-subscription-service-limits.md?toc=%2fazure%2fvirtual-network%2ftoc.json#azure-resource-manager-virtual-networking-limits).
 
 ## Multiple NICs per virtual machine
-You can have up to 8 NICs per virtual machine, depending on machine size. The maximum number of NICs per machine is available in the [VM size article](../virtual-machines/windows/sizes.md). The following example is a scale set network profile showing multiple NIC entries, and multiple public IPs per virtual machine:
+You can have up to 8 NICs per virtual machine, depending on machine size. The maximum number of NICs per machine is available in the [VM size article](../virtual-machines/windows/sizes.md). All NICs connected to a VM instance must connect to the same virtual network. The NICs can connect to different subnets, but all subnets must be part of the same virtual network.
+
+The following example is a scale set network profile showing multiple NIC entries, and multiple public IPs per virtual machine:
+
 ```json
 "networkProfile": {
     "networkInterfaceConfigurations": [