Merge pull request #313709 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-26 06:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-cache-for-redis/.openpublishing.redirection.redis-cache.json

@@ -403,8 +403,8 @@
         },
         {
             "source_path_from_root": "/articles/azure-cache-for-redis/migrate/migrate-overview.md",
-            "redirect_url": "/azure/redis/migrate/migrate-overview",
-            "redirect_document_id": true
+            "redirect_url": "/azure/redis/migrate/migrate-basic-standard-premium-overview",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/azure-cache-for-redis/cache-overview-vector-similarity.md",

articles/azure-cache-for-redis/TOC.yml

@@ -31,8 +31,22 @@
 - name: Migration 
   expanded: true
   items:
-  - name: Migrate to Azure Managed Redis
-    href: /azure/redis/migrate/migrate-overview
+  - name: Migrate Basic, Standard, or Premium tiers to Azure Managed Redis
+    items:
+    - name: Overview
+      href: /azure/redis/migrate/migrate-basic-standard-premium-overview
+    - name: Understand
+      href: /azure/redis/migrate/migrate-basic-standard-premium-understand
+    - name: Self-service
+      href: /azure/redis/migrate/migrate-basic-standard-premium-self-service
+  - name: Migrate Enterprise tier to Azure Managed Redis
+    items:
+    - name: Overview
+      href: /azure/redis/migrate/migrate-redis-enterprise-overview
+    - name: Understand
+      href: /azure/redis/migrate/migrate-redis-enterprise-understand
+    - name: Self-service
+      href: /azure/redis/migrate/migrate-redis-enterprise-self-service
   - name: Migrate to Azure Redis from other caches
     href: cache-migration-guide.md
 

articles/azure-cache-for-redis/cache-whats-new.md

@@ -39,7 +39,10 @@ The following are the important dates to note for Basic, Standard, and Premium t
 | October 1, 2026 | Creating new caches in Basic, Standard or Premium tiers is blocked for existing customers. |
 | October 1, 2028 | Remaining caches in Basic, Standard or Premium tiers are turned off.                       |
 
-For more information on moving your caches to Azure Managed Redis, see [Migrate from Basic, Standard, Premium, and Enterprise tiers to Azure Managed Redis](/azure/redis/migrate/migrate-overview).
+For more information on moving your caches to Azure Managed Redis, see:
+
+- [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview)
+- [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview)
 
 For more details about the retirement of Azure Cache for Redis, see [Azure Cache for Redis Retirement: What to Know and How to Prepare](https://techcommunity.microsoft.com/blog/azure-managed-redis/azure-cache-for-redis-retirement-what-to-know-and-how-to-prepare/4458721).
 

articles/azure-cache-for-redis/includes/cache-retirement-alert.md

@@ -4,7 +4,11 @@ ms.topic: include
 ---
 
 > [!IMPORTANT]
-> Azure Cache for Redis announced its retirement timeline for all SKUs. We recommend moving your existing Azure Cache for Redis instances to [Azure Managed Redis](../../redis/migrate/migrate-overview.md) as soon as you can. 
+> Azure Cache for Redis announced its retirement timeline for all SKUs. We recommend moving your existing Azure Cache for Redis instances to Azure Managed Redis as soon as you can.
+>
+> Migration guidance:
+> - [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview)
+> - [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview)
 >
 > For more details about the retirement:
 >   - [Azure Cache for Redis Retirement: What to Know and How to Prepare](https://techcommunity.microsoft.com/blog/azure-managed-redis/azure-cache-for-redis-retirement-what-to-know-and-how-to-prepare/4458721)

articles/azure-cache-for-redis/index.yml

@@ -78,5 +78,7 @@ landingContent:
             url: /azure/redis/whats-new
           - text: Azure Managed Redis architecture
             url: /azure/redis/architecture
-          - text: Moving to Azure Managed Redis from Azure Cache for Redis
-            url: /azure/redis/migrate/migrate-overview
+          - text: Migrate Basic, Standard, and Premium tiers to Azure Managed Redis
+            url: /azure/redis/migrate/migrate-basic-standard-premium-overview
+          - text: Migrate Enterprise tier to Azure Managed Redis
+            url: /azure/redis/migrate/migrate-redis-enterprise-overview

articles/azure-cache-for-redis/retirement-faq.yml

@@ -15,7 +15,7 @@ summary: |
   - [Basic, Standard, and Premium tiers](#questions-on-basic--standard--and-premium-tiers-of-azure-cache-for-redis-retirement)
   - [Enterprise and Enterprise Flash tiers](#questions-on-the-enterprise-tier-of-azure-cache-for-redis-retirement)
 
-  For more information on moving your caches to Azure Managed Redis, see [Move from Azure Cache for Redis to Azure Managed Redis](/azure/redis/migrate/migrate-overview). 
+  For more information on moving your caches to Azure Managed Redis, see [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview).
 
 sections:
   - name: Questions on Basic, Standard, and Premium tiers of Azure Cache for Redis retirement
@@ -74,7 +74,7 @@ sections:
       - question: How do I choose the right Azure Managed Redis tier?
 
         answer: | 
-          For more information, see the [Migration overview](/azure/redis/migrate/migrate-overview) on how to choose the right Azure Managed Redis tier and SKU.
+          For more information, see [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview) to choose the right Azure Managed Redis tier and SKU.
 
       - question: How do I choose the appropriate clustering policy?
 
@@ -95,12 +95,12 @@ sections:
         answer: | 
           Given the benefits of using Azure Managed Redis, we highly recommend you migrate to Azure Managed Redis as soon as possible, without waiting for the retirement deadline.
 
-          For step-by-step instructions, see the [Move from Azure Cache for Redis to Azure Managed Redis](migrate/migrate-overview.md).
+          For step-by-step instructions, see [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview).
 
       - question: How can I retain data during migration?
 
         answer: | 
-          To retain data during migration, users should follow the guidance in [Migrate from Basic, Standard, Premium, and Enterprise tiers to Azure Managed Redis](/azure/redis/migrate/migrate-overview). This documentation provides instructions on migrating cache endpoints and preserving data throughout the process.
+          To retain data during migration, users should follow the guidance in [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview). This documentation provides instructions on migrating cache endpoints and preserving data throughout the process.
 
       - question: Can I transfer my reservations or reserved pricing from Azure Cache for Redis to Azure Managed Redis?
 
@@ -153,12 +153,12 @@ sections:
 
           Azure Managed Redis is compatible with all Redis client libraries, redis-cli, and Redis Insights. Most client libraries work without other configuration, but applications should verify compatibility with clustered Redis instances because Azure Managed Redis is clustered by default.
 
-          For detailed guidance on client library configuration and migration steps, see the [migration overview](/azure/redis/migrate/migrate-overview).
+          For detailed guidance on client library configuration and migration steps, see [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview).
 
       - question: How do I choose the right Azure Managed Redis tier?
 
         answer: |   
-          For more information, see the [migration overview](/azure/redis/migrate/migrate-overview) on how to choose the right Azure Managed Redis tier and SKU.
+          For more information, see [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview) to choose the right Azure Managed Redis tier and SKU.
 
       - question: Does Azure Managed Redis support every feature that I currently use?
 
@@ -174,12 +174,12 @@ sections:
         answer: |           
           Given the benefits of using Azure Managed Redis, we highly recommend you migrate to Azure Managed Redis as soon as possible, without waiting for the retirement deadline.
 
-          For step-by-step instructions, see the [Move from Azure Cache for Redis to Azure Managed Redis](migrate/migrate-overview.md).
+          For step-by-step instructions, see [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview).
 
       - question: How can data be retained during migration?
 
         answer: |
-          To retain data during migration, users should follow the guidance in [Migrate from Basic, Standard, Premium, and Enterprise tiers to Azure Managed Redis](/azure/redis/migrate/migrate-overview). This documentation provides instructions on migrating cache endpoints and preserving data throughout the process.
+          To retain data during migration, users should follow the guidance in [Migrate Basic, Standard, and Premium tiers to Azure Managed Redis](/azure/redis/migrate/migrate-basic-standard-premium-overview) and [Migrate Enterprise tier to Azure Managed Redis](/azure/redis/migrate/migrate-redis-enterprise-overview). This documentation provides instructions on migrating cache endpoints and preserving data throughout the process.
       
       - question: Can I transfer my reservations or reserved pricing from Azure Cache for Redis to Azure Managed Redis?
 

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