Merge pull request #313031 from johndowns/functions-reliability-links

Update links to Azure Functions reliability guide

Author: prmerger-automator[bot]

articles/azure-functions/flex-consumption-plan.md

@@ -97,7 +97,7 @@ Flex Consumption includes an _always ready_ feature that you can use to choose i
 
 For example, if you set always ready to 2 for your HTTP group of functions, the platform keeps two instances always running for those functions. Those instances process your function executions first. Depending on concurrency settings, the platform scales beyond those two instances by using on-demand instances.
 
-You can configure no fewer than two always-ready instances per function or function group while [zone redundancy is enabled](/azure/reliability/reliability-functions?pivots=flex-consumption-plan#availability-zone-support). 
+You can configure no fewer than two always-ready instances per function or function group while [zone redundancy is enabled](/azure/reliability/reliability-functions?pivots=flex-consumption-plan#resilience-to-availability-zone-failures). 
 
 To learn how to configure always ready instances, see [Set always ready instance counts](flex-consumption-how-to.md#set-always-ready-instance-counts).
 

articles/azure-functions/migration/migrate-plan-consumption-to-flex.md

@@ -472,7 +472,7 @@ Here are some strategies to protect both upstream and downstream data during the
 + **Idempotency**: Ensure your functions can safely process the same message multiple times without negative side effects. For more information, see [Designing Azure Functions for identical input](../functions-idempotent.md).
 + **Logging and monitoring**: Enable detailed logging in both apps during migration to track message processing. For more information, see [Monitor executions in Azure Functions](../functions-monitoring.md).
 + **Checkpointing**: For streaming triggers, such as the Event Hubs trigger, implement correct checkpoint behaviors to track processing position. For more information, see [Azure Functions reliable event processing](../functions-reliable-event-processing.md).
-+ **Parallel processing**: Consider temporarily running both apps in parallel during the cutover. Make sure to carefully monitor and validate how data is processed from the upstream service. For more information, see [Active-active pattern for non-HTTPS trigger functions](/azure/reliability/reliability-functions#active-active-pattern-for-non-https-trigger-functions).
++ **Parallel processing**: Consider temporarily running both apps in parallel during the cutover. Make sure to carefully monitor and validate how data is processed from the upstream service. For more information, see [Custom multi-region solutions for resiliency](/azure/reliability/reliability-functions#custom-multi-region-solutions-for-resiliency).
 + **Gradual cutover**: For high-volume systems, consider implementing a gradual cutover by redirecting portions of traffic to the new app. You can manage the routing of requests upstream from your apps by using services such as [Azure API Management](../functions-openapi-definition.md) or [Azure Application Gateway](../../app-service/overview-app-gateway-integration.md).
 
 ### Mitigations by trigger type

articles/azure-functions/storage-considerations.md

@@ -47,7 +47,7 @@ Storage accounts that you create during the function app creation process in the
 
 - When you create your function app in the Azure portal, you can only choose an existing storage account in the same region as the function app that you create. This requirement is a performance optimization and not a strict limitation. To learn more, see [Storage account location](#storage-account-location).
 
-- When you create your function app on a plan with [availability zone support](/azure/reliability/reliability-functions#availability-zone-support) enabled, only [zone-redundant storage accounts](../storage/common/storage-redundancy.md#zone-redundant-storage) are supported.
+- When you create your function app on a plan with [availability zone support](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures) enabled, only [zone-redundant storage accounts](../storage/common/storage-redundancy.md#zone-redundant-storage) are supported.
 
 When you use deployment automation to create your function app with a network-secured storage account, you must include specific networking configurations in your ARM template or Bicep file. If you don't include these settings and resources, your automated deployment might fail in validation. For ARM template and Bicep guidance, see [Secured deployments](functions-infrastructure-as-code.md#secured-deployments). For an overview on configuring storage accounts with networking, see [How to use a secured storage account with Azure Functions](configure-networking-how-to.md).
 

articles/azure-resource-manager/management/relocation/relocation-functions.md

@@ -59,7 +59,7 @@ If your application persists data to the app's shared storage path, make sure to
 
 ### Connected services
 
-Your functions might connect to Azure Services and other resources using either a service SDK or triggers and bindings. Any connected service might be negatively impacted when the app moves to a new region. If latency or throughout are issues, consider moving any connected service to the new region as well. To learn how to move those resources across regions, see the documentation for the respective services. When moving an app with connected services, you might want to consider a [cross-region disaster recovery and business continuity](/azure/reliability/reliability-functions#cross-region-disaster-recovery-and-business-continuity) strategy during the move.
+Your functions might connect to Azure Services and other resources using either a service SDK or triggers and bindings. Any connected service might be negatively impacted when the app moves to a new region. If latency or throughout are issues, consider moving any connected service to the new region as well. To learn how to move those resources across regions, see the documentation for the respective services. When moving an app with connected services, you might want to consider a [multi-region resiliency](/azure/reliability/reliability-functions#custom-multi-region-solutions-for-resiliency) strategy during the move.
 
 Changes to connected services might require you to update the values stored in your application settings, which are used to connect to those services.
 
@@ -83,7 +83,7 @@ Functions uses access keys to make it more difficult to access HTTP endpoints in
 
 ### Downtime
 
-If minimal downtime is a requirement, consider running your function app in both regions as recommended to implement a disaster recovery architecture. The specific architecture you implement depends on the trigger types in your function app. For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#cross-region-disaster-recovery-and-business-continuity).
+If minimal downtime is a requirement, consider running your function app in both regions as recommended to implement a disaster recovery architecture. The specific architecture you implement depends on the trigger types in your function app. For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#custom-multi-region-solutions-for-resiliency).
 
 ### Durable Functions
 

articles/logic-apps/quickstart-create-example-consumption-workflow.md

@@ -96,7 +96,7 @@ To create a Standard logic app workflow that runs in single-tenant Azure Logic A
    >
    > Availability zones are automatically enabled for new and existing Consumption logic app workflows in 
    > [Azure regions that support availability zones](/azure/reliability/availability-zones-region-support). 
-   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#availability-zone-support) and 
+   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures) and 
    > [Protect logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md).
 
    When you're done, your settings look similar to the following example:

articles/logic-apps/tutorial-build-schedule-recurring-logic-app-workflow.md

@@ -85,7 +85,7 @@ You can create a similar workflow with a Standard logic app resource. However, t
    >
    > Availability zones are automatically enabled for new and existing Consumption logic app workflows in 
    > [Azure regions that support availability zones](/azure/reliability/availability-zones-region-support). 
-   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#availability-zone-support) and 
+   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures) and 
    > [Protect logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md).
 
    After you finish, your settings look similar to the following example:

articles/logic-apps/tutorial-process-email-attachments-workflow.md

@@ -273,7 +273,7 @@ After you confirm that your function works, create your logic app resource and w
    >
    > Availability zones are automatically enabled for new and existing Consumption logic app workflows in 
    > [Azure regions that support availability zones](/azure/reliability/availability-zones-region-support). 
-   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#availability-zone-support) and 
+   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures) and 
    > [Protect logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md).
 
 1. When you're ready, select **Review + create**. After Azure validates the information about your logic app resource, select **Create**.

articles/logic-apps/tutorial-process-mailing-list-subscriptions-workflow.md

@@ -86,7 +86,7 @@ You can create a similar workflow with a Standard logic app resource where some
    >
    > Availability zones are automatically enabled for new and existing Consumption logic app workflows in 
    > [Azure regions that support availability zones](/azure/reliability/availability-zones-region-support). 
-   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#availability-zone-support) and 
+   > For more information, see [Reliability in Azure Functions](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures) and 
    > [Protect logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md).
 
    After you finish, your settings look similar to the following example: