Configure Azure Redis cache

When you upload your site on several instances in Azure or want to scale the instances, you need to prepare the communication infrastructure to transmit messages between the nodes. For example, to communicate cache invalidation. Sitefinity CMS uses Redis message sender that you must configure for NLB communication in Azure Web Apps.

NOTE: In Sitefinity CMS Redis Cache is used for NLB communication only. It is not used for persisting items in cache.

Perform the following:

1. In Microsoft Azure, configure a running instance of Azure Redis and get a connection string.
   For more information, see How to Use Azure Redis Cache.
2. In Sitefinity CMS backend, navigate to Administration » Settings » Advanced » System » LoadBalancing » Redis Settings » Connection String.
3. In the Redis Settings page that appears, enter the connection string and prefix key for all messages to be used from this site.
This enables using Redis from different client applications.
Ensure that the ConnectionString field is in the following format: 
$redisPrimaryKey@$redisCacheName.redis.cache.windows.net?ssl=true
For example, 
yq2YLjsdlf34iwushrgesdeirkfs034jsdls493=@mydomain.redis.cache.windows.net?ssl=true
4. Save your changes.

NOTE: Because Redis Cache is not used for storing cache data, but for NLB communication only, Sitefinity CMS can work with the minimum pricing tier for Azure Redis – Basic tier for development purposes. If you want to achieve failover redundancy for a production environment, we recommend using at least Azure Standard Pricing tier (C0+). For more information about the different pricing tires, see Redis Cache Pricing.

NOTE: Sitefinity CMS and Redis are completely decoupled and they can work both (or one of them) on-premises infrastructure.