Skip to content

Commit 84f1721

Browse files
authored
Merge pull request #180183 from asudbring/nat-faq
Added FAQ for Virtual Network NAT
2 parents 608d0e0 + 599cbed commit 84f1721

File tree

2 files changed

+73
-0
lines changed

2 files changed

+73
-0
lines changed
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
### YamlMime:FAQ
2+
metadata:
3+
title: Virtual Network NAT frequently asked questions
4+
description: Answers to common questions about using Azure Virtual Network NAT.
5+
6+
title: Frequently asked questions for Azure Virtual Network NAT
7+
summary: |
8+
Here are some answers to common questions about using Azure Virtual Network NAT.
9+
10+
sections:
11+
- name: Single section - ignored
12+
questions:
13+
- question: Is the Virtual Network NAT public IP address static?
14+
answer: |
15+
Yes. When Virtual Network NAT is configured on a subnet, all outbound connectivity uses your specified static public IP address(es).
16+
17+
- question: What is the maximum number of public IP addresses that can be used by Virtual Network NAT?
18+
answer: |
19+
The Virtual Network NAT gateway resource can use up to 16 public IP addresses. The Virtual Network NAT can use any combination of public IP addresses and public IP address prefixes totaling to 16 addresses. The maximum prefix size that can be used by Virtual Network NAT is /28 (16 addresses).
20+
21+
- question: Can IPs of existing Virtual Network NAT be changed?
22+
answer: |
23+
No, an existing IP attached to the Virtual Network NAT can't be changed. A different IP can be attached to Virtual Network NAT by creating a new public IP address. Associate the new public IP address with the NAT gateway resource. Disassociate the old IP address.
24+
25+
- question: If multiple public IP addresses are assigned to a NAT gateway resource, is there a disruption of traffic if one of the IP addresses is removed?
26+
answer: |
27+
No. If the Virtual Network NAT gateway resource has multiple public IPs, it will load balance traffic between the assigned IPs. Removing one of the IPs won't cause any downtime. It's advised that if you decide to remove one of the public IP addresses from the NAT gateway resource, use a maintenance window for the removal.
28+
29+
- question: Can Virtual Network NAT be attached to multiple virtual networks?
30+
answer: |
31+
No. Virtual Network NAT cannot be attached to multiple virtual networks.
32+
33+
- question: Can Virtual Network NAT be attached to multiple subnets?
34+
answer: |
35+
Yes. Virtual Network NAT can be associated with multiple subnets within a virtual network. It isn't required to be associated with all subnets within a virtual network. Each subnet within a virtual network can be configured with its own Virtual Network NAT.
36+
37+
- question: Can Virtual Network NAT be associated with a gateway subnet?
38+
answer: |
39+
No. Virtual Network NAT can't be associated with a [gateway](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings#gwsub) subnet.
40+
41+
- question: How does Virtual Network NAT work with Availability zones?
42+
answer: |
43+
Virtual Network NAT can be non-zonal or zonal only.
44+
45+
A non-zonal Virtual Network NAT is one that hasn't been associated to a specific zone. A non-zonal Virtual Network NAT is still assigned to one zone within the virtual network. In this instance, Azure decides which zone to choose for the Virtual Network NAT.
46+
47+
A zonal Virtual Network NAT is associated to a specific zone by the user when the Virtual Network NAT is created.
48+
49+
- question: How can I obtain logs for my Virtual Network NAT resource?
50+
answer: |
51+
Network security groups (NSG) can be configured to outbound traffic sent from a resource in a subnet/virtual network through a virtual network NAT gateway resource.
52+
53+
Network security group flow logs can be used to monitor outbound traffic through a Virtual Network NAT gateway resource.
54+
55+
Use Azure Security Center and follow the network protection recommendations to help secure your Azure network resources. Enable network security group flow logs and send the logs to an Azure Storage account for auditing. You can also send the flow logs to a Log Analytics workspace and then use Traffic Analytics to provide insights into traffic patterns in your Azure cloud. Some advantages of Traffic Analytics are the ability to visualize network activity, identify hot spots and security threats, understand traffic flow patterns, and pinpoint network misconfigurations.
56+
57+
- question: How do I delete a Virtual Network NAT gateway resource?
58+
answer: |
59+
To delete a Virtual Network NAT gateway resource, the resource must first be disassociated from the subnet. Once the NAT gateway resource is disassociated from all subnets, it can be deleted.
60+
61+
- question: Can I use the Virtual Network NAT gateway resource with Azure App Services?
62+
answer: |
63+
Yes. For more information about Virtual Network NAT integration with Azure App Services, see [Virtual Network NAT gateway integration](https://docs.microsoft.com/azure/app-service/networking/nat-gateway-integration).
64+
65+
- question: Can I use the Virtual Network NAT gateway resource with Azure Kubernetes Service?
66+
answer: |
67+
Yes. For more information about Virtual Network NAT integration with Azure Kubernetes Service, see [Managed NAT Gateway (preview)](https://docs.microsoft.com/azure/aks/nat-gateway).
68+
69+
additionalContent: |
70+
## Next steps
71+
If your question is not listed above, please send feedback about this page with your question. This will create a GitHub issue for the product team to ensure all of our valued customer questions are answered.

articles/virtual-network/nat-gateway/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,3 +78,5 @@ items:
7878
href: https://azure.microsoft.com/pricing/calculator/
7979
- name: Stack Overflow
8080
href: https://stackoverflow.com/questions/tagged/azure-virtual-network
81+
- name: FAQ
82+
href: faq.yml

0 commit comments

Comments
 (0)