Quickstart: Create an Azure Managed Redis Instance

Azure Managed Redis provides fully integrated and managed Redis Enterprise on Azure. There are four tiers of Azure Managed Redis, each with different performance characteristics:

Three tiers are for in-memory data:

• Memory Optimized Ideal for memory-intensive use cases that require a high memory-to-vCPU ratio (1:8) but don't need the highest throughput performance. It provides a lower price point for scenarios where less processing power or throughput is necessary, making it an excellent choice for development and testing environments.
• Balanced (Memory + Compute) Offers a balanced memory-to-vCPU (1:4) ratio, making it ideal for standard workloads. It provides a healthy balance of memory and compute resources.
• Compute Optimized Designed for performance-intensive workloads requiring maximum throughput, with a low memory-to-vCPU (1:2) ratio. It's ideal for applications that demand the highest performance.

One tier stores data both in-memory and on-disk:

• Flash Optimized Enables Redis clusters to automatically move less frequently accessed data from memory (RAM) to NVMe storage. This reduces performance, but allows for cost-effective scaling of caches with large datasets.

For more information on choosing the right SKU and tier, see Choosing the right tier

• You need an Azure subscription before you begin. If you don't have one, create an account.

Azure Managed Redis is continually expanding into new regions. To check the availability by region for all tiers, see Products available by region.

1. To create an Azure Managed Redis instance, sign in to the Azure portal and select Create a resource.

2. On the New page, in the search box type Azure Cache for Redis.

3. On the New Redis Cache tab, configure the settings for your new cache on the Basics .

   Expand table

   Setting	Choose a value	Description
   Subscription	Drop down and select your subscription.	The subscription under which to create this new Azure Managed Redis instance.
   Resource group	Drop down and select a resource group, or select Create new and enter a new resource group name.	Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together.
   Name	Enter a name that is unique in the region.	The cache name must be a string between 1 and 63 characters when combined with the cache's region name that contain only numbers, letters, or hyphens. (If the cache name is fewer than 45 characters long it should work in all currently available regions.) The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's host name is \<DNS name\>.\<Azure region\>.redis.chinacloudapi.cn.
   Region	Drop down and select a location.	Azure Managed Redis is available in selected Azure regions.
   Data tier	Select either In-memory for high-performance, or Flash for lower performance caches	The in-memory tiers include Balanced, Memory Optimized, and Compute Optimized. Use the Flash tier to use in-memory (RAM) and on-disk (SSD) data storage.
   Cache Size	Drop down and select a size.	Cache size depends on tier. The smallest size is a Balanced tier. The size largest in-memory tier is a Memory Optimized tier.
   Performance	Drop down and select a performance preference.	Performance depends on the number of vCPUs. Number of vCPU varies with tier. Compute Optimized has the most vCPUs.

   For guidance on choosing the right performance tier, see Choosing the right tier.

   Important

   All in-memory tiers that use over 120 GB of storage are in Public Preview, including Memory Optimized M150 and higher; Balanced B150 and higher; and Compute Optimized X150 and higher. All these tiers and higher are in Public Preview.

   All Flash Optimized tiers are in Public Preview.

4. Select Next: Networking , and select either a Public Endpoint or Private Endpoint.

5. Select Next: Active geo-replication. To use active geo-replication it must be enabled during provisioning. Caches without active geo-replication can't be added to or join active geo-replication groups later. For more information, see Configure active geo-replication for Azure Managed Redis instances.

6. Select the Next: Advanced tab.

   Configure any Redis modules you want to add to the instance.

   By default, for a new managed cache:

   • Microsoft Entra ID is enabled.
   • Access Keys Authentication is disabled for security reasons.

   Important

   For optimal security, we recommend that you use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization by using Microsoft Entra ID and managed identities provides superior security and ease of use over shared access key authorization. For more information about using managed identities with your cache, see Use Microsoft Entra ID for cache authentication.

   Set Clustering policy:

   • Use Enterprise in order to use RedisSearch or other modules
   • Use OSS for a clustered cache.
   • Use Non-clustered (Preview) for a non-clustered cache.

   For more information on choosing Clustering policy, see Cluster policy.

   Important

   You can't change the clustering policy of an Azure Managed Redis instance after you create it. If you're using RediSearch, the Enterprise cluster policy is required, and NoEviction is the only eviction policy supported.

   Important

   If you're using this cache instance in a geo-replication group, eviction policies cannot be changed after the instance is created. Be sure to know the eviction policies of your primary nodes before you create the cache. For more information on active geo-replication, see Active geo-replication prerequisites.

   Important

   You can't change modules after you create a cache instance. Modules must be enabled at the time you create an Azure Cache for Redis instance. There is no option to enable the configuration of a module after you create a cache.

7. Select Next: Tags and skip.

8. Select Next: Review + create.

9. Review the settings and select Create.

   It takes several minutes for the Redis instance to create. You can monitor progress on the Azure Managed Redis Overview page. When Status shows as Running, the cache is ready to use.

• What is Azure Managed Redis?
• Using Azure Managed Redis with .NET