Merge pull request #311797 from dlepow/amrauth

[AMR] Connection troubleshoot - CLI

Author: prmerger-automator[bot]

articles/redis/entra-for-authentication.md

@@ -1,7 +1,7 @@
 ---
 title: Use Microsoft Entra for cache authentication with Azure Managed Redis
 description: Learn how to use Microsoft Entra with Azure Managed Redis.
-ms.date: 11/05/2025
+ms.date: 02/12/2026
 ms.topic: conceptual
 ms.custom:
   - references_regions
@@ -66,13 +66,37 @@ If you have used access keys in the past for authentication, you need to update
 
 ## Troubleshooting Microsoft Entra ID and your cache
 
-If your application fails to access the Azure Managed Redis instance through Microsoft Entra ID, use this PowerShell script:
+If you encounter authentication issues with Microsoft Entra ID on your Azure Managed Redis instance, you can use the Azure CLI to test connectivity or validate your tokens using a PowerShell script.
 
-[EntraTokenValidation](https://github.com/AzureManagedRedis/DiagnosticTools/tree/main/EntraTokenValidation)
+### Test connectivity with Azure CLI
+
+You can use the Azure CLI to quickly test if you can connect to your Redis cluster. The [az redisenterprise test-connection](/cli/azure/redisenterprise#az_redisenterprise_test_connection) command is helpful for debugging connection issues and verifies end-to-end connectivity by sending a `ping` command. 
+
+For prerequisites to use the Azure CLI with Azure Managed Redis, see [Manage an Azure Managed Redis cache using the Azure CLI](scripts/create-manage-cache.md).
+
+
+To test connection with Microsoft Entra ID authentication (the default), run the following command:
+
+```azurecli
+az redisenterprise test-connection --name <cache-name> --resource-group <resource-group-name>
+```
 
-Use this PowerShell script to validate Microsoft Entra ID tokens for Azure Managed Redis Cache resources. The script validates tokens and verifies access policies to help you diagnose authentication issues.
+Or explicitly specify Entra authentication:
+
+```azurecli
+az redisenterprise test-connection --name <cache-name> --resource-group <resource-group-name> --auth entra
+```
+
+> [!NOTE]
+> This command uses the credential established through `az login`, which supports user accounts, managed identities, or service principals.
+
+### Validate Microsoft Entra tokens
+
+If your application fails to access the Azure Managed Redis instance through Microsoft Entra ID, you can also use the following PowerShell script:
+
+[EntraTokenValidation](https://github.com/AzureManagedRedis/DiagnosticTools/tree/main/EntraTokenValidation)
 
-If you're having trouble using Microsoft Entra ID to authenticate Redis connections, run this script to analyze your Microsoft Entra token and identify any issues.
+This PowerShell script validates Microsoft Entra ID tokens for Azure Managed Redis Cache resources. The script checks tokens and verifies access policies to help you diagnose authentication issues.
 
 ## Client library support
 

articles/redis/troubleshoot-connectivity.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot connectivity in Azure Managed Redis
 description: Learn how to resolve connectivity problems when creating clients with Azure Managed Redis.
-ms.date: 05/18/2025
+ms.date: 02/12/2026
 ms.topic: conceptual
 ms.custom:
   - template-concept
@@ -21,6 +21,7 @@ In this article, we provide troubleshooting help for connecting your client appl
   - [Kubernetes hosted applications](#kubernetes-hosted-applications)
   - [Linux-based client application](#linux-based-client-application)
 - [Continuous connectivity issues](#continuous-connectivity)
+  - [Test connectivity using Azure CLI](#test-connectivity-using-azure-cli)
   - [Test connectivity using _redis-cli_](#test-connectivity-using-redis-cli)
   - [Test connectivity using PSPING](#test-connectivity-using-psping)
   - [Private endpoint configuration](#private-endpoint-configuration)
@@ -50,6 +51,34 @@ Using optimistic TCP settings in Linux might cause client applications to experi
 
 If your application can't connect to your Azure Managed Redis instance, it's possible some configuration on the cache isn't set up correctly. The following sections offer suggestions on how to make sure your cache is configured correctly.
 
+### Test connectivity using Azure CLI
+
+You can use the Azure CLI to quickly test if you can connect to your Redis cluster. The [az redisenterprise test-connection](/cli/azure/redisenterprise#az_redisenterprise_test_connection) command is helpful for debugging connection issues and verifies end-to-end connectivity by sending a `ping` command. 
+
+For prerequisites to use the Azure CLI with Azure Managed Redis, see [Manage an Azure Managed Redis cache using the Azure CLI](scripts/create-manage-cache.md).
+
+
+To test connection with Microsoft Entra ID authentication (the default), run the following command:
+
+```azurecli
+az redisenterprise test-connection --name <cache-name> --resource-group <resource-group-name>
+```
+
+Or explicitly specify Entra authentication:
+
+```azurecli
+az redisenterprise test-connection --name <cache-name> --resource-group <resource-group-name> --auth entra
+```
+
+> [!NOTE]
+> This command uses the credential established through `az login`, which supports user accounts, managed identities, or service principals.
+
+To test connection with access key authentication, run the following command:
+
+```azurecli
+az redisenterprise test-connection --name <cache-name> --resource-group <resource-group-name> --auth accesskey --access-key <access-key-value>
+```
+
 ### Test connectivity using _redis-cli_
 
 Test connectivity using _redis-cli_. For more information on CLI, [Use the Redis command-line tool with Azure Managed Redis](how-to-redis-cli-tool.md).