Premium Azure Cache for Redis instances in production with no reservation
What does ZopNight detect here?
ZopNight flags a Premium tier Azure Cache for Redis instance that is marked as production, has never been stopped, and shows average CPU or memory use of 30% or more across at least 60 days, but is still billed at pay-as-you-go rates. Basic and Standard caches are skipped because Microsoft sells no reservations for those tiers.
Signal and threshold
| Field | Value |
|---|---|
| Rule IDs | RC-1339 |
| Category | discount |
| Severity | low |
| Metric | cache CPU, used memory percentage |
| Threshold | Premium tier, 60+ days history, 70%+ uptime, 30%+ CPU or memory |
| Evaluation window | 30d |
| Source | ZopNight |
| Permissions used | Microsoft.Cache/redis/read · Microsoft.Insights/Metrics/Read · Microsoft.Capacity/reservationorders/read |
Where it applies
Which Redis tiers can be reserved at all
Azure Cache for Redis reservations prepay compute for one or three years in exchange for a discount. Microsoft’s support table is short: Basic and Standard, no; Premium, yes; Enterprise and Enterprise Flash, yes. Reservations are sold per node, and a Premium cache has two nodes by default, so one cache takes two reservation units. The discount does not cover networking or storage.
Existing and new caches pick up the reservation automatically up to the reserved size, so there is no migration step. The same page also carries Microsoft’s notice that Azure Cache for Redis has announced a retirement timeline for all SKUs, with Azure Managed Redis as the destination. Weigh that before choosing a three-year term.
Finding Premium caches
az redis list \ --query "[?sku.name=='Premium'].{name:name, rg:resourceGroup, size:sku.capacity, location:location}" \ -o tableDaily CPU and memory for a candidate over the past month:
az monitor metrics list --resource <cache-resource-id> \ --metric percentProcessorTime usedmemorypercentage --offset 30d --interval PT24H --aggregation AverageExisting reservations are listed under Reservations in the portal. A cache already covered there is not a candidate.
The checks a cache must pass
- The name contains
prod,production,prdorlive, or an environment tag marks it as production. - ZopNight has never recorded the cache being stopped.
- The tier is Premium. Only classic Azure Cache for Redis is in scope, so Premium is the one reservable tier this check sees.
- No reservation or savings plan covers it and it has no
reserved=truetag. - At least 60 days of history, uptime of at least 70%, and cache CPU or used memory percentage averaging at least 30%.
Caches that are passed over
Basic and Standard caches, and caches whose tier cannot be read, are skipped rather than sent a recommendation for a reservation they cannot buy. A cache missing any of the utilization or history signals is also skipped. If the break-even comparison below shows the reservation costing more than the cache does today, there is no finding.
Break-even pricing for a cache
ZopNight prefers a break-even figure over a flat discount:
current month = what the cache is billed now, for the hours it actually ranreserved month = 1-year reserved hourly rate x 730saving = current month - reserved month (only when positive)When those rates are not available it falls back to the current cost multiplied by a discount derived from the rate tiers, and only if uptime is still high enough.
Reserving the cache
- Confirm the cache stays in service, at this size, for the full term, and check the retirement timeline against a three-year purchase.
- In the portal, open Reservations, select Add and Azure Cache for Redis.
- Pick the region, the Premium tier size and the term, and buy one unit per node.
- Recheck the cache’s cost after the next billing day to confirm the reservation applied.