We have an use case that restrict the specific port for security. So It would be good to be able to change the port so that it can be applied to various user environments.

The Application we support uses Azure Redis cache for session state. Currently Redis and the application is in a vNet in CentralUS. The application is working with Redis. Since we are using Azure Traffic Manager, we would like to setup our application in eastUS in it's own vNet and peer to the Redis in CentralUS. Currently, this is not permitted.

Currently there is no way of scaling down to C0 or C1 basic from the standard pricing, this should be there as a part of PAAS product like any other products in the Azure.

We don't have high cache size requirements (<50MB) but looking to use VNET integration, view, export, geo replication features. Currently its only allowed with the premium tier that starts with 6GB/$400+. We will need cache for each environment DEV, QA, STG, PROD. This kind of cost is not justified for the small apps (API Management pricing have the same issues)

Hi. I've created Azure redis cache with the following configuration.
- Clustered mode. (2- shard)
- 3 replicas for each primary node.
It looks like redis only provide single endpoint to client.
How my client application access readonly replica?
If it's not possible at the moment, do you have any plans to provide it?
Thanks.

Can we please provide option to enable and collect the diagnostics logs for the Azure Redis Cache instance.

Note: As of now Azure redis supports only metrics but not logging

Redis 6.0 is released and brings a highly desired feature such as access control.

Are there plans to support Redis 6.0?

We would like to use Redis Streams, so we would like if Azure Cache supported redis version 5.0

redis cache deployments from the portal always using the same name "redis.cache" and new deployments will replace the old deployment history. Please work on adding a time stamp in the deployment name.

It would be good to have the ability to add external modules to Redis Cache service. We have an use case to store JSON in Redis and ReJSON module supports that. Inability to add ReJSON to Azure Redis Cache costs us a lot.

When maintenance is carried out on the Redis Cache hosts or Redis Services, no indication of this is given anywhere.
We need to be forewarned about maintenance.
When monitoring starts detecting issues we are then ready for it or at least know why we are getting the connection errors or timeouts.

Currently when maintenance is done:
Azure service status => ZERO INDICATION
Azure Planned maintenance => ZERO INDICATION
Health Alerts => ZERO INDICATION
Redis Cache Health => ZERO INIDCATION

I have an ARM template that creates Redis resources, basic tier. Usually, Redis spins up fine, but, occasionally, it completes with Azure Redis giving a status of "Failed". All calls will then result in an error. I then have to delete the resource and try again.

This is something that Azure should be doing on its own. When Azure reports that it created a resource for me, there should actually be a working resource there.

Solution won't recognize .AddUserSecret until you add a nuget package fot it Microsoft.Extensions.Configuration.AddUserSecrets

We want to see the health report of Redis Cache if host server or guest server on which Redis cache is running is getting upgraded.

Currently, we don't have any report about when the redis cache became unavailable. Yesterday our redis cache was failing to make connection to our application and it failed with Socket failure error when I looked into the resource health it was showing available so this information was not correct.

hi, in one of my api i started calling redis cache using microsoft redis client library for .net core. so it will check in cache and if not found then it will call another microservice using httpclient call. Am noting in application insight end to end transaction details page its not showing up calls made to redis cache. I will have to use custom api to send that data to application insight it would be great if application insights even shows external calls to redis cache grouped in transaction details report in application insights

Is there a way to increase the number of databases? Based on the tier, I am limited to fixed number of databases, but is there a negative impact if I wanted to increase beyond this number? Since the memory of the cache applies across all databases, why is there these limits?

Currently if a Redis node swaps due to patching or failing there is no way to figure this out in the Azure portal. The only way to find out is to log a service ticket. Which isnt great for the customer and worse for MS.

Please provide an event log in the portal that customers can use to see what node failures or swaps happen in the cluster.