Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into expandSizeCheck

roygara · roygara · commit bd5a0ec068e1 · 2022-12-09T11:29:33.000-08:00
diff --git a/articles/communication-services/concepts/telephony/certified-session-border-controllers.md b/articles/communication-services/concepts/telephony/certified-session-border-controllers.md
@@ -55,4 +55,4 @@ Note the certification granted to a major version. That means that firmware with
 
 ### Quickstarts
 
-- [Call to Phone](../../quickstarts/telephony/pstn-call.md)
+- [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)
diff --git a/articles/communication-services/concepts/telephony/direct-routing-infrastructure.md b/articles/communication-services/concepts/telephony/direct-routing-infrastructure.md
@@ -110,8 +110,10 @@ The SBC makes a DNS query to resolve sip.pstnhub.microsoft.com. Based on the SBC
 
 ## Media traffic: IP and Port ranges
 
-The media traffic flows to and from a separate service called Media Processor. At the moment of publishing, Media Processor for Communication Services can use any Azure IP address. 
-Download [the full list of addresses](https://www.microsoft.com/download/details.aspx?id=56519).
+The media traffic flows to and from a separate service called Media Processor. The IP address ranges for media traffic are the same as for signaling:
+
+- `52.112.0.0/14 (IP addresses from 52.112.0.1 to 52.115.255.254)`
+- `52.120.0.0/14 (IP addresses from 52.120.0.1 to 52.123.255.254)`
 
 ### Port ranges
 The port ranges of the Media Processors are shown in the following table: 
diff --git a/articles/communication-services/concepts/telephony/emergency-calling-concept.md b/articles/communication-services/concepts/telephony/emergency-calling-concept.md
@@ -71,5 +71,5 @@ There is also an option to use purchased number as a caller ID for direct routin
 
 ### Quickstarts
 
-- [Call to Phone](../../quickstarts/telephony/pstn-call.md)
+- [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)
 - [Add Emergency Calling to your app](../../quickstarts/telephony/pstn-call.md)
diff --git a/articles/communication-services/concepts/telephony/known-limitations-acs-telephony.md b/articles/communication-services/concepts/telephony/known-limitations-acs-telephony.md
@@ -49,4 +49,4 @@ This article provides information about limitations and known issues related to
 
 ### Quickstarts
 
-- [Call to Phone](../../quickstarts/telephony/pstn-call.md)
+- [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)
diff --git a/articles/iot-hub-device-update/configure-access-control-device-update.md b/articles/iot-hub-device-update/configure-access-control-device-update.md
@@ -1,7 +1,7 @@
 ---
 title: Configure Access Control in Device Update for IoT Hub | Microsoft Docs
 description: Configure Access Control in Device Update for IoT Hub.
-author: eshashah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 10/31/2022
 ms.topic: how-to
diff --git a/articles/iot-hub-device-update/create-device-update-account.md b/articles/iot-hub-device-update/create-device-update-account.md
@@ -1,7 +1,7 @@
 ---
 title: Create an account for Device Update for Azure IoT Hub
 description: Create a device update account and instance in Device Update for Azure IoT Hub using the Azure portal or CLI.
-author: eshashah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 10/30/2022
 ms.topic: how-to
diff --git a/articles/iot-hub-device-update/device-update-agent-overview.md b/articles/iot-hub-device-update/device-update-agent-overview.md
@@ -1,7 +1,7 @@
 ---
 title: Understand Device Update for Azure IoT Hub Agent| Microsoft Docs
 description: Understand Device Update for Azure IoT Hub Agent.
-author: EshaShah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 9/12/2022
 ms.topic: conceptual
diff --git a/articles/iot-hub-device-update/device-update-agent-provisioning.md b/articles/iot-hub-device-update/device-update-agent-provisioning.md
@@ -1,7 +1,7 @@
 ---
 title: Provisioning Device Update for Azure IoT Hub Agent| Microsoft Docs
 description: Provisioning Device Update for Azure IoT Hub Agent
-author: EshaShah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 8/26/2022
 ms.topic: how-to
diff --git a/articles/iot-hub-device-update/device-update-configuration-file.md b/articles/iot-hub-device-update/device-update-configuration-file.md
@@ -1,7 +1,7 @@
 ---
 title: Understand Device Update for Azure IoT Hub Configuration File| Microsoft Docs
 description: Understand Device Update for Azure IoT Hub  Configuration File.
-author: EshaShah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 08/27/2022
 ms.topic: conceptual
diff --git a/articles/iot-hub-device-update/device-update-plug-and-play.md b/articles/iot-hub-device-update/device-update-plug-and-play.md
@@ -1,7 +1,7 @@
 ---
 title: Understand how Device Update for IoT Hub uses IoT Plug and Play | Microsoft Docs
 description: Device Update for IoT Hub uses to discover and manage devices that are over-the-air update capable.
-author: EshaShah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 1/26/2022
 ms.topic: conceptual
diff --git a/articles/iot-hub-device-update/migration-public-preview-refresh-to-ga.md b/articles/iot-hub-device-update/migration-public-preview-refresh-to-ga.md
@@ -1,7 +1,7 @@
 ---
 title: Migrating to the latest Device Update for IoT Hub release | Microsoft Docs
 description: Understand how to migrate to latest Device Update for IoT Hub release
-author: EshaShah
+author: eshashah-msft
 ms.author: eshashah
 ms.date: 9/15/2022
 ms.topic: how-to
diff --git a/articles/iot-hub-device-update/monitor-device-update-iot-hub.md b/articles/iot-hub-device-update/monitor-device-update-iot-hub.md
@@ -1,7 +1,7 @@
 ---
 title: Monitoring Device Update for IoT Hub
 description: Start here to learn how to monitor Device Update for IoT Hub 
-author: eshashah
+author: eshashah-msft
 ms.author: eshashah
 ms.topic: conceptual 
 ms.service: iot-hub
diff --git a/articles/virtual-network/nat-gateway/nat-gateway-resource.md b/articles/virtual-network/nat-gateway/nat-gateway-resource.md
@@ -7,27 +7,29 @@ ms.service: virtual-network
 ms.subservice: nat
 ms.topic: article
 ms.workload: infrastructure-services
-ms.custom: ignite-2022
-ms.date: 02/25/2022
+ms.custom: ignite-2022, FY23 content-maintenance
+ms.date: 12/06/2022
 ms.author: allensu
 ---
 
 # Design virtual networks with NAT gateway
 
 NAT gateway provides outbound internet connectivity for one or more subnets of a virtual network. Once NAT gateway is associated to a subnet, NAT provides source network address translation (SNAT) for that subnet. NAT gateway specifies which static IP addresses virtual machines use when creating outbound flows. Static IP addresses come from public IP addresses, public IP prefixes, or both. If a public IP prefix is used, all IP addresses of the entire public IP prefix are consumed by a NAT gateway. A NAT gateway can use up to 16 static IP addresses from either.
 
-:::image type="content" source="./media/nat-overview/flow-direction1.png" alt-text="Diagram depicts a NAT gateway resource that consumes all IP addresses for a public IP prefix and directs traffic to and from two subnets of VMs and a virtual machine scale set.":::
+:::image type="content" source="./media/nat-overview/flow-direction1.png" alt-text="Diagram of a NAT gateway resource with virtual machines and a Virtual Machine Scale Set.":::
 
 *Figure: Virtual Network NAT for outbound to internet*
 
 ## How to deploy NAT
 
-Configuring and using NAT gateway is intentionally made simple:
+Deployments are intentionally made simple:
 
 NAT gateway:
 
 - Create a non-zonal or zonal NAT gateway.
+
 - Assign a public IP address or public IP prefix.
+
 - If necessary, modify TCP idle timeout (optional). Review [timers](#timers) before you change the default.
 
 Virtual network:
@@ -52,13 +54,13 @@ NAT gateway is recommended for all production workloads where you need to connec
 
 ### Coexistence of outbound and inbound connectivity 
 
-NAT gateway, Load balancer and instance-level public IPs are flow direction aware. NAT gateway can coexist in the same virtual network as Load balancer and IL PIPs to provide outbound and inbound connectivity seamlessly. Inbound traffic through Load balancer or IL PIPs is translated separately from outbound traffic through NAT gateway. 
+NAT gateway, load balancer and instance-level public IPs are flow direction aware. NAT gateway can coexist in the same virtual network as a load balancer and instance-level public IPs to provide outbound and inbound connectivity seamlessly. Inbound traffic through a load balancer or instance-level public IPs is translated separately from outbound traffic through NAT gateway. 
 
-The following scenarios are examples of how to ensure coexistence of Load balancer or instance level public IPs for inbound with NAT gateway for outbound.
+The following examples demonstrate co-existence of a load balancer or instance-level public IPs with a NAT gateway. Inbound traffic traverses the load balancer or public IP. Outbound traffic traverses the NAT gateway.
 
 #### NAT and VM with an instance-level public IP
 
-:::image type="content" source="./media/nat-overview/flow-direction2.png" alt-text="Diagram that depicts a NAT gateway resource that consumes all IP addresses for a public IP prefix and directs that traffic to and from two subnets that contain VMs and a virtual machine scale set.":::
+:::image type="content" source="./media/nat-overview/flow-direction2.png" alt-text="Diagram of a NAT gateway resource that consumes all IP addresses for a public IP prefix. The NAT gateway directs traffic for two subnets of VMs and a Virtual Machine Scale Set.":::
 
 *Figure: Virtual Network NAT and VM with an instance level public IP*
 
@@ -84,7 +86,7 @@ Any outbound configuration from a load-balancing rule or outbound rules is super
 
 #### NAT and VM with an instance-level public IP and a standard public load balancer
 
-:::image type="content" source="./media/nat-overview/flow-direction4.png" alt-text="Diagram that depicts a NAT gateway that supports outbound traffic to the internet from a virtual network and inbound traffic with an instance-level public I P and a public load balancer.":::
+:::image type="content" source="./media/nat-overview/flow-direction4.png" alt-text="Diagram of a NAT gateway that supports outbound traffic to the internet from a virtual network. Inbound traffic is depicted with an instance-level public IP and a public load balancer.":::
 
 *Figure: Virtual Network NAT and VM with an instance-level public IP and a standard public load balancer*
 
@@ -136,21 +138,21 @@ NAT gateway interacts with IP and IP transport headers of UDP and TCP flows. NAT
 
 Source Network Address Translation (SNAT) rewrites the source of a flow to originate from a different IP address and/or port. Typically, SNAT is used when a private network needs to connect to a public host over the internet. SNAT allows multiple VM instances within the private VNet to use the same single Public IP address or set of IP addresses (prefix) to connect to the internet.
 
-NAT gateway SNATs the private IP address and port of a virtual machine to a static public IP address and SNAT port before going outbound to the internet from a virtual network. Each new connection to the same destination endpoint uses a different SNAT port so that connections can be distinguished from one another. SNAT port exhaustion occurs when a source endpoint has run out of available SNAT ports to differentiate between new connections.
+NAT gateway uses SNAT to translate the private IP address and port of a virtual machine to a static public IP address and port. Traffic is translated before leaving the virtual network for the Internet.  Each new connection to the same destination endpoint uses a different SNAT port so that connections can be distinguished from one another. SNAT port exhaustion occurs when a source endpoint has run out of available SNAT ports to differentiate between new connections.
 
 ### Example SNAT flows for NAT gateway
 
 The following example flows explain the basic concept of SNAT and how it works with NAT gateway. 
 
-In the table below the VM makes connections to destination IP 65.52.0.1 from the following source tuples (IPs and ports):
+In the following table, the VM makes connections to destination IP 65.52.0.1 from the following source tuples (IPs and ports):
 
 | Flow | Source tuple | Destination tuple |
 |:---:|:---:|:---:|
 | 1 | 192.168.0.16:4283 | 65.52.0.1:80 |
 | 2 | 192.168.0.16:4284 | 65.52.0.1:80 |
 | 3 | 192.168.0.17.5768 | 65.52.0.1:80 |
 
-When NAT gateway is configured with public IP address 65.52.1.1, the source IPs are SNAT'd into NAT gateway's public IP address and a SNAT port as shown below:
+When NAT gateway is configured with public IP address 65.52.1.1, the source IPs are translated into NAT gateway's public IP address and a SNAT port:
 
 | Flow | Source tuple | Source tuple after SNAT | Destination tuple |
 |:---:|:---:|:---:|:---:|
@@ -170,21 +172,21 @@ NAT gateway dynamically allocates SNAT ports across a subnet's private resources
 
 Pre-allocation of SNAT ports to each virtual machine isn't required, which means SNAT ports aren't left unused by VMs not actively needing them.
 
-:::image type="content" source="./media/nat-overview/exhaustion-threshold.png" alt-text="Diagram that depicts the inventory of all available SNAT ports used by any VM on subnets configured with NAT with an exhaustion threshold.":::
+:::image type="content" source="./media/nat-overview/exhaustion-threshold.png" alt-text="Diagram of all available SNAT ports used by virtual machines on subnets configured with NAT and an exhaustion threshold.":::
 
 *Figure: Differences in exhaustion scenarios*
 
 After a SNAT port is released, it's available for use by any VM on subnets configured with NAT. On-demand allocation allows dynamic and divergent workloads on subnets to use SNAT ports as needed. As long as SNAT ports are available, SNAT flows will succeed. 
 
 ### Source (SNAT) port reuse
 
-NAT gateway selects a port at random out of the available inventory of ports to make new outbound connections. If NAT gateway doesn't find any available SNAT ports, then it will reuse a SNAT port. A SNAT port can be reused when connecting to a different destination IP and port as shown below with this extra flow.
+NAT gateway selects a port at random out of the available inventory of ports to make new outbound connections. If NAT gateway doesn't find any available SNAT ports, then it will reuse a SNAT port. A SNAT port can be reused when connecting to a different destination IP and port as shown in the following table with this extra flow.
 
 | Flow | Source tuple | Destination tuple |
 |:---:|:---:|:---:|
 | 4 | 192.168.0.16:4285 | 65.52.0.2:80 |
 
-A NAT gateway will translate flow 4 to a SNAT port that may already be in use for other destinations as well (see flow 1 from table above). See [Scale NAT gateway](#scalability) for more discussion on correctly sizing your IP address provisioning.
+A NAT gateway will translate flow 4 to a SNAT port that may already be in use for other destinations as well (see flow 1 from previous table). See [Scale NAT gateway](#scalability) for more discussion on correctly sizing your IP address provisioning.
 
 | Flow | Source tuple | Source tuple after SNAT | Destination tuple |
 |:---:|:---:|:---:|:---:|
@@ -226,15 +228,15 @@ Design recommendations for configuring timers:
 
 - TCP keepalives can be used to provide a pattern of refreshing long idle connections and endpoint liveness detection. TCP keepalives appear as duplicate ACKs to the endpoints, are low overhead, and invisible to the application layer.
 
-- Because UDP idle timeout timers aren't configurable, UDP keepalives should be used to ensure that the idle timeout value isn't reached, and that the connection is maintained. Unlike TCP connections, a UDP keepalive enabled on one side of the connection only applies to traffic flow in one direction. UDP keepalives must be enabled on both sides of the traffic flow in order to keep the traffic flow alive.
+- UDP idle timeout timers aren't configurable, UDP keepalives should be used to ensure that the idle timeout value isn't reached, and that the connection is maintained. Unlike TCP connections, a UDP keepalive enabled on one side of the connection only applies to traffic flow in one direction. UDP keepalives must be enabled on both sides of the traffic flow in order to keep the traffic flow alive.
 
 ## Limitations
 
 - Basic load balancers and basic public IP addresses aren't compatible with NAT. Use standard SKU load balancers and public IPs instead.
   
-  - To upgrade a basic load balancer to standard, see [Upgrade Azure Public Load Balancer](../../load-balancer/upgrade-basic-standard.md)
+  - To upgrade a load balancer from basic to standard, see [Upgrade Azure Public Load Balancer](../../load-balancer/upgrade-basic-standard.md)
   
-  - To upgrade a basic public IP address to standard, see [Upgrade a public IP address](../ip-services/public-ip-upgrade-portal.md)
+  - To upgrade a public IP address from basic to standard, see [Upgrade a public IP address](../ip-services/public-ip-upgrade-portal.md)
 
 - NAT gateway doesn't support ICMP 
 

Original file line number	Diff line number	Diff line change
`@@ -55,4 +55,4 @@ Note the certification granted to a major version. That means that firmware with`
`55`	`55`
`56`	`56`	`### Quickstarts`
`57`	`57`
`58`		`-- [Call to Phone](../../quickstarts/telephony/pstn-call.md)`
	`58`	`+- [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)`
Original file line number	Diff line number	Diff line change
`@@ -49,4 +49,4 @@ This article provides information about limitations and known issues related to`
`49`	`49`
`50`	`50`	`### Quickstarts`
`51`	`51`
`52`		`-- [Call to Phone](../../quickstarts/telephony/pstn-call.md)`
	`52`	`+- [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)`