Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fwfaq

Author: duongau

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/cdn/cdn-http-variables.md",
+      "redirect_url": "/previous-versions/azure/cdn/cdn-http-variables",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cdn/cdn-advanced-http-reports.md",
       "redirect_url": "/previous-versions/azure/cdn/cdn-advanced-http-reports",

articles/app-service/app-service-hybrid-connections.md

@@ -4,7 +4,7 @@ description: Learn how to create and use hybrid connections in Azure App Service
 author: madsd
 ms.assetid: 66774bde-13f5-45d0-9a70-4e9536a4f619
 ms.topic: article
-ms.date: 01/31/2025
+ms.date: 04/10/2025
 ms.author: madsd
 ms.custom: "UpdateFrequency3, fasttrack-edit"
 #customer intent: As an app developer, I want to understand the usage of Hybrid Connections to provide access to apps in Azure App Service.
@@ -115,15 +115,18 @@ In addition to there being an App Service plan SKU requirement, there's an extra
 
 ## Hybrid Connection Manager
 
-The Hybrid Connections feature requires a relay agent in the network that hosts your Hybrid Connection endpoint. That relay agent is called the Hybrid Connection Manager (HCM). To download HCM:
+> [!NOTE]
+> The new version of the Hybrid Connection Manager is in public preview and supports both Windows and Linux. To download and learn more about the new version, see [Announcing the Public Preview of the New Hybrid Connection Manager](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-the-public-preview-of-the-new-hybrid-connection-manager-hcm/4401657).
+>
 
