edit pass: cache-azure-active-directory-for-authentication

Author: paulth1

articles/azure-cache-for-redis/cache-azure-active-directory-for-authentication.md

@@ -1,7 +1,7 @@
 ---
-title: Use Microsoft Entra ID for cache authentication
+title: Use Microsoft Entra for cache authentication
 titleSuffix: Azure Cache for Redis
-description: Learn how to use Microsoft Entra ID with Azure Cache for Redis.
+description: Learn how to use Microsoft Entra with Azure Cache for Redis.
 author: flang-msft
 
 ms.custom: references_regions
@@ -12,13 +12,13 @@ ms.author: franlanglois
 
 ---
 
-# Use Microsoft Entra ID for cache authentication
+# Use Microsoft Entra for cache authentication
 
-Azure Cache for Redis offers two methods to [authenticate](cache-configure.md#authentication) to your cache instance: access keys and Microsoft Entra ID.
+Azure Cache for Redis offers two methods to [authenticate](cache-configure.md#authentication) to your cache instance: access keys and Microsoft Entra.
 
 Although access key authentication is simple, it comes with a set of challenges around security and password management. For contrast, in this article, you learn how to use a Microsoft Entra token for cache authentication.
 
-Azure Cache for Redis offers a password-free authentication mechanism by integrating with [Microsoft Entra ID](/azure/active-directory/fundamentals/active-directory-whatis). This integration also includes [role-based access control](/azure/role-based-access-control/) functionality provided through [access control lists (ACLs)](https://redis.io/docs/management/security/acl/) supported in open-source Redis.
+Azure Cache for Redis offers a password-free authentication mechanism by integrating with [Microsoft Entra](/azure/active-directory/fundamentals/active-directory-whatis). This integration also includes [role-based access control](/azure/role-based-access-control/) functionality provided through [access control lists (ACLs)](https://redis.io/docs/management/security/acl/) supported in open-source Redis.
 
 To use the ACL integration, your client application must assume the identity of a Microsoft Entra entity, like service principal or managed identity, and connect to your cache. In this article, you learn how to use your service principal or managed identity to connect to your cache. You also learn how to grant your connection predefined permissions based on the Microsoft Entra artifact that's used for the connection.
 
@@ -30,15 +30,15 @@ To use the ACL integration, your client application must assume the identity of
 
 ## Prerequisites and limitations
 
-- Microsoft Entra ID-based authentication is supported for SSL connections and TLS 1.2 or higher.
-- Microsoft Entra ID-based authentication isn't supported on Azure Cache for Redis instances that [depend on Azure Cloud Services](./cache-faq.yml#caches-with-a-dependency-on-cloud-services--classic).
-- Microsoft Entra ID-based authentication isn't supported in the Enterprise tiers of Azure Cache for Redis Enterprise.
+- Microsoft Entra authentication is supported for SSL connections and TLS 1.2 or higher.
+- Microsoft Entra authentication isn't supported on Azure Cache for Redis instances that [depend on Azure Cloud Services](./cache-faq.yml#caches-with-a-dependency-on-cloud-services--classic).
+- Microsoft Entra authentication isn't supported in the Enterprise tiers of Azure Cache for Redis Enterprise.
 - Some Redis commands are blocked. For a full list of blocked commands, see [Redis commands not supported in Azure Cache for Redis](cache-configure.md#redis-commands-not-supported-in-azure-cache-for-redis).
 
 > [!IMPORTANT]
-> After a connection is established by using a Microsoft Entra token, client applications must periodically refresh the Microsoft Entra token before expiry. Then the apps must send an `AUTH` command to the Redis server to avoid disrupting connections. For more information, see [Configure your Redis client to use Microsoft Entra ID](#configure-your-redis-client-to-use-microsoft-entra-id).
+> After a connection is established by using a Microsoft Entra token, client applications must periodically refresh the Microsoft Entra token before expiry. Then the apps must send an `AUTH` command to the Redis server to avoid disrupting connections. For more information, see [Configure your Redis client to use Microsoft Entra](#configure-your-redis-client-to-use-microsoft-entra-id).
 
-## Enable Microsoft Entra ID authentication on your cache
+## Enable Microsoft Entra authentication on your cache
 
 1. In the Azure portal, select the Azure Cache for Redis instance where you want to configure Microsoft Entra token-based authentication.
 
@@ -55,17 +55,17 @@ To use the ACL integration, your client application must assume the identity of
    > [!IMPORTANT]
    > After the enable operation is finished, the nodes in your cache instance reboot to load the new configuration. We recommend that you perform this operation during your maintenance window or outside your peak business hours. The operation can take up to 30 minutes.
 
-For information on how to use Microsoft Entra ID with the Azure CLI, see the [reference pages for identity](/cli/azure/redis/identity).
+For information on how to use Microsoft Entra with the Azure CLI, see the [reference pages for identity](/cli/azure/redis/identity).
 
 ## Disable access key authentication on your cache
 
-Using Microsoft Entra ID is the secure way to connect your cache. We recommend that you use Microsoft Entra ID and disable access keys.
+Using Microsoft Entra is the secure way to connect your cache. We recommend that you use Microsoft Entra and disable access keys.
 
-When you disable access key authentication for a cache, all existing client connections are terminated, whether they use access keys or Microsoft Entra ID authentication. Follow the recommended Redis client best practices to implement proper retry mechanisms for reconnecting Microsoft Entra-based connections, if any.
+When you disable access key authentication for a cache, all existing client connections are terminated, whether they use access keys or Microsoft Entra authentication. Follow the recommended Redis client best practices to implement proper retry mechanisms for reconnecting Microsoft Entra-based connections, if any.
 
 Before you disable access keys:
 
-- Microsoft Entra ID authorization must be enabled.
+- Microsoft Entra authorization must be enabled.
 - Disabling access keys is only available for Basic, Standard, and Premium tier caches.
 - For geo-replicated caches, you must:
 
@@ -88,7 +88,7 @@ If you have a cache where access keys are used and you want to disable access ke
 1. Confirm that you want to update your configuration by selecting **Yes**.
 
 > [!IMPORTANT]
-> When the **Disable Access Keys Authentication** setting is changed for a cache, all existing client connections, using access keys or Microsoft Entra ID, are terminated. Follow the best practices to implement proper retry mechanisms for reconnecting Microsoft Entra-based connections. For more information, see [Connection resilience](cache-best-practices-connection.md).
+> When the **Disable Access Keys Authentication** setting is changed for a cache, all existing client connections, using access keys or Microsoft Entra, are terminated. Follow the best practices to implement proper retry mechanisms for reconnecting Microsoft Entra-based connections. For more information, see [Connection resilience](cache-best-practices-connection.md).
 
 ## Use data access configuration with your cache
 
@@ -115,9 +115,9 @@ If you want to use a custom access policy instead of Redis Data Owner, go to **D
    > [!IMPORTANT]
    > After the enable operation is finished, the nodes in your cache instance reboot to load the new configuration. We recommend that you perform this operation during your maintenance window or outside your peak business hours. The operation can take up to 30 minutes.
 
-## Configure your Redis client to use Microsoft Entra ID
+## Configure your Redis client to use Microsoft Entra
 
-Because most Azure Cache for Redis clients assume that a password and access key are used for authentication, you likely need to update your client workflow to support authentication by using Microsoft Entra ID. In this section, you learn how to configure your client applications to connect to Azure Cache for Redis by using a Microsoft Entra token.
+Because most Azure Cache for Redis clients assume that a password and access key are used for authentication, you likely need to update your client workflow to support authentication by using Microsoft Entra. In this section, you learn how to configure your client applications to connect to Azure Cache for Redis by using a Microsoft Entra token.
 
 ### Microsoft Entra client workflow
 
@@ -135,9 +135,9 @@ Because most Azure Cache for Redis clients assume that a password and access key
 
 ### Client library support
 
-The library [`Microsoft.Azure.StackExchangeRedis`](https://www.nuget.org/packages/Microsoft.Azure.StackExchangeRedis) is an extension of `StackExchange.Redis` that enables you to use Microsoft Entra ID to authenticate connections from a Redis client application to an Azure Cache for Redis. The extension manages the authentication token, including proactively refreshing tokens before they expire to maintain persistent Redis connections over multiple days.
+The library [`Microsoft.Azure.StackExchangeRedis`](https://www.nuget.org/packages/Microsoft.Azure.StackExchangeRedis) is an extension of `StackExchange.Redis` that enables you to use Microsoft Entra to authenticate connections from a Redis client application to an Azure Cache for Redis. The extension manages the authentication token, including proactively refreshing tokens before they expire to maintain persistent Redis connections over multiple days.
 
-[This code sample](https://github.com/Azure/Microsoft.Azure.StackExchangeRedis) demonstrates how to use the `Microsoft.Azure.StackExchangeRedis` NuGet package to connect to your Azure Cache for Redis instance by using Microsoft Entra ID.
+[This code sample](https://github.com/Azure/Microsoft.Azure.StackExchangeRedis) demonstrates how to use the `Microsoft.Azure.StackExchangeRedis` NuGet package to connect to your Azure Cache for Redis instance by using Microsoft Entra.
 
 The following table includes links to code samples. They demonstrate how to connect to your Azure Cache for Redis instance by using a Microsoft Entra token. Various client libraries are included in multiple languages.