Can you deploy a gateway with only one NIC on azure with full functionality?

Question

Options

• AYes, you can deploy with 1 NIC but only for Auto scaling use cases
• BYes, this deployment scenario is fully supported
• CNo, you must deploy a gateway with NIC on every internal subnet
• DNo, a gateway on Azure have to be deployed with at least 2 NIC's

• A
  2% (1)
• B
  89% (39)
• C
  7% (3)
• D
  2% (1)

Explanation

Deploying a gateway with a single NIC on Azure is fully supported and provides complete functionality (B). Azure's software-defined networking (SDN) model handles traffic routing through User Defined Routes (UDRs) and Network Security Groups at the platform level, so a gateway doesn't need multiple physical NICs to inspect or route traffic across segments the way an on-premises appliance would.

Why the distractors are wrong:

• A is wrong because single-NIC support is not restricted to autoscaling scenarios - it's a general deployment option across use cases.
• C is wrong because Azure's SDN removes the need to place a NIC on every internal subnet; route tables steer traffic to the gateway without it needing a direct interface on each subnet.
• D is wrong because the multi-NIC requirement is a legacy on-premises concept; Azure's virtual networking abstracts that constraint away.

Memory tip: Think "cloud = software-defined." In Azure, routing logic lives in the platform (UDRs, NSGs), not in hardware NICs - so one NIC is enough for a gateway to see and control all the traffic you direct its way.

No community discussion yet for this question.