Skip to content

Commit 04fcf1f

Browse files
name fix - how to TS integration
1 parent 3149248 commit 04fcf1f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/virtual-network/nat-gateway/troubleshoot-nat-and-azure-services.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot outbound connectivity with Azure services
33
titleSuffix: Azure Virtual Network
4-
description: Troubleshoot issues with Virtual Network NAT and Azure services.
4+
description: Troubleshoot issues with NAT gateway and Azure services.
55
author: asudbring
66
ms.service: virtual-network
77
ms.subservice: nat
@@ -107,7 +107,7 @@ Update your idle timeout timer configuration on your User-Assigned NAT gateway w
107107

108108
### How NAT gateway integration with Azure Firewall works
109109

110-
Azure Firewall can provide outbound connectivity to the internet from virtual networks. Azure Firewall provides only 2,496 SNAT ports per public IP address. While Azure Firewall can be associated with up to 250 public IP addresses to handle egress traffic, often, customers require much fewer public IP addresses for connecting outbound due to various architectural requirements and limitations by destination endpoints for the number of public IP addresses they can allowlist. One method by which to get around this allowlist IP limitation and to also reduce the risk of SNAT port exhaustion is to use NAT gateway in the same subnet with Azure Firewall. To learn how to set up NAT gateway in an Azure Firewall subnet, see [Scale SNAT ports with Azure Virtual Network NAT](../../firewall/integrate-with-nat-gateway.md).
110+
Azure Firewall can provide outbound connectivity to the internet from virtual networks. Azure Firewall provides only 2,496 SNAT ports per public IP address. While Azure Firewall can be associated with up to 250 public IP addresses to handle egress traffic, often, customers require much fewer public IP addresses for connecting outbound due to various architectural requirements and limitations by destination endpoints for the number of public IP addresses they can allowlist. One method by which to get around this allowlist IP limitation and to also reduce the risk of SNAT port exhaustion is to use NAT gateway in the same subnet with Azure Firewall. To learn how to set up NAT gateway in an Azure Firewall subnet, see [Scale SNAT ports with Azure NAT Gateway](../../firewall/integrate-with-nat-gateway.md).
111111

112112
## Azure Databricks
113113

@@ -125,8 +125,8 @@ We're always looking to improve the experience of our customers. If you're exper
125125

126126
To learn more about NAT gateway, see:
127127

128-
* [Virtual Network NAT](./nat-overview.md)
128+
* [Azure NAT Gateway](./nat-overview.md)
129129

130130
* [NAT gateway resource](./nat-gateway-resource.md)
131131

132-
* [Metrics and alerts for NAT gateway resources](./nat-metrics.md)
132+
* [Metrics and alerts for NAT gateway resources](./nat-metrics.md)

0 commit comments

Comments
 (0)