Merge branch 'main' into release-esan-backup

Author: v-alje

articles/api-management/set-header-policy.md

@@ -67,10 +67,11 @@ User-Agent: value2
 User-Agent: value3
 ```
 
-The following limitations apply:
+#### Limitations
 
-- Removal of `Server` header isn't supported.
-- Headers: `Connection`, `ContentLength`, `KeepAlive`, `TransferEncoding` cannot be modified or deleted. 
+- The following headers can't be appended, overridden, or deleted: `Connection`, `Content-Length`, `Keep-Alive`, `Transfer-Encoding`
+- The client IP address value in the `X-Forwarded-For` header can't be deleted
+- The `Server` header can't be deleted in responses
 
 ## Examples
 

articles/application-gateway/http-response-codes.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: troubleshooting
-ms.date: 03/28/2025
+ms.date: 05/26/2025
 ms.author: mbender
 ---
 
@@ -97,10 +97,7 @@ Other reasons for clients receiving 403 responses include:
 
 #### 404 – Page not found
 
-An HTTP 404 response can be returned if a request is sent to an application gateway that is:
-- Using a [v2 sku](overview-v2.md).
-- Without a hostname match defined in any [multi-site listeners](multiple-site-overview.md).
-- Not configured with a [basic listener](application-gateway-components.md#types-of-listeners).
+An HTTP 404 response is generated when a request is made to Application Gateway (V2 SKUs) with a hostname that doesn’t corresponds to any of the configured Multi-site listeners, and there is no Basic listener present. Learn more about [types of listeners](application-gateway-components.md#types-of-listeners).
 
 #### 408 – Request Time-out
 

articles/automation/shared-resources/modules.md

@@ -3,7 +3,7 @@ title: Manage modules in Azure Automation
 description: This article tells how to use PowerShell modules to enable cmdlets in runbooks and DSC resources in DSC configurations.
 services: automation
 ms.subservice: shared-capabilities
-ms.date: 10/01/2024
+ms.date: 05/27/2025
 ms.topic: how-to 
 ms.custom: devx-track-azurepowershell, devx-track-python
 ms.service: azure-automation

articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md

@@ -21,7 +21,7 @@ In this tutorial, you learn how to:
 
 > [!div class="checklist"]
 > * Set up dynamic configuration refresh for your Azure Functions app.
-> * Enable automatic configuration refresh using App Configuraion middleware.
+> * Enable automatic configuration refresh using App Configuration middleware.
 > * Use the latest configuration in Function calls when changes occur in your App Configuration store.
 
 ## Prerequisites

articles/azure-cache-for-redis/cache-how-to-scale.md

@@ -137,7 +137,7 @@ az redis update --cluster-name myCache --resource-group myGroup --set "sku.name"
 For more information on scaling with Azure CLI, see [Change settings of an existing Azure Cache for Redis](cache-manage-cli.md#scale).
 
 > [!NOTE]
-> When you scale a cache up or down programatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
+> When you scale a cache up or down programmatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
 >
 
 ### [Scale out and in - Premium only](#tab/scale-out-and-in---premium-only)

articles/azure-cache-for-redis/cache-migration-guide.md

@@ -1,122 +1,94 @@
 ---
 title: Migrate to Azure Cache for Redis
-description: Learn how to migrate your existing cache to Azure Cache for Redis
+description: Learn how to migrate an existing cache to Azure Cache for Redis or migrate between Azure Cache for Redis instances.
 ms.topic: conceptual
 ms.custom:
   - ignite-2024
 ms.collection: 
  - migration
  - aws-to-azure
-ms.date: 11/17/2021
+ms.date: 05/22/2025
 appliesto:
   - ✅ Azure Cache for Redis
 
 ---
-# Migrate to Azure Cache for Redis
+# Migrate to or between Azure Cache for Redis instances
 
-This article describes a number of approaches to migrate an existing Redis cache running on-premises or in another cloud service to Azure Cache for Redis.
+This article describes several Azure Cache for Redis migration scenarios. You can migrate open-source Redis caches running on-premises or in cloud virtual machines (VMs), or hosted caches from other cloud platforms, to Azure Cache for Redis.
 
-## Migration scenarios
+You can also migrate one Azure Cache for Redis instance to another instance. If you only need to move an Azure Redis cache from one Azure region to another, see [Move Azure Cache for Redis instances to different regions](cache-moving-resources.md).
 
-Open-source Redis can run in many compute environments. Common examples include:
-
-- **On-premises** - Redis caches running in private data centers.
-- **Cloud-based VMs** - Redis caches running on Azure VMs, AWS EC2, and so on.
-- **Hosting services** - Managed Redis services such as AWS ElastiCache.
-
-If you have such a cache, you may be able to move it to Azure Cache for Redis with minimal interruption or downtime. 
-
-If you're looking to move from one Azure region to another, we recommend you see our [Move Azure Cache for Redis instances to different regions](cache-moving-resources.md) article.
+Open-source Redis can run in many compute environments, such as private on-premises data centers or cloud-hosted VMs. Other hosting platforms like Amazon Web Services (AWS) host Redis cache services like AWS ElastiCache. You can usually migrate these Redis caches to Azure Cache for Redis with minimal interruption or downtime.
 
 ## Migration options
 
-There are different ways that you can switch from one cache to another. Depending on where your cache is and how your application interacts with it, one method will be more useful than the others. Some of the frequently used migration strategies are detailed below.
+How you migrate from one cache to another depends on where your cache exists and how your application interacts with it. The following table lists frequently used migration strategies.
 
    | Option       | Advantages | Disadvantages |
    | ------------ | ---------- | ------------- |
-   | Create a new cache | Simplest to implement. | Need to repopulate data to the new cache, which may not work with many applications. |
-   | Export and import data via RDB file | Compatible with any Redis cache generally. | Some data could be lost, if they're written to the existing cache after the RDB file is generated. | 
-   | Dual-write data to two caches | No data loss or downtime. Uninterrupted operations of the existing cache. Easier testing of the new cache. | Needs two caches for an extended period of time. | 
-   | Migrate data programmatically | Full control over how data are moved. | Requires custom code. | 
+   | Create a new cache | Simplest to implement. | Must repopulate data to the new cache, which might not work with some applications. |
+   | Export and import data via read-only database (RDB) file. | Compatible with any Redis cache. | Data written to the existing cache after the RDB file is generated could be lost. | 
+   | Dual-write data to two caches. | No data loss or downtime, no interrupted cache operations, and easier testing. | Needs two caches for an extended time period. | 
+   | Migrate data programmatically. | Full control over how data is moved. | Requires custom code. | 
 
-### Create a new Azure Cache for Redis
+### Create a new cache
 
-This approach technically isn't a migration. If losing data isn't a concern, the easiest way to move to Azure Cache for Redis is to create cache instance and connect your application to it. For example, if you use Redis as a look-aside cache of database records, you can easily rebuild the cache from scratch.
+If uninterrupted operations and potential data loss aren't concerns, the easiest way to move data to Azure Cache for Redis is to create an Azure Redis cache instance and connect your application to it. For example, if you use Redis as a look-aside cache of database records, you can easily rebuild the cache from scratch. This approach isn't technically a migration.
 
 General steps to implement this option are:
 
-1. Create a new Azure Cache for Redis instance.
-
-1. Optionally, try out the new [Azure Managed Redis (preview)](../redis/overview.md).
-
-2. Update your application to use the new instance.
-
+1. Create a new Azure Cache for Redis instance. Optionally, try out [Azure Managed Redis](../redis/overview.md).
+1. Update your application to use the new Azure Redis instance.
 3. Delete the old Redis instance.
 
 ### Export data to an RDB file and import it into Azure Cache for Redis
 
-Open-source Redis defines a standard mechanism for taking a snapshot of a cache's in-memory dataset and saving it to a file. This file, called RDB, can be read by another Redis cache. [Azure Cache for Redis premium tier](cache-overview.md#service-tiers) supports importing data into a cache instance via RDB files. You can use an RDB file to transfer data from an existing cache to Azure Cache for Redis.
+Open-source Redis defines a standard mechanism to take a snapshot of a cache's in-memory dataset and save it to an RDB file that any Redis cache can read. Azure Cache for Redis [Premium tier](cache-overview.md#service-tiers) supports importing data into a cache instance via RDB file. You can use the RDB file to transfer data from an existing cache to Azure Cache for Redis.
 
 > [!IMPORTANT]
-> RDB file format can change between Redis versions and may not maintain backward-compatibility. The Redis version of the cache you're exporting from should be equal or less than the version provided by Azure Cache for Redis.
->
+> RDB file format can change between Redis versions and might not maintain backward compatibility. The Redis version of the cache you export should be equal to or lower than the version that Azure Cache for Redis provides.
 
 General steps to implement this option are:
 
-1. Create a new Azure Cache for Redis instance in the premium tier that is the same size as (or bigger than) the existing cache.
-
-2. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
-
-    > [!NOTE]
-    > If you’re migrating data within Azure Cache for Redis, see [these instructions on how to export an RDB file](cache-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/az.rediscache/export-azrediscache) instead.
-    >
+1. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or save one manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named *dump.rdb* by default and is located at the path specified in the *redis.conf* configuration file.
+1. Create a new Premium-tier Azure Cache for Redis instance that's at least as large as the existing cache.
+1. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use `AzCopy` for this task.
+1. [Import](cache-how-to-import-export-data.md#import) the RDB file into the new cache. You can also use the PowerShell [Import-AzRedisCache](/powershell/module/az.rediscache/import-azrediscache) cmdlet.
+1. Update your application to use the new cache instance.
 
-3. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use AzCopy for this task.
-
-4. Import the RDB file into the new cache using these [import instructions](cache-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/az.rediscache/import-azrediscache).
+> [!NOTE]
+> To migrate data from another Azure Redis instance, first [export](cache-how-to-import-export-data.md#export) the RDB file from that instance, or use the PowerShell [Export-AzRedisCache](/powershell/module/az.rediscache/export-azrediscache) cmdlet.
 
-5. Update your application to use the new cache instance.
+### Write to two Redis caches during migration
 
-### Write to two Redis caches simultaneously during migration period
+Rather than moving data between caches, you can temporarily set your application to write data to both an existing cache and a new one. The application reads data from the existing cache initially. When the new cache has enough data, you can switch the application to that cache and retire the old one.
 
-Rather than moving data directly between caches, you may use your application to write data to both an existing cache and a new one you're setting up. The application will still read data from the existing cache initially. When the new cache has the necessary data, you switch the application to that cache and retire the old one. Let's say, for example, you use Redis as a session store and the application sessions are valid for seven days. After writing to the two caches for a week, you'll be certain the new cache contains all non-expired session information. You can safely rely on it from that point onward without concern over data loss.
+For example, suppose you use Redis as a session store and the application sessions expire after seven days. After writing to both caches for seven days, you know the new cache contains all nonexpired session information and you can safely rely on it from that point on. You can then retire the old cache.
 
 General steps to implement this option are:
 
-1. Create a new Azure Cache for Redis instance in the premium tier that is the same size as (or bigger than) the existing cache.
-
-2. Modify application code to write to both the new and the original instances.
-
-3. Continue reading data from the original instance until the new instance is sufficiently populated with data.
-
-4. Update the application code to reading and writing from the new instance only.
-
-5. Delete the original instance.
+1. Create a new Premium-tier Azure Cache for Redis instance that's at least as large as the existing cache.
+1. Modify your application code to write to both the new and the original instances.
+1. Continue using data from the original instance until the new instance is sufficiently populated with data.
+1. Update the application code to reading and writing from the new instance only.
+1. Delete the original instance.
 
 ### Migrate programmatically
 
-You can create a custom migration process by programmatically reading data from an existing cache and writing them into Azure Cache for Redis. This [open-source tool](https://github.com/deepakverma/redis-copy) can be used to copy data from one Azure Cache for Redis instance to another. A [compiled version](https://github.com/deepakverma/redis-copy/releases/download/alpha/Release.zip) is available as well. You may also find the source code to be a useful guide for writing your own migration tool.
+You can create a custom migration by programmatically reading data from an existing cache and writing it into Azure Cache for Redis. For example, you can use the open-source [redis-copy](https://github.com/deepakverma/redis-copy) tool to copy data from one Azure Redis instance to another.
+
+The source code can be a useful guide for writing your own migration tool. A [compiled version](https://github.com/deepakverma/redis-copy/releases/download/alpha/Release.zip) is also available.
 
 > [!NOTE]
 > This tool isn't officially supported by Microsoft. 
->
 
 General steps to implement this option are:
 
-1. Create a VM in the region where the existing cache is located. If your dataset is large, choose a relatively powerful VM to reduce copying time.
-
-2. Create a new Azure Cache for Redis instance.
-
-3. Flush data from the new cache to ensure that it's empty. This step is required because the copy tool itself doesn't overwrite any existing key in the target cache.
-
-    > [!IMPORTANT]
-    > Make sure to NOT flush from the source cache.
-    >
-
-4. Use an application such as the open-source tool above to automate the copying of data from the source cache to the target. Remember that the copy process could take a while to complete depending on the size of your dataset.
+1. Create an Azure virtual machine (VM) in the same region as the existing cache. If your dataset is large, choose a powerful VM to reduce copying time.
+1. Create a new Azure Cache for Redis instance and make sure that it's empty. The `redis-copy` tool doesn't overwrite any existing keys in the target cache.
+4. Use an application such as `redis-copy` to automate copying the data from the source cache to the target cache. The copy process could take a while depending on the size of your dataset.
 
-## Next steps
-Learn more about Azure Cache for Redis features.
+## Related content
 
-* [Azure Cache for Redis service tiers](cache-overview.md#service-tiers)
-* [Import data](cache-how-to-import-export-data.md#import)
+- [Azure Cache for Redis service tiers](cache-overview.md#service-tiers)
+- [Import and export data](cache-how-to-import-export-data.md#import)