Azure DDoS Protection now
covers the public IPs behind Azure NAT Gateway StandardV2, in public preview.
You can protect the IPv4 and IPv6 addresses that carry your outbound internet
traffic from network-layer DDoS attacks, using the same DDoS Network Protection
or IP Protection you already have. There’s no new API, feature registration or
appliance to manage, and no unsolicited inbound connections are opened to your
gateway.
Why it matters:
NAT Gateway doesn’t accept inbound
connections, but its public IPs are still reachable from the internet, and
they’re the identity of everything behind them. Partners, SaaS providers and
banks often allow-list these IPs, so anyone who learns them can aim traffic at
them. Every VM in the associated subnets shares the same IPs, so a single flood
can cut off API calls, partner integrations, updates and telemetry all at once.
An attacker doesn’t need to reach your workloads to cause an outage, only to
break their path to the internet.
Now your outbound IPs get
automatic network-layer mitigation, plus the DDoS metrics, diagnostics and
alerts you already rely on. It also simplifies compliance, because policies
requiring DDoS protection on all public IPs no longer need an exception for NAT
Gateway.
Learn
more.