Blog Post

Azure Network Security Blog
4 MIN READ

DDoS Support for NATGWv2 IP - Public Preview

Jdasari's avatar
Jdasari
Icon for Microsoft rankMicrosoft
Nov 16, 2026

Introduction

Azure DDoS Protection now covers the public IP addresses used by Azure NAT Gateway StandardV2, in public preview. Customers can protect the StandardV2 IPv4 and IPv6 public IPs that carry their outbound internet traffic from network-layer DDoS attacks, using the same DDoS Network Protection and IP Protection they already use. There's no new API, feature registration or appliance to manage, and DDoS protection doesn't open the gateway to unsolicited inbound connections.

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.

  • Your outbound IPs are known to others. Every external service your workloads call sees these IPs. Partners, SaaS providers and banks often keep them on allow-lists. Anyone who learns them can aim traffic at them.
  • One IP set serves many workloads. Every VM in the associated subnets shares the gateway's public IPs. A flood that saturates these IPs can disrupt outbound connectivity for all of them at once. That includes calls to external APIs, partner integrations, package and update downloads, and telemetry.
  • Outbound failures hurt production. An attack on the NAT IPs doesn't have to reach your workloads to cause an outage. It only has to break their path to the internet.
  • Same protection as your inbound endpoints. Until now, customers could protect inbound public IPs but not the IPs behind NAT Gateway StandardV2. With this preview, outbound IPs get automatic network-layer mitigation, plus the DDoS metrics, diagnostics and alerts they already use.
  • Easier compliance. Security policies and posture checks that require DDoS protection on all public IPs no longer have an exception for NAT Gateway IPs.

 

 

Figure 1: Outbound workloads use a StandardV2 NAT Gateway and a DDoS-protected public IP to reach the internet. Conceptual diagram, not an Azure portal screenshot.

Protect the public IPs behind your outbound connectivity

A NAT gateway uses its associated public IP addresses when workloads initiate connections to the internet. With this preview, eligible StandardV2 IPv4 and IPv6 public IP addresses can receive Azure DDoS Protection while associated with a StandardV2 NAT Gateway.

 

 

Figure 2: The Outbound IP blade of a StandardV2 NAT Gateway lists an individual public IP address and a public IP prefix. Resource names, subscription details, and IP addresses in this and the following screenshots are generic examples.

You use the familiar Azure DDoS Protection model. There is no separate DDoS setting on the NAT Gateway resource:

  • DDoS Network Protection: Protect eligible NAT Gateway public IPs through the virtual network's protection configuration when the gateway is associated with a subnet in that virtual network.
  • DDoS IP Protection: Enable protection on an eligible individual public IP address associated with StandardV2 NAT Gateway.

This brings network-layer DDoS protection to a public IP that plays an important role in your outbound architecture, without changing how NAT Gateway establishes outbound connections. It does not make NAT Gateway an inbound endpoint: unsolicited inbound connections remain blocked.

See it in the Azure portal

The Configure DDoS Protection pane on the public IP resource shows the protection status and lets you choose the protection type.

Network Protection, inherited from the virtual network. The public IP shows Protected: IP is DDoS protected, with the Network type selected. This type inherits DDoS protection from the virtual network.

 

 

Figure 3: The public IP shows protected status with Network Protection inherited from the virtual network.

IP Protection, specific to the public IP. Selecting the IP type applies protection to this IP address only. The pane lets you add the IP to an existing DDoS protection plan and pick that plan from a list.

 

 

Figure 4: The same public IP shows protected status with IP Protection selected and an existing DDoS protection plan.

Disabled. Selecting Disable shows the public IP as unprotected, even when protection is configured on the virtual network. The pane warns that the IP will not receive any protection while this option is selected.

 

 

Figure 5: Selecting Disable shows the public IP as unprotected, even when protection is configured on the virtual network.

Get started in the Azure portal

  1. Create or use a StandardV2 NAT Gateway, associate it with your workload subnet, and configure an eligible native StandardV2 public IP address.
  2. Choose your protection model. For Network Protection, configure Azure DDoS Protection on the virtual network. For IP Protection, open the individual Public IP address resource and configure DDoS protection there.
  3. Return to the public IP resource to check its protection status. Use its monitoring experience to review applicable DDoS metrics and alerts.

The portal experience follows the existing public IP workflow. Depending on your configuration, the public IP can show protection inherited from the virtual network or IP-specific protection.

Preview scope and considerations

This preview supports eligible native StandardV2 IPv4 and IPv6 public IP addresses used with StandardV2 NAT Gateway. Some scenarios are not part of it:

  • It does not extend DDoS protection to the Standard NAT Gateway SKU.
  • DDoS custom policies for NAT Gateway public IPs are not part of the initial preview.

 

Public IP prefixes are supported only through DDoS Network Protection. When a virtual network uses Network Protection, the protection is inherited and applies automatically to the entire IP prefix. DDoS IP Protection does not support public IP prefixes.

 

 

 

Figure 6: The StandardV2 public IP prefix resource overview. This screenshot does not establish IP-level protection eligibility for a prefix.

 

 

Figure 7: The prefix Metrics blade lists DDoS-related metrics. Metric availability alone does not establish the final preview support boundary.

Azure DDoS Protection addresses network-layer attacks. It is not a substitute for application-layer protection where your architecture requires it.

Ready to explore?

Start with a StandardV2 NAT Gateway and an eligible native StandardV2 public IP, then choose the virtual-network or individual-public-IP protection model that fits your deployment.

Published Nov 16, 2026
Version 1.0
No CommentsBe the first to comment