NIC

In the Ultra Transcenders books

AZ-305AZ-104AZ-7002V0-17.25AZ-900SC-900AZ-802MD-102ALZ

Each book explains NIC in context, with comparison tables and the common traps.

Related terms

• Add-AzNetworkInterfaceIpConfig

  Cmdlet in Az.Network for adding another IP configuration to a NIC that already exists. Passing -PrivateIpAddressVersion IPv6 lets a VM gain IPv6 without needing a second NIC.

• AzureFirewallManagementSubnet

  Subnet (minimum /26) set aside for the management NIC of Azure Firewall; that NIC must have a public IP address of its own and a default route to the internet.

• Backend pool

  Targets of a load balancer, identified by IP address or NIC IP configuration. A pool can't span VNets, and a Standard load balancer won't accept a VM that has a Basic public IP.

• Custom DNS server

  DNS server addresses configured on a VNet, or overridden on a NIC, in place of Azure-provided DNS, such as AD DS domain controllers; VMs need to be able to reach that private IP.

• DFW

  Distributed firewall. Stateful rules from NSX (vDefend) are enforced right at each virtual NIC inside the hypervisor, giving micro-segmentation between workloads. Gateway firewalls on Tier-0/1 are a separate thing.

• DHCP

  Azure delivers each NIC's private IP to the guest operating system using this protocol, so keep the OS set to obtain addresses automatically and configure any static IP on the Azure NIC.

• Effective security rules

  Network Watcher feature showing the merged subnet and NIC NSG rules that apply to a network interface; it does not test any traffic.

• Forced tunnelling

  Routing Azure's internet-bound traffic through an on-premises device or NVA rather than letting it break out directly. ExpressRoute achieves this when 0.0.0.0/0 is advertised over BGP, and site-to-site VPN uses BGP or a default site; Azure Firewall needs a management NIC (AzureFirewallManagementSubnet and a management public IP) for it.