ACL commands not allowed on Azure Managed Redis instance

Question

ACL commands not allowed on Azure Managed Redis instance

Raisa Varghese [V] 20

I am using an Azure Redis Enterprise instance (dev-cache) with the following configuration:

Location: West US 3

SKU: Balanced_B0

Modules: RediSearch 2.10.18, RedisJSON 2.8.10

Client Protocol: Encrypted

Clustering Policy: EnterpriseCluster

When I try to create a new user with ACL using the command:
ACL SETUSER demo-svc on >DemoPass123! +@read +set ~demo*

I get the following error:
(error) ERR command 'acl|setuser' is not allowed

Are ACL commands supported on Azure Redis Enterprise instances?

If supported, is there a configuration or permission I need to enable?
Are there any alternatives to implement role-based access in this setup?

Mahesh Kurva 10,520 Reputation points Microsoft External Staff Moderator

2025-09-01T16:32:35.95+00:00
Hi Raisa Varghese [V],

Greetings!!

Currently, ACL commands like ACL SETUSER are not supported on Azure Redis Enterprise instances.

Unfortunately, there’s no setting or permission you can enable to allow ACL commands on this tier.

If you need role-based access, here are some options:

Use application-level access control: Handle roles and permissions within your app before connecting to Redis.

Use different Redis instances for different services or access levels.

Microsoft Entra authentication is supported only in Basic, Standard, and Premium tiers.

You can define custom access policies using permission strings like +@read +set ~demo*.

These policies are assigned via RBAC and enforced through Microsoft Entra authentication.

For more information, please refer the documentation:

Configure custom data access policies.

Redis commands not supported in Azure Cache for Redis.

I hope this information helps. Please do let us know if you have any further queries.

Answer accepted by question author

0 additional answers

Your answer

Mahesh Kurva 10,520 Reputation points Microsoft External Staff Moderator

2025-09-01T16:32:35.95+00:00

Hi Raisa Varghese [V],

Greetings!!

Currently, ACL commands like ACL SETUSER are not supported on Azure Redis Enterprise instances.

Unfortunately, there’s no setting or permission you can enable to allow ACL commands on this tier.

If you need role-based access, here are some options:

Use application-level access control: Handle roles and permissions within your app before connecting to Redis.

Use different Redis instances for different services or access levels.

Microsoft Entra authentication is supported only in Basic, Standard, and Premium tiers.

You can define custom access policies using permission strings like +@read +set ~demo*.

These policies are assigned via RBAC and enforced through Microsoft Entra authentication.

For more information, please refer the documentation:

Configure custom data access policies.

Redis commands not supported in Azure Cache for Redis.

I hope this information helps. Please do let us know if you have any further queries.

Answer 1

Mahesh Kurva 10,520 Microsoft External Staff Moderator

Hi Raisa Varghese [V],

That menu is only available in the Basic, Standard, and Premium tiers not in Enterprise or Enterprise Flash. Hence, you won’t see it in your Azure portal for a Redis Enterprise instance.

User's image Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Raisa Varghese [V] 20 Reputation points

2025-09-02T04:39:03.8166667+00:00

For the 4th option -

"define custom access policies using permission strings like +@read +set ~demo*".

The menu Data Access Configuration is not coming up in the side menu of the Azure managed redis instance.

https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-configure-role-based-access-control#create-the-custom-data-access-policy
Mahesh Kurva 10,520 Reputation points Microsoft External Staff Moderator

2025-09-03T18:02:36.9133333+00:00

Hi Raisa Varghese [V],

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mahesh Kurva 10,520 Reputation points Microsoft External Staff Moderator

2025-09-04T18:19:37.4233333+00:00

Hi Raisa Varghese [V],

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Raisa Varghese [V] 20 Reputation points

2025-09-08T05:51:22.76+00:00

Hi Mahesh Kurva

Thank you for your guidance. Got an understanding of the difference in availability of access policies across the tiers.
Mahesh Kurva 10,520 Reputation points Microsoft External Staff Moderator

2025-09-08T06:40:16.8766667+00:00

Hi Raisa Varghese [V],

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Vanshita Rohela 0 Reputation points

2026-07-23T08:18:08.74+00:00

Hi @Mahesh Kurva

By any chance could you provide the Microsoft documentation where this is clearly stated that data plane access policies cannot be given on managed redis? While trying through terraform, I received Bad Request error stating access strings are not supported on databases with modules enabled.