On this page
Azure Managed Redis is billed per node-hour by SKU. In East US on 14 November 2026, a 24 GB Memory Optimized node lists at $0.431 an hour, and a production instance runs two nodes. Azure reserves about 20% of memory, so 10 GB of data needs a 24 GB SKU.
Prices checked 14 November 2026. They are USD list prices for East US from Microsoft's price feed, excluding taxes, discounts, private endpoints and data transfer. Hourly prices are Microsoft's published per-node rates. Monthly figures are our estimates, calculated from those rates: for Memory Optimized, Balanced and Compute Optimized, the hourly rate x 2 nodes (a high availability, or HA, instance) x 730 hours. Confirm your region and agreement in the Azure pricing calculator.
Azure Managed Redis tiers and list prices
Four tiers share one price list shape: Memory Optimized, Balanced, Compute Optimized and Flash Optimized. The first three keep data in memory and differ in how many vCPUs each gigabyte gets. Flash Optimized puts cold values on NVMe storage.
| Tier | Memory to vCPU | Sizes | Built for |
|---|---|---|---|
| Memory Optimized | 8:1 | 12 GB to 1,920 GB | Large caches and dev or test where throughput matters less |
| Balanced | 4:1 | 0.5 GB to 960 GB | Standard workloads; Microsoft's suggested starting point |
| Compute Optimized | 2:1 | 3 GB to 720 GB | Maximum throughput and latency-sensitive services |
| Flash Optimized | RAM plus NVMe | 250 GB to 4,500 GB | Large datasets with a hot subset; sizes marked preview on the pricing page |
In-memory sizes from 360 GB up are also marked preview on the pricing page. Here is what the common production sizes cost, per node-hour (Microsoft's published rate) and per month for an HA pair (our estimate: hourly rate x 2 nodes x 730 hours):
| Size | Memory Optimized | Balanced | Compute Optimized |
|---|---|---|---|
| 12 GB | M10: $0.216 per hour, $315 a month | B10: $0.315, $460 | X10: $0.583, $851 |
| 24 GB | M20: $0.431, $629 | B20: $0.629, $918 | X20: $1.166, $1,702 |
| 60 GB | M50: $0.862, $1,259 | B50: $1.257, $1,835 | X50: $2.331, $3,403 |
| 120 GB | M100: $1.724, $2,517 | B100: $2.496, $3,644 | X100: $4.663, $6,808 |
Microsoft also sells one-year and three-year reservations, and a single-node option without HA for development and test only. A non-HA instance has no availability SLA and can lose data during maintenance.
How to size an Azure Managed Redis instance
Size for peak used memory divided by 0.8. Azure reserves about 20% of each instance for replication during failover, geo-replication buffers and other work that is not your data. A 12 GB SKU gives roughly 9.6 GB for keys.
Do not double the number for HA. Microsoft states the SKU memory limit already accounts for replication, even though the Used Memory metric reports primary and replica together. Alert when Used Memory Percentage stays above 75%.
Three worked examples, all from the table above. Monthly figures are our estimates, calculated as above:
| Peak data | Needs at least | SKU size | Balanced HA, per month | Memory Optimized HA, per month |
|---|---|---|---|---|
| 5 GB | 6.25 GB | 12 GB | $460 (B10) | $315 (M10) |
| 10 GB | 12.5 GB | 24 GB | $918 (B20) | $629 (M20) |
| 40 GB | 50 GB | 60 GB | $1,835 (B50) | $1,259 (M50) |
Memory Optimized is the cheaper tier per gigabyte but has the fewest vCPUs, so test throughput before you pick it. Microsoft's docs describe scaling down as limited, so start from measured peaks, not from the old cache label.
What the move from Azure Cache for Redis costs
The SKU is the small part. The work is changing clients and checking features. Microsoft retires the Enterprise and Enterprise Flash tiers on 31 March 2027, and says Enterprise instances are migrated to Azure Managed Redis starting 1 April 2027, while its retirement FAQ says Enterprise caches not upgraded by 31 March 2027 are disabled from 1 April 2027. Plan to migrate yourself before then. Basic, Standard and Premium retire on 30 September 2028 and are disabled from 1 October 2028. Our Azure Cache for Redis retirement dates guide covers both timelines.
Budget engineering time for these differences, all from Microsoft's migration guide:
- The endpoint moves to
<region>.redis.azure.net, and the port is 10000 for TLS and non-TLS. - Only database 0 exists, so apps that use several databases need key prefixes.
- Instances are clustered by default. A non-clustered mode exists up to 25 GB.
- Keyspace notifications are not available yet, and there is no Microsoft Entra ID role-based access control.
- Virtual network injection is gone. Use Azure Private Link.
- A cache runs in TLS or non-TLS mode, not both.
On list price, the move often saves money. For the three Premium sizes below, our estimate puts an HA pair of Balanced nodes about 43% lower. Redis, the vendor, reports the same range in its own 13 November comparison.
| Premium, per month (our estimate: published hourly rate x 730 hours) | Balanced HA, per month (our estimate) |
|---|---|
| P2, 13 GB: $810 | B10, 12 GB: $460 |
| P3, 26 GB: $1,620 | B20, 24 GB: $918 |
| P4, 53 GB: $3,241 | B50, 60 GB: $1,835 |
These pairs are not like for like. Size by peak used memory, and test throughput. A workload that needs Compute Optimized can cost more: a 6 GB Premium P1 is about $405 a month by the same method, against about $425 for a 6 GB X5 pair.
Alternatives: Redis or Valkey in your own Azure subscription
If Azure Managed Redis does not fit, run Redis Open Source or Valkey yourself in Azure. Teams choose this when they need multiple databases, keyspace notifications or virtual network deployment, which Azure Managed Redis does not offer today. See managed Redis providers compared for the wider field, and Redis to Valkey migration if licensing is part of the decision.
Support for Redis on Azure
Microsoft operates Azure Managed Redis. AceMQ supports Redis you run or migrate. Redis support from AceMQ runs $24,000 to $72,000 a year (USD) by SLA, scope and deployment, 24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan. Quote requests get a reply within 1 hour. AceMQ is listed in the Redis partner directory. See 24/7 Redis support, or managed Redis in your own Azure subscription if you want AceMQ to hold the pager.
Sources
- Azure Managed Redis pricing (tiers, sizes, SKUs; prices load by script, so per-node hourly rates come from the price feed below)
- Azure Retail Prices API, East US, Redis Cache service (consumption meters for Azure Managed Redis and Azure Cache for Redis Premium)
- Microsoft Learn: What is Azure Managed Redis? (tiers, ratios, sizes, preview marks, HA and non-HA)
- Microsoft Learn: Azure Managed Redis architecture (about 20% reserved memory; clustering; scaling down)
- Microsoft Learn: memory management best practices (HA does not require a larger SKU; 75% alert)
- Microsoft Learn: migrating from Basic, Standard and Premium, differences (endpoint, port 10000, database 0, keyspace notifications, Private Link, 12 GB SKUs give about 9.6 GB usable)
- Microsoft Tech Community: Azure Cache for Redis retirement, what to know (dates; Enterprise instances migrated starting 1 April 2027; updated 30 July 2026)
- Microsoft Learn: retirement FAQ (Enterprise caches not upgraded by 31 March 2027 are disabled from 1 April 2027; page updated 18 August 2026)
- Redis: moving from Azure Cache for Redis to Azure Managed Redis can cut costs by 40% (vendor view; East US 2 prices, 13 Nov 2026)
Frequently Asked Questions
How much does Azure Managed Redis cost?
Per-node list prices in East US on 14 November 2026 run from $0.016 an hour for the smallest Balanced size (B0) to $27.648 an hour for the largest preview Memory Optimized size, and the common 24 GB sizes list at $0.431 (Memory Optimized), $0.629 (Balanced) and $1.166 (Compute Optimized). A production HA instance bills two nodes.
Is Azure Managed Redis more expensive than Azure Cache for Redis?
For the three Premium sizes we compared, our estimate from list prices was about 43% lower on Balanced nodes. A throughput-heavy workload on Compute Optimized can cost slightly more, as the 6 GB example shows. Compare at your own sizes in the Azure pricing calculator.
How much memory should I buy?
Peak used memory divided by 0.8, rounded up to the next SKU. Azure reserves about 20% of memory, so 10 GB of data needs a SKU of at least 12.5 GB, which in practice means 24 GB.
Can I run Redis on AKS or VMs instead?
Yes. Redis Open Source or Valkey on Azure Kubernetes Service or virtual machines works, and it keeps features Azure Managed Redis lacks, such as multiple databases and keyspace notifications. You then own operations, or hire a team that does it.
Guides, comparisons and research