-1. In the [Azure portal], select your app. Select **Settings** > **Networking**.
-1. Next to **Hybrid connections**, select the link to open the **Hybrid connections page**.
-1. Select **Download connection manager**.
+The Hybrid Connections feature requires a relay agent in the network that hosts your Hybrid Connection endpoint. That relay agent is called the Hybrid Connection Manager (HCM). To download the HCM:
+
+> [!div class="nextstepaction"]
+> [Download the Hybrid Connection Manager](https://download.microsoft.com/download/0/e/4/0e48d57b-c563-4877-8acb-cb740c7c6a78/HybridConnectionManager-0.7.9.msi)
 
 This tool runs on Windows Server 2012 and later. The HCM runs as a service and connects outbound to Azure Relay on port 443.
 
-After you install HCM, you can run *HybridConnectionManagerUi.exe* to use the UI for the tool. This file is in the Hybrid Connection Manager installation directory. In Windows 10, you can also search for *Hybrid Connection Manager UI* in your search box.
+After you install HCM, you can run *HybridConnectionManagerUi.exe* to use the UI for the tool. This file is in the Hybrid Connection Manager installation directory. In Windows 10 and later, you can also search for *Hybrid Connection Manager UI* in your search box.
 
 :::image type="content" source="media/app-service-hybrid-connections/hybrid-connections-hcm.png" alt-text="Screenshot of Hybrid Connection Manager.":::
 

articles/automation/delete-run-as-account.md

@@ -3,7 +3,7 @@ title: Delete an Azure Automation Run As account
 description: This article tells how to delete a Run As account with PowerShell or from the Azure portal.
 services: automation
 ms.subservice: process-automation
-ms.date: 04/08/2025
+ms.date: 04/11/2025
 ms.topic: how-to
 ms.service: azure-automation
 ---
@@ -13,7 +13,7 @@ ms.service: azure-automation
 > [!IMPORTANT]
 > Azure Automation Run as accounts, including  Classic Run as accounts have retired on **30 September 2023** and replaced with [Managed Identities](automation-security-overview.md#managed-identities). You would no longer be able to create or renew Run as accounts through the Azure portal. For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity.md?tabs=run-as-account#sample-scripts).
 
-Run As accounts in Azure Automation provide authentication for managing resources on the Azure Resource Manager or Azure Classic deployment model using Automation runbooks and other Automation features. This article describes how to delete a Run As or Classic Run As account. When you perform this action, the Automation account is retained. After you delete the Run As account, you can re-create it in the Azure portal or with the provided PowerShell script.
+Run As accounts in Azure Automation provide authentication for managing resources on the Azure Resource Manager or Azure Classic deployment model using Automation runbooks and other Automation features. This article describes how to delete a Run As or Classic Run As account. When you perform this action, the Automation account is retained.
 
 ## Permissions for Run As accounts and Classic Run As accounts
 

articles/azure-cache-for-redis/cache-how-to-redis-cli-tool.md

@@ -1,116 +1,125 @@
 ---
-title: Use redis-cli with Azure Cache for Redis
-description: Learn how to use *redis-cli* as a command-line tool for interacting with an Azure Cache for Redis as a client
+title: Use redis-cli
+description: Learn how to use redis-cli as a command-line tool for interacting with an Azure Cache for Redis as a client.
 
 
 
-ms.topic: conceptual
-ms.date: 01/04/2024
+ms.topic: how-to
+ms.date: 04/04/2025
 appliesto:
   - ✅ Azure Cache for Redis
 ---
 # Use the Redis command-line tool with Azure Cache for Redis
 
-Use the [redis-cli command-line tool](https://redis.io/docs/connect/cli/) to interact with an Azure Cache for Redis as a client. Use this tool to directly interact with your Azure Cache for Redis instance and for debugging and troubleshooting.
+This article describes how to use the [redis-cli command-line interface](https://redis.io/docs/connect/cli/) to interact with Azure Cache for Redis as a client. You can use *redis-cli* to directly interact with your Azure Redis cache instance, and for debugging and troubleshooting.
+
+## Prerequisite
+
+Access to an Azure Cache for Redis server instance.
 
 ## Install redis-cli
 
-The _redis-cli_ tool is installed automatically with the _Redis package_, which is available for multiple operating systems. See the open source [install Redis](https://redis.io/docs/install/install-redis/) guide for the most detailed documentation on your preferred operating system.
+The redis-cli tool installs automatically with the Redis package, which is available for Linux, macOS, and Windows. For detailed installation instructions, see the open-source [Redis documentation](https://redis.io/docs).
 
-### Linux
+### Install on Linux
 
-The _redis-cli_ runs natively on Linux, and most distributions include a _Redis package_ that contains the _redis-cli_ tool. On Ubuntu, for instance, you install the _Redis package_  with the following commands:
+The redis-cli tool runs natively on Linux, and most Linux distributions include a Redis package that contains redis-cli. For instance, you install the Redis package on Ubuntu with the following commands:
 
 ```linux
 sudo apt-get update
 sudo apt-get install redis
 ```
 
-### Windows
+### Install on Windows
 
-The best way to use _redis-cli_ on a Windows computer is to install the [Windows Subsystem for Linux (WSL)](/windows/wsl/about). The Linux subsystem allows you to run linux tools directly on Windows. To install WSL, follow the [WSL installation instructions](/windows/wsl/install).
+The best way to use redis-cli on Windows is to install the [Windows Subsystem for Linux](/windows/wsl/about) (WSL), which allows you to run Linux tools directly on Windows. To install WSL, see [How to install Linux on Windows with WSL](/windows/wsl/install).
 
-Once WSL is installed, you can install _redis-cli_ using whatever package management is available in the Linux distro you chose for WSL.
+Once installed, use WSL to install a Linux distro, and then install redis-cli by using the available package management for the Linux distro you chose. The default distro for WSL is Ubuntu. For more information, see the open-source [Redis documentation](https://redis.io/docs).
 
-## Gather cache access information
+## Connect using redis-cli
 
-You can gather the information needed to access the cache using these methods:
+To use redis-cli to connect to your Azure Redis cache as a client, you must specify the cache host name, port, and keys. You can retrieve these values by the following methods:
 
 - Azure CLI using [az redis list-keys](/cli/azure/redis#az-redis-list-keys)
 - Azure PowerShell using [Get-AzRedisCacheKey](/powershell/module/az.rediscache/Get-AzRedisCacheKey)
-- Using the Azure portal
+- [Azure portal](https://portal.azure.com)
 
-In this section, you retrieve the keys from the Azure portal.
+The following section describes how to get these values from the Azure portal.
 
 [!INCLUDE [redis-cache-create](includes/redis-cache-access-keys.md)]
 
-## Connect using redis-cli
+### Get other cache information
+
+You might also need to specify the following options for redis-cli:
 
-Open up a shell or terminal on a computer with the _Redis package_ installed. If using WSL, you can [use the Windows Terminal](/windows/wsl/install#ways-to-run-multiple-linux-distributions-with-wsl) to open a Linux command line. Before connecting with redis-cli, check:
+- **TLS**: By default, Azure Redis instances use [TLS](cache-remove-tls-10-11.md) encryption for connections. If the cache uses TLS, you must enable TLS for redis-cli by using the `--tls` option.
+- **Clustering**: If you have a Premium tier cache that uses clustering, or an Enterprise or Enterprise Flash tier cache that uses OSS cluster policy, add the `-c` option to ensure that all shards can be accessed.
 
-1. Whether TLS access is needed - By default, Azure Cache for Redis instances use [TLS](cache-remove-tls-10-11.md) encryption for connections. Whenever TLS is used on the server side, TLS on redis-cli must be enabled using the `--tls` option.
-1. The port used - All Enterprise and Enterprise Flash tier caches use port `10000`. Basic, Standard, and Premium tier caches, however, use either port `6379` for non-TLS connections or port `6380` for TLS connections.
-1. Whether the cache instance uses clustering - If you're using a Premium tier cache that uses clustering or an Enterprise/Enterprise Flash tier cache that is using OSS cluster policy, add the `-c`option to ensure all shards can be accessed.
+### Run the redis-cli connection command
 
-### Examples
+To connect to your cache, open a shell or terminal on a computer with the Redis package installed. On Windows, you can use WSL with [Windows Terminal](/windows/wsl/install#ways-to-run-multiple-linux-distributions-with-wsl) to open a Linux command line.
 
-1. Use the following command to connect to a Basic, Standard, or Premium tier Azure Cache for Redis instance using TLS:
+Run one of the following command lines, depending on your TLS, port, and clustering options. Replace the `<cache name>` and `<access key>` placeholders with the values for your cache.
 
-    ```console
-    redis-cli -p 6380 -h yourcachename.redis.cache.windows.net -a YourAccessKey --tls
-    ```
+- Connect to a Basic, Standard, or Premium tier Azure Redis instance that uses TLS:
 
-1. Connect to a Basic, Standard, or Premium tier Azure Cache for Redis instance that doesn't use TLS:
+  ```console
+  redis-cli -p 6380 -h <cache name>.redis.cache.windows.net -a <access key> --tls
+  ```
 
-    ```console
-    redis-cli -p 6379 -h yourcachename.redis.cache.windows.net -a YourAccessKey
-    ```
+- Connect to a Basic, Standard, or Premium tier Azure Redis instance that doesn't use TLS:
 
-1. Connect to a Basic, Standard, or Premium tier Azure Cache for Redis instance using TLS and clustering:
+  ```console
+  redis-cli -p 6379 -h <cache name>.redis.cache.windows.net -a <access key>
+  ```
 
-    ```console
-    redis-cli -p 6380 -h yourcachename.redis.cache.windows.net -a YourAccessKey --tls -c
-    ```
+- Connect to a Premium tier Azure Redis instance that uses TLS and clustering:
 
-1. Connect to an Enterprise or Enterprise Flash tier cache instance using Enterprise cluster policy with TLS:
+  ```console
+  redis-cli -p 6380 -h <cache name>.redis.cache.windows.net -a <access key> --tls -c
+  ```
 
-    ```console
-    redis-cli -p 10000 -h yourcachename.eastus.redisenterprise.cache.azure.net -a YourAccessKey --tls
-    ```
+- Connect to an Enterprise or Enterprise Flash tier cache instance that uses Enterprise cluster policy with TLS:
 
-1. Connect to an Enterprise or Enterprise Flash tier cache instance using  OSS cluster policy without TLS:
+  ```console
+  redis-cli -p 10000 -h <cache name>.eastus.redisenterprise.cache.azure.net -a <access key> --tls
+  ```
 
-    ```console
-    redis-cli -p 10000 -h yourcachename.eastus.redisenterprise.cache.azure.net -a YourAccessKey -c
-    ```
+- Connect to an Enterprise or Enterprise Flash tier cache instance that uses OSS cluster policy without TLS:
 
-### Testing the connection
+  ```console
+  redis-cli -p 10000 -h <cache name>.eastus.redisenterprise.cache.azure.net -a <access key> -c
+  ```
 
-Once the connection is established, you can issue commands to your Azure Cache for Redis instance. One easy way to test the connection is to use the [`PING`](https://redis.io/commands/ping/) command. This command returns `PONG` in the console.
+You're now connected to your Azure Redis cache instance.
 
-```output
-yourcachename.redis.cache.windows.net:6380> PING
+## Use redis-cli commands with your Azure Redis cache
+
+Once you establish the connection, you can issue commands to your Azure Redis instance at the redis-cli command prompt. The following examples show a connection to a cache named `contoso` that uses port `6380`.
+
+One easy way to test the connection is to use the [`PING`](https://redis.io/commands/ping/) command. The command returns `PONG` in the console.
+
+```console
+contoso.redis.cache.windows.net:6380> PING
 PONG
 ```
 
-You can also run commands like `SET` and `GET`:
+You can also run commands like `SET` and `GET`.
 
-```output
-yourcachename.redis.cache.windows.net:6380> SET hello world
+```console
+contoso.redis.cache.windows.net:6380> SET hello world
 OK
-yourcachename.redis.cache.windows.net:6380> GET hello
+contoso.redis.cache.windows.net:6380> GET hello
 "world"
 ```
 
-You're now connected to your Azure Cache for Redis instance using the _redis-cli_.
-
-## redis-cli alternatives
+## Alternatives to redis-cli
 
-While the _redis-cli_ is a useful tool, you can connect to your cache in other ways for troubleshooting or testing:
+While the redis-cli is a useful tool, you can also use the following other methods to connect to your cache for troubleshooting or testing:
 
-- Azure Cache for Redis offers a [Redis Console](cache-configure.md#redis-console) built into the Azure portal where you can issue commands without needing to install the command-line tool. The Redis Console feature is currently only available in the Basic, Standard, and Premium tiers.
-- [RedisInsight](https://redis.io/insight/) is a rich open source graphical tool for issuing Redis commands and viewing the contents of a Redis instance. It works with Azure Cache for Redis and is supported on Linux, Windows, and macOS.
+- [Redis Console](cache-configure.md#redis-console) lets you issue commands without having to install redis-cli. Redis Console is currently available only for Basic, Standard, and Premium tiers. If Redis Console is available, you can use it by selecting **Console** in the top toolbar of your cache **Overview** page in the Azure portal.
+- [RedisInsight](https://redis.io/insight/) is a rich open-source graphical tool for issuing Redis commands and viewing the contents of a Redis instance. RedisInsight works with Azure Cache for Redis and is supported on Linux, Windows, and macOS.
 
 ## Related content
 
-Get started by creating a [new Enterprise-tier cache](quickstart-create-redis-enterprise.md) instance.
+Get started by creating a [new Enterprise-tier cache](quickstart-create-redis-enterprise.md).

articles/azure-cache-for-redis/includes/media/redis-cache-access-keys/redis-cache-hostname-ports.png

@@ -1,17 +1,25 @@
 ---
-ms.date: 08/16/2024
+ms.date: 04/04/2025
 ms.topic: include
 ms.custom: ignite-2024
 ---
 
-### Retrieve host name, ports, and access keys from the Azure portal
+### Get cache host name, port, and access keys from the Azure portal
 
-To connect your Azure Cache for Redis server, the cache client needs the host name, ports, and a key for the cache. Some clients might refer to these items by slightly different names. You can get the host name, ports, and keys from the [Azure portal](https://portal.azure.com).
+To connect to your Azure Redis cache, the cache client needs the cache host name, ports, and keys. Some clients might refer to these items by slightly different names. Follow these instructions to get the cache host name, ports, and keys from the [Azure portal](https://portal.azure.com).
 
-- To get the host name and ports for your cache, select **Overview** from the **Resource** menu. The host name is of the form `<DNS name>.redis.cache.windows.net`.
+- Get the host name from the cache **Overview** page. The host name is of the form `<cachename>.redis.cache.windows.net`.
 
-  :::image type="content" source="media/redis-cache-access-keys/redis-cache-hostname-ports.png" alt-text="Screenshot showing Azure Cache for Redis properties.":::
+- Select the link next to **Ports** to get the ports. Enterprise and Enterprise Flash tier caches use port `10000`. Basic, Standard, and Premium tier caches use either port `6380` for Transport Layer Security (TLS) connections or port `6379` for non-TLS connections.
 
-- To get the access keys, select **Authentication** from the **Resource** menu. Then, select the **Access keys** tab.
+- To get the access keys, select **Show access keys**.
 
-  :::image type="content" source="media/redis-cache-access-keys/redis-cache-keys.png" alt-text="Screenshot showing Azure Cache for Redis access keys.":::
+  :::image type="content" source="media/redis-cache-access-keys/redis-cache-hostname-ports.png" alt-text="Screenshot showing Azure Redis cache properties.":::
+
+  The **CacheKeys** pane displays the keys.
+ 
+  :::image type="content" source="media/redis-cache-access-keys/redis-cache-keys-pane.png" alt-text="Screenshot showing Azure Redis cache access keys pane.":::
+
+  You can also select **Authentication** under **Settings** in the left navigation menu, and then select the **Access keys** tab.
+
+  :::image type="content" source="media/redis-cache-access-keys/redis-cache-keys.png" alt-text="Screenshot showing Azure Redis cache access keys.":::

articles/azure-cache-for-redis/includes/media/redis-cache-access-keys/redis-cache-keys-pane.png

@@ -1000,7 +1000,7 @@ Moves between resource groups and subscriptions are supported for APIs that use
 > | Resource type | Resource group | Subscription | Region move |
 > | ------------- | ----------- | ---------- | ----------- |
 > | accounts | **Yes** | **Yes** | No. [Learn more](/azure/azure-monitor/app/create-workspace-resource#how-do-i-move-an-application-insights-resource-to-a-new-region). |
-> | actiongroups | No | No | No |
+> | actiongroups | Yes | Yes | No |
 > | activitylogalerts | No | No | No |
 > | alertrules | **Yes** | **Yes** | No |
 > | autoscalesettings | **Yes** | **Yes** | No |

articles/azure-cache-for-redis/includes/media/redis-cache-access-keys/redis-cache-keys.png

@@ -13,7 +13,7 @@ Microsoft regularly applies important updates to the Azure VMware Solution for n
 
 ## April 2025
 
-Public Preview of the next generation of Azure VMware Solution is here. Azure VMware Solution in an Azure Virtual Network is now available in East US, UK South, Switzerland North, and Japan East on the AV64 SKU. With this capability, we've achieved infrastructure innovation, powered by Azure Boost, simplifying networking, delivering 100 Gbps throughput, lowering latency, and boosting performance for VMware vSphere workloads. Private clouds are deployed inside a virtual network, enabling your private cloud with standard Azure Networking. Azure ExpressRoute is no longer required.
+**AV48 SKU**
 
 Azure VMware Solution AV48 node size is now available in the Japan East region. The AV48 node is built on Intel Xeon Gold 6442Y CPUs with a total of 48 physical cores, 1 TB of Memory and 19.2 TB of total storage.