A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.
Hello KRISHNA, AMAL,
There is no evidence that Microsoft increased the price of Azure Managed Redis on January 1.
If price didn’t change, why did your cost triple?
This is the important part. Even with no pricing change, Redis cost can jump due to billing‑related factors, not infrastructure changes.
Here are the most common reasons that match your symptoms:
A) You may have been billed at the wrong meter before Dec 31
If your cache was newly deployed (AMR launched GA in May 2025), Azure sometimes initially bills:
- Only the primary node
- HA replica not metered yet
- Lower tier meter applied before final SKU assignment
Your graph shows:
Flat stable cost → sudden permanent increase → static afterward This strongly resembles a billing correction event.
HA Replica charges started applying on Jan 1
You stated your instance is B3 Balanced with HA. Azure Managed Redis charges per node, and HA = 2 nodes.
If until Dec 31 only the primary node was billed, and starting Jan 1 both primary + replica were billed, the daily cost would jump ≈2×, and with some internal meter adjustments may appear closer to 3× depending on region taxes.
Regional meter realignment (NE + EU‑W)
You confirmed both North Europe and West Europe clusters show the same behavior.
When the same pattern appears in multiple regions, the issue is almost always:
- Metering correction rolled out globally on the same date
- Not related to your application load (you have zero traffic)
This again matches a billing fix, not a price increase.
Pricing currency conversion change (YEN)
Azure bills in local currency based on:
- Daily FX rate
- Currency update intervals (monthly/quarterly depending on region)
If Microsoft updated the JPY exchange rate for Yen-based billing, your cost per day could jump without SKU price changing at all.
This is often invisible in the portal unless you check the "Effective Price" inside Cost Analysis.
Your graph indicates a billing correction event, not usage or pricing change
Your uploaded chart shows:
- A stable 600 JPY/day through all of December
- Immediately on Jan 1, a flat increase to 1500 JPY/day
- No daily variation (rules out usage)
This pattern is characteristic of SKU meter correction.
What you should do next (recommended escalation path)
Because there is no documented price increase, and symptoms match a meter correction, you should open a Billing Support Ticket.
Correct support category
Since “Azure Managed Redis” may not appear in dropdowns, use:
Azure → Billing → Cost Analysis / Unexpected Charges
Billing support is free, even without a support plan.
🔹 Information to include
Provide:
- Subscription ID
- Resource ID of Redis instance
- Your graph
- Date cost increased (Jan 1, 2026)
- Mention: “Possible metering correction / replica billing suddenly applied”
Azure Billing can check whether HA replica meters started being billed or if a currency FX adjustment was applied.
Let me if you need assistance in creating support ticket for billing, if yes share your email and availability with timezone for discussion?