# Cache - Azure Cache for Redis

{% hint style="info" %}
From version 1.23.0, we recommend using Azure Managed Redis instead of Azure Cache for Redis for new environments, following Microsoft’s own recommendations.

*All instances of Azure Cache for Redis tiers (Basic, Standard, and Premium) will be retired on September 30, 2028.*

*All instances of Azure Cache for Redis Enterprise and Enterprise Flash tiers will be retired on March 31, 2027.*

\
<https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/retirement-faq><br>
{% endhint %}

## Creating Azure Managed Redis

After navigating to **Azure Managed Redis**, hit Create. In the following screen assign your Resource group, give the cache a Name, choose a location and assign the **SKU B1** type (or **B3** if you want to use Active geo-replication). The type selection is up to you but we recommend a cache with at least 1GB of storage.

#### Basics

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2FyoXbypent7VtYUSzMi6q%2Fimage.png?alt=media&#x26;token=b1521830-9fa2-4279-b27d-017f8e6e090d" alt=""><figcaption><p>Basic Azure Managed Redis settings</p></figcaption></figure>

#### Networking settings

{% hint style="warning" %}
It is recommended to use a Private Endpoint connection but for hassle free non-Prod environment deployments a Public Endpoint is also an option.
{% endhint %}

After selecting **Private Endpoint** click Add private endpoint and fill in the settings. Location and resource group settings should correspond to those of your server containers'.&#x20;

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2F53yhHCH7JfePypNVZ8Xw%2Fimage.png?alt=media&#x26;token=39412ebe-e777-4400-bcf4-9af32de029ae" alt=""><figcaption><p>Networking settings</p></figcaption></figure>

#### Advanced settings

{% hint style="warning" %}
For now we only support **Non-clustered** or **Enterprise** cluster policy
{% endhint %}

Make sure the Eviction Policy is set to **All Keys LRU** or **All Keys LFU.**

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2FqomXhKvm0kHG0plUJMZ7%2Fimage.png?alt=media&#x26;token=2216795a-22fd-4cd0-be22-320b30ae3788" alt=""><figcaption><p>Advanced settings</p></figcaption></figure>

Enable Access Keys Authentication and keep the rest of the settings default unless your use-case demands otherwise.

Validate your settings and create the cache.

### Connection strings

The format of your connection string will depend on whether you're using SSL or non-SSL connection.

* **SSL** - `rediss://default:<access_key>@<hostname>:<port>`
* **Non-SSL** - `redis://default:<access_key>@<hostname>:<port>`

Note the difference is in the first part of the string `rediss://` x `redis://`.

* You can find the `<access_key>` under Settings / Authentication / Access keys
* You can find the `<hostname>` and `<port>` under Settings / Properties / Endpoint

## Creating Azure Cache for Redis (retiring)

After navigating to **Azure Cache for Redis**, hit Create. In the following screen assign your Resource group, give the cache a DNS name, choose a location and assign the **Standard C1** type. The type selection is up to you but we recommend a cache with at least 1GB of storage.&#x20;

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2FMVOpO9obw4ejv5fW4PB5%2Fimage.png?alt=media&#x26;token=2fee0f26-3ce8-4005-bda9-e6b1eabe638f" alt=""><figcaption><p>Basic Azure Cache for Redis settings</p></figcaption></figure>

#### Networking settings

{% hint style="warning" %}
It is recommended to use a Private Endpoint connection but for hassle free non-Prod environment deployments a Public Endpoint is also an option.
{% endhint %}

After selecting **Private Endpoint** click Add private endpoint and fill in the settings. Location and resource group settings should correspond to those of your server containers'.&#x20;

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2F8AjCPWcW0VZ3oMtsJ0Lo%2Fimage.png?alt=media&#x26;token=b262ed24-2088-44cc-988d-b38d8f625442" alt=""><figcaption><p>Networking settings</p></figcaption></figure>

Keep the rest of the settings default unless your use-case demands otherwise. Optionally also add tags for easier resource management.

Validate your settings and create the cache.

### Necessary settings and connection strings

**Maxmemory policy**

After the cache has been provisioned, navigate to it's Settings/Advanced Settings tab. Once there, change the Maxmemory policy to **allkeys-lru** or **allkeys-lfu**.

**Connection string**

The format of your connection string will depend on whether you're using SSL or non-SSL connection.

* **SSL** - `rediss://<access_key>@<hostname>:<port>`
* **Non-SSL** - `redis://<access_key>@<hostname>:<port>`

Note the difference is in the first part of the string `rediss://` x `redis://`.

* You can find the `<access_key>` under Settings / Access keys
* You can find the `<hostname>` and `<port>` under Settings / Properties

{% hint style="warning" %}

#### Error - Redis Client WRONGPASS

Some Azure Cache for Redis deployments require the connection string to contain the user and not only the access key. The default user is '**default**' so the final connection string would have the following format: `redis(s)://default:<access_key>@<hostname>:<port>`
{% endhint %}

{% hint style="info" %}
Azure Cache for Redis tends to idle after a period of inactivity (10 minutes). To prevent this, and the corresponding expensive cache misses, we recommend setting the REDIS\_PING\_INTERVAL optional Environment Variable.
{% endhint %}