Link check and Acrolinx.

Author: TimShererWithAquent

articles/azure-functions/ip-addresses.md

@@ -3,7 +3,7 @@ title: IP addresses in Azure Functions
 description: Learn how to find inbound and outbound IP addresses for function apps, and what causes them to change.
 
 ms.topic: conceptual
-ms.date: 06/08/2023
+ms.date: 05/05/2025
 ---
 
 # IP addresses in Azure Functions
@@ -19,7 +19,7 @@ IP addresses are associated with function apps, not with individual functions. I
 
 ## Function app inbound IP address
 
-Each function app starts out by using a single inbound IP address. When running in a Consumption or Premium plan, additional inbound IP addresses may be added as event-driven scale-out occurs. To find the inbound IP address or addresses being used by your app, use the `nslookup` utility from your local computer, as in the following example:
+Each function app starts out by using a single inbound IP address. When a function app runs in a Consumption or Premium plan, more inbound IP addresses might be added as event-driven scale-out occurs. To find the inbound IP address or addresses being used by your app, use the `nslookup` utility from your local computer, as in the following example:
 
 ```command
 nslookup <APP_NAME>.azurewebsites.net
@@ -29,19 +29,19 @@ In this example, replace `<APP_NAME>` with your function app name. If your app u
 
 ## <a name="find-outbound-ip-addresses"></a>Function app outbound IP addresses
 
-Each function app has a set of available outbound IP addresses. Any outbound connection from a function, such as to a back-end database, uses one of the available outbound IP addresses as the origin IP address. You can't know beforehand which IP address a given connection will use. For this reason, your back-end service must open its firewall to all of the function app's outbound IP addresses.
+Each function app has a set of available outbound IP addresses. Any outbound connection from a function, such as to a back-end database, uses one of the available outbound IP addresses as the origin IP address. You can't know beforehand which IP address a given connection uses. For this reason, your back-end service must open its firewall to all of the function app's outbound IP addresses.
 
 > [!TIP]
-> For some platform-level features such as [Key Vault references](../app-service/app-service-key-vault-references.md), the origin IP might not be one of the outbound IPs, and you should not configure the target resource to rely on these specific addresses. It is recommended that the app instead use a virtual network integration, as the platform will route traffic to the target resource through that network.
+> For some platform-level features such as [Key Vault references](../app-service/app-service-key-vault-references.md), the origin IP might not be one of the outbound IPs, and you shouldn't configure the target resource to rely on these specific addresses. We recommend that the app instead uses a virtual network integration, because the platform routes traffic to the target resource through that network.
 
 To find the outbound IP addresses available to a function app:
 
 # [Azure portal](#tab/portal)
 
 1. Sign in to the [Azure Resource Explorer](https://resources.azure.com).
-2. Select **subscriptions > {your subscription} > providers > Microsoft.Web > sites**.
-3. In the JSON panel, find the site with an `id` property that ends in the name of your function app.
-4. See `outboundIpAddresses` and `possibleOutboundIpAddresses`. 
+1. Select **subscriptions > {your subscription} > providers > Microsoft.Web > sites**.
+1. In the JSON panel, find the site with an `id` property that ends in the name of your function app.
+1. See `outboundIpAddresses` and `possibleOutboundIpAddresses`.
 
 # [Azure CLI](#tab/azurecli)
 
@@ -60,10 +60,10 @@ $functionApp.PossibleOutboundIPAddress
 
 ---
 
-The set of `outboundIpAddresses` is currently available to the function app. The set of `possibleOutboundIpAddresses` includes IP addresses that will be available only if the function app [scales to other pricing tiers](#outbound-ip-address-changes).
+The set of `outboundIpAddresses` is currently available to the function app. The set of `possibleOutboundIpAddresses` includes IP addresses that are available only if the function app [scales to other pricing tiers](#outbound-ip-address-changes).
 
 > [!NOTE]
-> When a function app that runs on the [Consumption plan](consumption-plan.md) or the [Premium plan](functions-premium-plan.md) is scaled, a new range of outbound IP addresses may be assigned. When running on either of these plans, you can't rely on the reported outbound IP addresses to create a definitive allowlist. To be able to include all potential outbound addresses used during dynamic scaling, you'll need to add the entire data center to your allowlist.
+> When a function app that runs on the [Consumption plan](consumption-plan.md) or the [Premium plan](functions-premium-plan.md) is scaled, a new range of outbound IP addresses might be assigned. When running on either of these plans, you can't rely on the reported outbound IP addresses to create a definitive allowlist. To be able to include all potential outbound addresses used during dynamic scaling, you need to add the entire data center to your allowlist.
 
 ## Data center outbound IP addresses
 
@@ -101,21 +101,21 @@ The inbound IP address **might** change when you:
 - Delete the last function app in a resource group and region combination, and re-create it.
 - Delete a TLS binding, such as during [certificate renewal](../app-service/configure-ssl-certificate.md#renew-an-expiring-certificate).
 
-When your function app runs in a [Consumption plan](consumption-plan.md) or in a [Premium plan](functions-premium-plan.md), the inbound IP address might also change even when you haven't taken any actions such as the ones [listed above](#inbound-ip-address-changes).
+When your function app runs in a [Consumption plan](consumption-plan.md) or in a [Premium plan](functions-premium-plan.md), the inbound IP address might also change even when you haven't taken any actions such as the ones here.
 
 ## Outbound IP address changes
 
 The relative stability of the outbound IP address depends on the hosting plan.  
 
 ### Consumption and Premium plans
 
-Because of autoscaling behaviors, the outbound IP can change at any time when running on a [Consumption plan](consumption-plan.md) or in a [Premium plan](functions-premium-plan.md). 
+Because of autoscaling behaviors, the outbound IP can change at any time when running on a [Consumption plan](consumption-plan.md) or in a [Premium plan](functions-premium-plan.md).
 
-If you need to control the outbound IP address of your function app, such as when you need to add it to an allow list, consider implementing a [virtual network NAT gateway](#virtual-network-nat-gateway-for-outbound-static-ip) while running in a Premium hosting plan. You can also do this by running in a Dedicated (App Service) plan.
+If you need to control the outbound IP address of your function app, such as when you need to add it to an allowlist, consider implementing a [virtual network NAT gateway](#virtual-network-nat-gateway-for-outbound-static-ip) while running in a Premium hosting plan. You can also do this by running in a Dedicated (App Service) plan.
 
 ### Dedicated plans
 
-When running on Dedicated (App Service) plans, the set of available outbound IP addresses for a function app might change when you:
+When a function app runs on Dedicated (App Service) plans, the set of available outbound IP addresses for a function app might change when you:
 
 * Take any action that can change the inbound IP address.
 * Change your Dedicated (App Service) plan pricing tier. The list of all possible outbound IP addresses your app can use, for all pricing tiers, is in the `possibleOutboundIPAddresses` property. See [Find outbound IPs](#find-outbound-ip-addresses).
@@ -126,34 +126,34 @@ Use the following procedure to deliberately force an outbound IP address change
 
 1. Scale your App Service plan up or down between Standard and Premium v2 pricing tiers.
 
-2. Wait 10 minutes.
+1. Wait 10 minutes.
 
-3. Scale back to where you started.
+1. Scale back to where you started.
 
 ## IP address restrictions
 
-You can configure a list of IP addresses that you want to allow or deny access to a function app. For more information, see [Azure App Service Static IP Restrictions](../app-service/app-service-ip-restrictions.md).
+You can configure a list of IP addresses that you want to allow or deny access to a function app. For more information, see [Azure App Service access restrictions](../app-service/app-service-ip-restrictions.md).
 
 ## Dedicated IP addresses
 
 There are several strategies to explore when your function app requires static, dedicated IP addresses. 
 
 ### Virtual network NAT gateway for outbound static IP
 
-You can control the IP address of outbound traffic from your functions by using a virtual network NAT gateway to direct traffic through a static public IP address. You can use this topology when running in a [Premium plan](functions-premium-plan.md) or in a [Dedicated (App Service) plan](dedicated-plan.md). To learn more, see [Tutorial: Control Azure Functions outbound IP with an Azure virtual network NAT gateway](functions-how-to-use-nat-gateway.md).
+You can control the IP address of outbound traffic from your functions by using a virtual network NAT gateway to direct traffic through a static public IP address. You can use this topology when running in a [Premium plan](functions-premium-plan.md) or in a [Dedicated hosting plan](dedicated-plan.md). To learn more, see [Tutorial: Control Azure Functions outbound IP with an Azure virtual network NAT gateway](functions-how-to-use-nat-gateway.md).
 
 ### App Service Environments
 
-For full control over the IP addresses, both inbound and outbound, we recommend [App Service Environments](../app-service/environment/intro.md) (the [Isolated tier](https://azure.microsoft.com/pricing/details/app-service/) of App Service plans). For more information, see [App Service Environment IP addresses](../app-service/environment/network-info.md#ip-addresses) and [How to control inbound traffic to an App Service Environment](../app-service/environment/app-service-app-service-environment-control-inbound-traffic.md).
+For full control over the IP addresses, both inbound and outbound, we recommend [App Service Environments](../app-service/environment/intro.md) (the [Isolated tier](https://azure.microsoft.com/pricing/details/app-service/) of App Service plans). For more information, see [App Service Environment overview](../app-service/environment/overview).
 
 To find out if your function app runs in an App Service Environment:
 
 # [Azure portal](#tab/portal)
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Navigate to the function app.
-3. Select the **Overview** tab.
-4. The App Service plan tier appears under **App Service plan/pricing tier**. The App Service Environment pricing tier is **Isolated**.
+1. Navigate to the function app.
+1. Select the **Overview** tab.
+1. The App Service plan tier appears under **App Service plan/pricing tier**. The App Service Environment pricing tier is **Isolated**.
 
 # [Azure CLI](#tab/azurecli)