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

Author: asudbring

articles/azure-functions/create-first-function-vs-code-java.md

@@ -47,7 +47,7 @@ In this section, you use Visual Studio Code to create a local Azure Functions pr
     |Prompt|Selection|
     |--|--|
     |**Select a language**| Choose `Java`.|
-    |**Select a version of Java**| Choose `Java 11` or `Java 8`, the Java version on which your functions run in Azure. Choose a Java version that you've verified locally. |
+    |**Select a version of Java**| Choose `Java 8`,  `Java 11`, `Java 17` or `Java 21`, the Java version on which your functions run in Azure. Choose a Java version that you've verified locally. |
     | **Provide a group ID** | Choose `com.function`. |
     | **Provide an artifact ID** | Choose `myFunction`. |
     | **Provide a version** | Choose `1.0-SNAPSHOT`. |

articles/azure-functions/functions-create-first-java-gradle.md

@@ -20,7 +20,7 @@ This article shows you how to build and publish a Java function project to Azure
 
 To develop functions using Java, you must have the following installed:
 
-- [Java Developer Kit](/azure/developer/java/fundamentals/java-support-on-azure), version 8
+- [Java Developer Kit](/azure/developer/java/fundamentals/java-support-on-azure), version 8, 11, 17 or 21. (Java 21 is currently supported in preview on Linux only)
 - [Azure CLI]
 - [Azure Functions Core Tools](./functions-run-local.md#v2) version 2.6.666 or above
 - [Gradle](https://gradle.org/), version 6.8 and above

articles/azure-functions/functions-create-maven-intellij.md

@@ -24,7 +24,7 @@ Specifically, this article shows you:
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
-- An [Azure supported Java Development Kit (JDK)](/azure/developer/java/fundamentals/java-support-on-azure) for Java, version 8, 11, or 17
+- An [Azure supported Java Development Kit (JDK)](/azure/developer/java/fundamentals/java-support-on-azure), version 8, 11, 17 or 21. (Java 21 is currently only supported in preview on Linux only)
 - An [IntelliJ IDEA](https://www.jetbrains.com/idea/download/) Ultimate Edition or Community Edition installed
 - [Maven 3.5.0+](https://maven.apache.org/download.cgi)
 - Latest [Function Core Tools](https://github.com/Azure/azure-functions-core-tools)

articles/nat-gateway/nat-metrics.md

@@ -1,15 +1,15 @@
 ---
 title: Metrics and alerts for Azure NAT Gateway
-titleSuffix: Azure Virtual Network
-description: Understand Azure Monitor metrics and alerts available for NAT gateway.
+titleSuffix: Azure NAT Gateway
+description: Get started learning about Azure Monitor metrics and alerts available for monitoring Azure NAT Gateway.
 author: asudbring
 ms.service: nat-gateway
-# Customer intent: As an IT administrator, I want to understand available Azure Monitor metrics and alerts for Virtual Network NAT.
-ms.topic: conceptual
-ms.date: 04/12/2022
+ms.topic: how-to
+ms.date: 01/30/2024
 ms.author: allensu
+# Customer intent: As an IT administrator, I want to understand available Azure Monitor metrics and alerts for Virtual Network NAT.
 ---
-# Azure NAT Gateway metrics and alerts
+# What is Azure NAT Gateway metrics and alerts?
 
 This article provides an overview of all NAT gateway metrics and diagnostic capabilities. This article provides general guidance on how to use metrics and alerts to monitor, manage, and [troubleshoot](troubleshoot-nat.md) your NAT gateway resource. 
 
@@ -19,7 +19,7 @@ Azure NAT Gateway provides the following diagnostic capabilities:
 
 - Network Insights: Azure Monitor Insights provides you with visual tools to view, monitor, and assist you in diagnosing issues with your NAT gateway resource. Insights provide you with a topological map of your Azure setup and metrics dashboards. 
 
-:::image type="content" source="./media/nat-overview/flow-direction1.png" alt-text="Diagram of a NAT gateway that consumes all IP addresses for a public IP prefix. The NAT gateway 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 uses all IP addresses for a public IP prefix. The NAT gateway directs traffic between subnets of VMs and a virtual machine scale set":::
 
 *Figure: Azure NAT Gateway for outbound to Internet*
 
@@ -29,19 +29,19 @@ NAT gateway provides the following multi-dimensional metrics in Azure Monitor:
 
 | Metric | Description | Recommended aggregation | Dimensions |
 |---|---|---|---|
-| Bytes | Bytes processed inbound and outbound | Sum | Direction (In; Out), Protocol (6 TCP; 17 UDP) |
-| Packets | Packets processed inbound and outbound | Sum | Direction (In; Out), Protocol (6 TCP; 17 UDP) |
+| Bytes | Bytes processed inbound and outbound | Sum | **Direction (In; Out)**, **Protocol (6 TCP; 17 UDP)** |
+| Packets | Packets processed inbound and outbound | Sum | **Direction (In; Out)**, **Protocol (6 TCP; 17 UDP)** |
 | Dropped Packets | Packets dropped by the NAT gateway | Sum | / |
-| SNAT Connection Count | Number of new SNAT connections over a given interval of time | Sum | Connection State (Attempted, Failed), Protocol (6 TCP; 17 UDP) |
-| Total SNAT Connection Count | Total number of active SNAT connections | Sum | Protocol (6 TCP; 17 UDP) |
-| Datapath Availability | Availability of the data path of the NAT gateway. Used to determine whether the NAT gateway endpoints are available for outbound traffic flow. | Avg | Availability (0, 100) |
+| SNAT Connection Count | Number of new SNAT connections over a given interval of time | Sum | **Connection State (Attempted, Failed)**, **Protocol (6 TCP; 17 UDP)** |
+| Total SNAT Connection Count | Total number of active SNAT connections | Sum | **Protocol (6 TCP; 17 UDP)** |
+| Datapath Availability | Availability of the data path of the NAT gateway. Used to determine whether the NAT gateway endpoints are available for outbound traffic flow. | Avg | **Availability (0, 100)** |
 
 >[!NOTE]
 > Count aggregation is not recommended for any of the NAT gateway metrics. Count aggregation adds up the number of metric values and not the metric values themselves. Use Sum aggregation instead to get the best representation of data values for connection count, bytes, and packets metrics.
 >
 > Use average for best represented health data for the datapath availability metric.
 >
-> See [aggregation types](/azure/azure-monitor/essentials/metrics-aggregation-explained#aggregation-types) for more information.
+> For information about aggregation types, see [aggregation types](/azure/azure-monitor/essentials/metrics-aggregation-explained#aggregation-types).
 
 ## Where to find my NAT gateway metrics
 
@@ -61,18 +61,20 @@ To view any one of your metrics for a given NAT gateway resource:
 
 1. Select the NAT gateway resource you would like to monitor.
 
-2. In the **Metric** drop-down menu, select one of the provided metrics.
+1. In the **Metric** drop-down menu, select one of the provided metrics.
 
-3. In the **Aggregation** drop-down menu, select the recommended aggregation listed in the [metrics overview](#metrics-overview) table.
+1. In the **Aggregation** drop-down menu, select the recommended aggregation listed in the [metrics overview](#metrics-overview) table.
 
     :::image type="content" source="./media/nat-metrics/nat-metrics-1.png" alt-text="Screenshot of the metrics set up in NAT gateway resource.":::
 
-4. To adjust the time frame over which the chosen metric is presented on the metrics graph or to adjust how frequently the chosen metric is measured, select the **Time** window in the top right corner of the metrics page and make your adjustments.
+1. To adjust the time frame over which the chosen metric is presented on the metrics graph or to adjust how frequently the chosen metric is measured, select the **Time** window in the top right corner of the metrics page and make your adjustments.
 
     :::image type="content" source="./media/nat-metrics/nat-metrics-2.png" alt-text="Screenshot of the metrics time setup configuration in NAT gateway resource.":::
 
 ## How to use NAT gateway metrics
 
+The following sections detail how to use each NAT gateway metric to monitor, manage, and troubleshoot your NAT gateway resource.
+
 ### Bytes
 
 The **Bytes** metric shows you the amount of data going outbound through NAT gateway and returning inbound in response to an outbound connection. 
@@ -85,19 +87,19 @@ To view the amount of data passing through NAT gateway:
 
 1. Select the NAT gateway resource you would like to monitor. 
 
-2. In the **Metric** drop-down menu, select the **Bytes** metric. 
+1. In the **Metric** drop-down menu, select the **Bytes** metric. 
 
-3. In the **Aggregation** drop-down menu, select **Sum**.
+1. In the **Aggregation** drop-down menu, select **Sum**.
 
-4. Select to **Add filter**.
+1. Select to **Add filter**.
 
-5. In the **Property** drop-down menu, select **Direction (Out | In)**.
+1. In the **Property** drop-down menu, select **Direction (Out | In)**.
 
-6. In the **Values** drop-down menu, select **Out**, **In**, or both. 
+1. In the **Values** drop-down menu, select **Out**, **In**, or both. 
 
-7. To see data processed inbound or outbound as their own individual lines in the metric graph, select **Apply splitting**. 
+1. To see data processed inbound or outbound as their own individual lines in the metric graph, select **Apply splitting**. 
 
-8.  In the **Values** drop-down menu, select **Direction (Out | In)**.
+1.  In the **Values** drop-down menu, select **Direction (Out | In)**.
 
 ### Packets
 
@@ -141,19 +143,19 @@ To view the connection state of your connections:
 
 1. Select the NAT gateway resource you would like to monitor. 
 
-2. In the **Metric** drop-down menu, select the **SNAT Connection Count** metric.
+1. In the **Metric** drop-down menu, select the **SNAT Connection Count** metric.
 
-3. In the **Aggregation** drop-down menu, select **Sum**. 
+1. In the **Aggregation** drop-down menu, select **Sum**. 
 
-4. Select to **Add filter**.
+1. Select to **Add filter**.
 
-5. In the **Property** drop-down menu, select **Connection State**.
+1. In the **Property** drop-down menu, select **Connection State**.
 
-6. In the **Values** drop-down menu, select **Attempted**, **Failed**, or both.
+1. In the **Values** drop-down menu, select **Attempted**, **Failed**, or both.
 
-7. To see attempted and failed connections as their own individual lines in the metric graph, select **Apply splitting**.
+1. To see attempted and failed connections as their own individual lines in the metric graph, select **Apply splitting**.
 
-8. In the **Values** drop-down menu, select **Connection State**.
+1. In the **Values** drop-down menu, select **Connection State**.
 
     :::image type="content" source="./media/nat-metrics/nat-metrics-3.png" alt-text="Screenshot of the metrics configuration.":::
 
@@ -190,7 +192,7 @@ You can use this metric to:
 
 Possible reasons for a drop in data path availability include: 
 
-- An infrastructure outage has occurred. 
+- An infrastructure outage. 
 
 - There aren't healthy VMs available in your NAT gateway configured subnet. For more information, see the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity). 
 
@@ -210,72 +212,75 @@ To set up a datapath availability alert, follow these steps:
 
 1. From the NAT gateway resource page, select **Alerts**. 
 
-2. Select **Create alert rule**. 
+1. Select **Create alert rule**. 
 
-3. From the signal list, select **Datapath Availability**. 
+1. From the signal list, select **Datapath Availability**. 
 
-4. From the **Operator** drop-down menu, select **Less than**. 
+1. From the **Operator** drop-down menu, select **Less than**. 
 
-5. From the **Aggregation type** drop-down menu, select **Average**. 
+1. From the **Aggregation type** drop-down menu, select **Average**. 
 
-6. In the **Threshold value** box, enter **90%**.
+1. In the **Threshold value** box, enter **90%**.
 
-7. From the **Unit** drop-down menu, select **Count**. 
+1. From the **Unit** drop-down menu, select **Count**. 
 
-8. From the **Aggregation granularity (Period)** drop-down menu, select **15 minutes**. 
+1. From the **Aggregation granularity (Period)** drop-down menu, select **15 minutes**. 
 
-9. Create an **Action** for your alert by providing a name, notification type, and type of action that is performed when the alert is triggered.
+1. Create an **Action** for your alert by providing a name, notification type, and type of action that is performed when the alert is triggered.
 
-10. Before deploying your action, **test the action group**.
+1. Before deploying your action, **test the action group**.
 
-11. Select **Create** to create the alert rule.
+1. Select **Create** to create the alert rule.
 
 >[!NOTE]
 >Aggregation granularity is the period of time over which the datapath availability is measured to determine if it has dropped below the threshold value. 
 Setting the aggregation granularity to less than 5 minutes may trigger false positive alerts that detect noise in the datapath.
 
 ### Alerts for SNAT port exhaustion 
 
-Set up an alert on the **SNAT connection count** metric to notify you of connection failures on your NAT gateway. A failed connection volume greater than zero can indicate that either you have reached the connection limit on your NAT gateway or that you have hit SNAT port exhaustion. Investigate further to determine the root cause of these failures.
+Set up an alert on the **SNAT connection count** metric to notify you of connection failures on your NAT gateway. A failed connection volume greater than zero can indicate that you reached the connection limit on your NAT gateway or that you hit SNAT port exhaustion. Investigate further to determine the root cause of these failures.
 
 To create the alert, use the following steps:
 
 1. From the NAT gateway resource page, select **Alerts**. 
 
-2. Select **Create alert rule**. 
+1. Select **Create alert rule**. 
 
-3. From the signal list, select **SNAT Connection Count**. 
+1. From the signal list, select **SNAT Connection Count**. 
 
-4. From the **Aggregation type** drop-down menu, select **Total**. 
+1. From the **Aggregation type** drop-down menu, select **Total**. 
 
-5. From the **Operator** drop-down menu, select **Greater than**. 
+1. From the **Operator** drop-down menu, select **Greater than**. 
 
-6. From the **Unit** drop-down menu, select **Count**. 
+1. From the **Unit** drop-down menu, select **Count**. 
 
-7. In the **Threshold value** box, enter 0.
+1. In the **Threshold value** box, enter 0.
 
-8. In the Split by dimensions section, select **Connection State** under Dimension name.
+1. In the Split by dimensions section, select **Connection State** under Dimension name.
 
-9. Under Dimension values, select **Failed** connections. 
+1. Under Dimension values, select **Failed** connections. 
 
-8. From the When to evaluate section, select **1 minute** under the **Check every** drop-down menu.
+1. From the When to evaluate section, select **1 minute** under the **Check every** drop-down menu.
 
-9. For the lookback period, select **5 minutes** from the drop-down menu options. 
+1. For the lookback period, select **5 minutes** from the drop-down menu options. 
 
-9. Create an **Action** for your alert by providing a name, notification type, and type of action that is performed when the alert is triggered.
+1. Create an **Action** for your alert by providing a name, notification type, and type of action that is performed when the alert is triggered.
 
-10. Before deploying your action, **test the action group**.
+1. Before deploying your action, **test the action group**.
 
-11. Select **Create** to create the alert rule.
+1. Select **Create** to create the alert rule.
 
 >[!NOTE]
 >SNAT port exhaustion on your NAT gateway resource is uncommon. If you see SNAT port exhaustion, check if NAT gateway's idle timeout timer is set higher than the default amount of 4 minutes. A long idle timeout timer seeting can cause SNAT ports too be in hold down for longer, which results in exhausting SNAT port inventory sooner. You can also scale your NAT gateway with additional public IPs to increase NAT gateway's overall SNAT port inventory. To troubleshoot these kinds of issues, refer to the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity#snat-exhaustion-due-to-nat-gateway-configuration). 
 
 ### Alerts for NAT gateway resource health
 
 [Azure Resource Health](/azure/service-health/overview) provides information on the health state of your NAT gateway resource. The resource health of your NAT gateway is evaluated by measuring the datapath availability of your NAT gateway endpoint. You can set up alerts to notify you when the health state of your NAT gateway resource changes. To learn more about NAT gateway resource health and setting up alerts, see: 
+
 * [Azure NAT Gateway Resource Health](/azure/nat-gateway/resource-health)
+
 * [NAT Gateway Resource Health Alerts](/azure/nat-gateway/resource-health#resource-health-alerts)
+
 * [How to create Resource Health Alerts in the Azure portal](/azure/service-health/resource-health-alert-monitor-guide)
 
 ## Network Insights
@@ -288,9 +293,9 @@ To view a topological map of your setup in Azure:
 
 1. From your NAT gateway’s resource page, select **Insights** from the **Monitoring** section.
 
-2. On the landing page for **Insights**, there's a topology map of your NAT gateway setup. This map shows the relationship between the different components of your network (subnets, virtual machines, public IP addresses). 
+1. On the landing page for **Insights**, there's a topology map of your NAT gateway setup. This map shows the relationship between the different components of your network (subnets, virtual machines, public IP addresses). 
 
-3. Hover over any component in the topology map to view configuration information.
+1. Hover over any component in the topology map to view configuration information.
 
     :::image type="content" source="./media/nat-metrics/nat-insights.png" alt-text="Screenshot of the Insights section of NAT gateway."::: 
 
@@ -308,11 +313,10 @@ The metrics dashboard can be used to better understand the performance and healt
 
 For more information on what each metric is showing you and how to analyze these metrics, see [How to use NAT gateway metrics](#how-to-use-nat-gateway-metrics).
 
-## More NAT gateway metrics guidance 
 
 ### What type of metrics are available for NAT gateway?
 
-NAT gateway has [multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics). Multi-dimensional metrics can be filtered by different dimensions in order to provide greater insight on the data provided. The [SNAT connection count](#snat-connection-count) metric can be filtered by Attempted and Failed connections in order to distinguish between the different types of connections being made by NAT gateway.  
+The NAT gateway supports [multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics). You can filter the multi-dimensional metrics by different dimensions to gain greater insight into the provided data. The [SNAT connection count](#snat-connection-count) metric allows you to filter the connections by Attempted and Failed connections, enabling you to distinguish between different types of connections made by the NAT gateway.
 
 Refer to the dimensions column in the [metrics overview](#metrics-overview) table to see which dimensions are available for each NAT gateway metric. 
 
@@ -325,7 +329,7 @@ All [platform metrics are stored](/azure/azure-monitor/essentials/data-platform-
 >
 >To retrieve NAT gateway metrics, use the metrics REST API.
 
-### How interpret metrics charts
+### How to interpret metrics charts
 
 Refer to [troubleshooting metrics charts](/azure/azure-monitor/essentials/metrics-troubleshoot) if you run into issues with creating, customizing or interpreting charts in Azure metrics explorer.