Skip to content

Commit 79f6176

Browse files
committed
fixing broken bookmarks
1 parent b7558c6 commit 79f6176

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To use the ACL integration, your client application must assume the identity of
3636
- 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).
3737

3838
> [!IMPORTANT]
39-
> 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).
39+
> 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).
4040
4141
## Enable Microsoft Entra authentication on your cache
4242

@@ -104,7 +104,7 @@ If you want to use a custom access policy instead of Redis Data Owner, go to **D
104104

105105
:::image type="content" source="media/cache-azure-active-directory-for-authentication/cache-new-redis-user.png" alt-text="Screenshot showing the available Access Policies.":::
106106

107-
1. Choose either **User or service principal** or **Managed Identity** to determine how to assign access to your Azure Cache for Redis instance. If you select **User or service principal** and you want to add a user, you must first [enable Microsoft Entra authentication](#enable-microsoft-entra-id-authentication-on-your-cache).
107+
1. Choose either **User or service principal** or **Managed Identity** to determine how to assign access to your Azure Cache for Redis instance. If you select **User or service principal** and you want to add a user, you must first [enable Microsoft Entra authentication](#enable-microsoft-entra-authentication-on-your-cache).
108108

109109
1. Then, choose **Select members** and choose **Select**. Then, select **Next: Review + assign**.
110110

articles/azure-cache-for-redis/cache-configure-role-based-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ The following list contains some examples of permission strings for various scen
131131
132132
## Configure your Redis client to use Microsoft Entra ID
133133

134-
Now that you have configured Redis User and Data access policy for configuring role based access control, you need to update your client workflow to support authenticating using a specific user/password. To learn how to configure your client application to connect to your cache instance as a specific Redis User, see [Configure your Redis client to use Microsoft Entra ID](cache-azure-active-directory-for-authentication.md#configure-your-redis-client-to-use-microsoft-entra-id).
134+
Now that you have configured Redis User and Data access policy for configuring role based access control, you need to update your client workflow to support authenticating using a specific user/password. To learn how to configure your client application to connect to your cache instance as a specific Redis User, see [Configure your Redis client to use Microsoft Entra](cache-azure-active-directory-for-authentication.md#configure-your-redis-client-to-use-microsoft-entra).
135135

136136
## Next steps
137137

0 commit comments

Comments
 (0)