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.

PREREQUISITES: This article describes how to setup Redis in a load-balanced environment.
To learn how to setup Redis as a shared cache location, see Configure the cache provider. 

To provision Redis cache for your Sitefinity CMS website, you must navigate to your Azure portal and search for Azure Cache for Redis.

Configure a running instance of Azure Redis and get a connection string. 
For more information, see Microsoft's documentation » Use Azure Cache for Redis in .NET Framework. 

Perform the following:

1. In Sitefinity CMS backend, navigate to Administration » Settings » Advanced » System » LoadBalancing » Redis Settings » Connection String.
2. 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
3. Save your changes.

RECOMMENDATION: 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 tiers, see Redis Cache Pricing.

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