Skip to content

Commit 9e1c888

Browse files
committed
more touchups
1 parent 8cb7a8d commit 9e1c888

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,26 +4,26 @@ description: Learn how to create and configure a data access policy for Azure Ca
44
ms.custom: references_regions, ignite-2024
55

66
ms.topic: conceptual
7-
ms.date: 04/14/2025
7+
ms.date: 04/15/2025
88
appliesto:
99
- ✅ Azure Cache for Redis
1010

1111
---
1212

1313
# Configure custom data access policies
1414

15-
Managing access to your Azure Redis cache instance is critical to ensuring that the right users have access to the right set of data and commands. Redis version 6 introduced the [Access Control List](https://redis.io/docs/management/security/acl/) (ACL), which specifies the keys that certain users can access and the commands that they can execute. For example, you can prohibit specific users from using the [DEL](https://redis.io/commands/del/) command to delete keys in the cache.
15+
Managing access to your Azure Redis cache instance is critical to ensuring that the right users have access to the right set of data and commands. Redis version 6 introduced the [Access Control List](https://redis.io/docs/management/security/acl/) (ACL), which lists the keys that specific users can access and the commands that they can execute. For example, you can prohibit specific users from using the [DEL](https://redis.io/commands/del/) command to delete keys in the cache.
1616

17-
Azure Cache for Redis integrates this ACL functionality with Microsoft Entra ID to allow you to configure data access policies for your application's users, service principal, and managed identity. Azure Cache for Redis offers three built-in access policies that you can assign via role-based access control (RBAC): **Data Owner**, **Data Contributor**, and **Data Reader**.
17+
Azure Cache for Redis integrates this ACL functionality with Microsoft Entra to allow you to configure and assign data access policies for your application's users, service principal, and managed identity. Azure Cache for Redis offers three built-in access policies that you can assign via role-based access control (RBAC): **Data Owner**, **Data Contributor**, and **Data Reader**.
1818

19-
If the built-in access policies don't satisfy your data protection and isolation requirements, you can create and use your own custom data access policies. This article describes configuring a custom data access policy for Azure Cache for Redis and enabling RBAC via Microsoft Entra ID authentication.
19+
If the built-in access policies don't satisfy your data protection and isolation requirements, you can create and use your own custom data access policies. This article describes configuring a custom data access policy for Azure Cache for Redis and enabling RBAC via Microsoft Entra authentication.
2020

2121
## Limitations
2222

2323
- Configuring data access policies isn't supported on Enterprise and Enterprise Flash tiers.
2424
- Redis ACL and data access policies aren't supported on Azure Redis instances that run Redis version 4.
2525
- Microsoft Entra authentication and authorization are supported only for Secure Socket Layer (SSL) connections.
26-
- Some Redis commands are blocked in Azure Cache for Redis. For more information, see [Redis commands not supported in Azure Cache for Redis](cache-configure.md#redis-commands-not-supported-in-azure-cache-for-redis)
26+
- Some Redis commands are blocked in Azure Cache for Redis. For more information, see [Redis commands not supported in Azure Cache for Redis](cache-configure.md#redis-commands-not-supported-in-azure-cache-for-redis).
2727

2828
## Redis ACL permissions
2929

@@ -53,19 +53,19 @@ Redis supports the following useful command categories. For more information and
5353
5454
### Commands
5555

56-
*Commands* allow you to control which specific commands a particular Redis user can run. In a permissions string, use `+command` to allow a command or `-command` to disallow a command.
56+
*Commands* allow you to control which specific commands a particular Redis user can run. In a permissions string, use `+<command>` to allow a command or `-<command>` to disallow a command.
5757

5858
### Keys
5959

6060
*Keys* allow you to control access to specific keys or groups of keys stored in the cache. Use `~<pattern>` in a permission string to provide a pattern for keys. Use either `~*` or `allkeys` to indicate that the permissions apply to all keys in the cache.
6161

6262
## Configure a custom data access policy for your application
6363

64-
To configure a custom data access policy, you create a permissions string to use as your custom access policy, and enable Microsoft Entra ID authentication and authorization to your cache.
64+
To configure a custom data access policy, you create a permissions string to use as your custom access policy, and enable Microsoft Entra authentication for your cache.
6565

6666
### Specify permissions
6767

68-
Configure the permissions string according to your requirements. The following examples show permission strings for various scenarios:
68+
Configure permission strings according to your requirements. The following examples show permission strings for various scenarios:
6969

7070
|Permissions string|Description|
7171
|------------------|-----------|
@@ -106,7 +106,7 @@ Respond **Yes** to the popup dialog box asking if you want to disable access key
106106
107107
## Configure your Redis client to use Microsoft Entra ID
108108

109-
Because most Azure Cache for Redis clients assume that a password and access key are used for authentication, you probably need to update your client workflow to support authentication by using a specific Microsoft Entra user name and 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).
109+
Most Azure Cache for Redis clients assume that a password and access key are used for authentication. You might need to update your client workflow to support authentication and authorization using a specific Microsoft Entra user name and 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).
110110

111111
## Related content
112112

0 commit comments

Comments
 (0)