Fix broken links due to refactor

Author: ggailey777

articles/azure-functions/durable/durable-functions-perf-and-scale.md

@@ -25,7 +25,7 @@ The following diagram illustrates this concept:
 In the Consumption and Elastic Premium plans, Durable Functions supports autoscale through the [Azure Functions scale controller](../event-driven-scaling.md#runtime-scaling). The scale controller monitors how long messages and tasks wait before processing. Based on these latencies, it adds or removes workers.
 
 > [!NOTE]
-> Starting with Durable Functions 2.0, you can configure function apps to run in VNet-protected service endpoints in the Elastic Premium plan. In this configuration, the Durable Functions triggers start scale requests instead of the scale controller. For more information, see [Runtime scale monitoring](../functions-networking-options.md#elastic-premium-plan-with-virtual-network-triggers).
+> Starting with Durable Functions 2.0, you can configure function apps to run in virtual network-protected service endpoints in the Elastic Premium plan. In this configuration, the Durable Functions triggers start scale requests instead of the scale controller. For more information, see [Runtime scale monitoring](../functions-target-based-scaling.md#premium-plan-with-runtime-scale-monitoring-enabled).
 
 On the Premium plan, automatic scaling keeps the number of workers (and operating cost) roughly proportional to the application's load.
 

articles/azure-functions/functions-best-practices.md

@@ -192,7 +192,7 @@ Both Flex Consumption and Premium plans are recommended for reducing cold starts
 | Plan | Guidance |
 |:--- |: --- |
 | **Flex Consumption plan** | • [Use always ready instances to keep instances running](flex-consumption-plan.md#always-ready-instances)<br/>• [Set always ready instance counts](flex-consumption-how-to.md#set-always-ready-instance-counts) |
-| **Premium plan** | • [Implement a Warmup trigger in your function app](functions-bindings-warmup.md)<br/>• [Set the values for Always-Ready instances and Max Burst limit](functions-premium-plan.md#plan-and-sku-settings)<br/>• [Use virtual network trigger support when using non-HTTP triggers on a virtual network](functions-networking-options.md#elastic-premium-plan-with-virtual-network-triggers)|
+| **Premium plan** | • [Implement a Warmup trigger in your function app](functions-bindings-warmup.md)<br/>• [Set the values for Always-Ready instances and Max Burst limit](functions-premium-plan.md#plan-and-sku-settings)<br/>• [Use virtual network trigger support when using non-HTTP triggers on a virtual network](./functions-target-based-scaling.md#premium-plan-with-runtime-scale-monitoring-enabled)|
 | **Dedicated plans** | • [Run on at least two instances with Azure App Service Health Check enabled](../app-service/monitor-instances-health-check.md)<br/>• [Implement autoscaling](/azure/architecture/best-practices/auto-scaling)|
 | **Consumption plan** | • Review your use of Singleton patterns and the concurrency settings for bindings and triggers to avoid artificially placing limits on how your function app scales.<br/>• [Review the `functionAppScaleLimit` setting, which can limit scale-out](event-driven-scaling.md#limit-scale-out)<br/>• Check for a Daily Usage Quota (GB-Sec) limit set during development and testing. Consider removing this limit in production environments. |
 

articles/azure-functions/functions-networking-options.md

@@ -33,7 +33,7 @@ Use the following resources to quickly get started with Azure Functions networki
   * [Restrict your storage account to a virtual network](configure-networking-how-to.md#restrict-your-storage-account-to-a-virtual-network).
   * [Control Azure Functions outbound IP with an Azure virtual network NAT gateway](functions-how-to-use-nat-gateway.md).
 
-## Inbound access restrictions
+## <a name="inbound-networking-features"></a>Inbound access restrictions
 
 You can use access restrictions to define a priority-ordered list of IP addresses that are allowed or denied access to your app. The list can include IPv4 and IPv6 addresses, or specific virtual network subnets using [service endpoints](#use-service-endpoints). When there are one or more entries, an implicit "deny all" exists at the end of the list. IP restrictions work with all function-hosting options.
 
@@ -51,13 +51,13 @@ When running on [Container Apps](./functions-container-apps-hosting.md), inbound
 
 ::: zone-end
 
-## Private endpoints (inbound)
+## <a name="private-endpoints"></a>Private endpoints (inbound)
 
 [!INCLUDE [functions-private-site-access](../../includes/functions-private-site-access.md)]
 
 To call other services that have a private endpoint connection, such as storage or service bus, be sure to configure your app to make [outbound calls to private endpoints](#private-endpoints). For more details on using private endpoints with the storage account for your function app, visit [restrict your storage account to a virtual network](#restrict-your-storage-account-to-a-virtual-network).
 
-## Service endpoints (inbound)
+## <a name="service-endpoints"></a>Service endpoints (inbound)
 
 Using service endpoints, you can restrict many Azure services to selected virtual network subnets to provide a higher level of security. Regional virtual network integration enables your function app to reach Azure services that are secured with service endpoints. This configuration is supported on all [plans](functions-scale.md#networking-features) that support virtual network integration. Follow these steps to access a secured service endpoint:
 
@@ -82,7 +82,7 @@ To learn how to set up service endpoints, see [Establish Azure Functions private
 
 ::: zone pivot="flex-consumption-plan,premium-plan,dedicated-plan,container-apps"
 
-## Virtual network integration (outbound)
+## <a name="virtual-network-integration"></a>Virtual network integration (outbound)
 
 This section details the features that Functions supports to control data outbound from your app.
 
@@ -107,7 +107,7 @@ To learn how to set up virtual network integration, see [Enable virtual network
 
 ::: zone pivot="flex-consumption-plan,premium-plan,dedicated-plan,container-apps"
 
-## Regional virtual network integration (outbound)
+## <a name="regional-virtual-network-integration"></a>Regional virtual network integration (outbound)
 
 Using regional virtual network integration enables your app to access:
 

articles/azure-functions/functions-target-based-scaling.md

@@ -76,7 +76,7 @@ To learn more, see the [example configurations for the supported extensions](#su
 
 ## Premium plan with runtime scale monitoring enabled
 
-When [runtime scale monitoring](functions-networking-options.md#elastic-premium-plan-with-virtual-network-triggers) is enabled the extensions themselves handle dynamic scaling because the [scale controller](event-driven-scaling.md#runtime-scaling) doesn't have access to services secured by a virtual network. After you enable runtime scale monitoring, you'll need to upgrade your extension packages to these minimum versions to unlock the extra target-based scaling functionality: 
+When [runtime scale monitoring](functions-networking-options.md#virtual-network-triggers-non-http) is enabled, the extensions themselves handle dynamic scaling because the [scale controller](event-driven-scaling.md#runtime-scaling) doesn't have access to services secured by a virtual network. After you enable runtime scale monitoring, you'll need to upgrade your extension packages to these minimum versions to unlock the extra target-based scaling functionality: 
 
 | Extension Name | Minimum Version Needed | 
 | -------------- | ---------------------- |