When a Savings Plan expires, the usage it covered goes back to On-Demand rates unless another commitment picks it up; in Azure, usage after a reservation or savings plan expires is charged at pay-as-you-go rates. Nothing is switched off; the bill simply rises. Start 90 days ahead and you decide on renewal, resizing or a deliberate lapse with data rather than under time pressure.

What happens at expiry, and what renews by itself

Defaults differ by provider and purchase channel:

CommitmentRenews without actionWhat a renewal buys
AWS Savings PlanNo"Renew Savings Plan" queues a purchase with the same configuration at the current rate, starting one second after expiry; the commitment amount can be changed in the cart
AWS Reserved Instance (EC2)No"Renew Reserved Instances" queues a purchase with the same configuration; regional RIs only, up to three years ahead
Azure reservationYes, on by default at purchaseA new reservation with the same SKU, region, scope, term and quantity; quantity, billing frequency and term can be changed
Azure savings plan, bought in the portalNo, off by defaultA new plan with the same term, billing frequency and hourly commitment; all three can be changed
Azure savings plan, bought through Partner CenterYes, on by default at purchaseAs in the portal

Two consequences. An Azure reservation is bought again for a full new term without review unless someone changes the setting. And an expired Azure commitment cannot be renewed after the fact; you can only buy a new one. The new reservation created by a renewal has auto-renew switched off.

Azure reservations and PartnerCenter savings plans, on by defaultAWS always; Azure savingsplans bought in the portalThe commitment reaches its end dateAuto-renew on?Bought again for a full new termwithout review; the new reservationhas auto-renew offCovered usage back at On-Demand orpay-as-you-go rates; in AWS a queuedpurchase replaces it, in Azure only a newpurchase, never a renewal after the fact
What the end date does: nothing switches off, the covered usage goes back to on-demand or pay-as-you-go rates, and only Azure's auto-renew buys again by itself, for a full term and without review

Where to find expiry dates

CommitmentConsoleField or command
AWS Savings PlansBilling and Cost Management, Savings Plans, Inventoryaws savingsplans describe-savings-plans --states active returns end; in CUR 2.0, savings_plan_end_time
AWS reservationsBilling and Cost Management, Reservations, Overview (shows those expiring this month); EC2 console, Reserved Instancesaws ec2 describe-reserved-instances --filters Name=state,Values=active returns End; in CUR 2.0, reservation_end_time
Azure reservationsAzure portal, ReservationsCost details carry ReservationId, ReservationName and PricingModel = Reservation, but no expiry date
Azure savings plansAzure portal, Savings plansCost details carry BenefitId, BenefitName and PricingModel = SavingsPlan

For Azure, keep the expiry date in your own list taken from the portal, with an owner and the renewal setting.

Setting up notifications

  • AWS Savings Plans: under Savings Plans, Overview, Manage alert subscriptions, choose alerts 1, 7, 30 or 60 days before expiry; AWS also alerts on the expiry date and on queued purchases, to up to 10 recipients.
  • AWS reservations: under Reservations, Overview, Manage alert subscriptions, choose 7, 30 or 60 days ahead and the expiry date, to up to 10 recipients, for EC2, RDS, Redshift, ElastiCache and OpenSearch Service.
  • Azure reservations: emails 30 days before expiry for terms of a year or more, 5 days before for shorter terms, and on the expiry date. Recipients depend on the purchase channel: under an EA the notification contacts, EA admin, reservation owners and reservation administrator; under an MCA the reservation owners and administrator; under CSP the partner's notification contact.
  • Azure savings plans: emails 30 days before and on the expiry date; currently none for Microsoft Partner Agreement subscriptions.

Use a distribution list, not a person. Thirty days' notice is too short for a 90-day review, so set the date from your own list.

What may have changed since you bought

Check today's terms before each renewal, not the ones from the last purchase:

  • Azure exchanges: Microsoft states that reservations bought on or after 1 February 2027 cannot be exchanged if savings plans cover the service, for example Virtual Machines, App Service and SQL Database. Reservations bought before that date keep one final exchange. An automatic renewal after that date buys a new reservation without that right.
  • Azure refunds: cancelled commitments may not exceed USD 50,000 in a rolling 12-month window per billing profile or enrolment. Microsoft currently charges no early termination fee but reserves the right to.
  • Azure savings plans: purchases are final, with no cancellation or exchange. Certain reservations can be traded in for a savings plan.
  • Azure renewal price: it becomes visible 30 days before expiry. If the price changes between locking it and the renewal, the renewal is not processed. Splitting, merging or transferring the reservation also cancels the renewal.
  • AWS corrections: a Savings Plan with an hourly commitment of USD 100 or less can be returned within seven days and in the same calendar month, within a quota. A queued RI purchase can be deleted until its scheduled time; a purchased RI cannot be cancelled.

The 90-60-30-day review

90 days before: gather facts

  1. Name an owner for each commitment; no owner, no renewal.
  2. Analyse covered usage over the last three months: utilisation, unused share, trend.
  3. List architecture changes up to the end of a possible new term: instance family or region moves, containers, serverless, decommissioning, migration.

60 days before: model the options

  1. Compare variants: same amount, lower amount, another type (for example a Compute Savings Plan instead of an RI, or an Azure savings plan instead of a reservation), one or three years, no, partial or all upfront.
  2. Agree the effect on budget and monthly cost with finance; cloud budget planning for 2027 needs the figure.
  3. Check the licence side at the same time: for Windows and SQL VMs a reservation covers compute only, and whether Azure Hybrid Benefit keeps covering the licence depends on your Software Assurance.

30 days before: decide and act

  1. Approval by the accountable person, with amount, term and payment option.
  2. Act: in AWS, queue the purchase; in Azure, switch auto-renew on or off deliberately, well before the final two days before expiry.
  3. In Azure, check the renewal price, now visible.

After expiry: on the first invoice, check that the new commitment is active, that there was no gap and that nothing overlaps.

90 days before: an owner per commitment,three months of covered usage, plannedarchitecture changes60 days before: variants of amount, type, termand payment, the budget effect agreed with finance,the licence side checked30 days before: approval; the purchase queued in AWS,auto-renew set deliberately in Azure,the renewal price checkedAfter expiry: the first invoice shows the newcommitment active, no gap and no overlap
The review runs on the calendar, not on the provider's 30-day email: facts at 90 days, options at 60, decision and action at 30, and a check on the first invoice after expiry

Query: what depends on the expiry (AWS CUR 2.0)

This Athena query on a CUR 2.0 export shows, for each commitment expiring in the next 90 days, last full month's covered usage at public On-Demand rates and at effective cost:

WITH covered AS (
  SELECT
    IF(line_item_line_item_type = 'SavingsPlanCoveredUsage',
       savings_plan_savings_plan_a_r_n, reservation_reservation_a_r_n) AS commitment_arn,
    IF(line_item_line_item_type = 'SavingsPlanCoveredUsage',
       savings_plan_end_time, reservation_end_time) AS end_time,
    pricing_public_on_demand_cost AS on_demand_cost,
    IF(line_item_line_item_type = 'SavingsPlanCoveredUsage',
       savings_plan_savings_plan_effective_cost, reservation_effective_cost) AS effective_cost
  FROM cur2 -- your Data Exports table name
  WHERE line_item_line_item_type IN ('SavingsPlanCoveredUsage', 'DiscountedUsage')
    AND line_item_usage_start_date >= date_add('month', -1, date_trunc('month', current_timestamp))
    AND line_item_usage_start_date < date_trunc('month', current_timestamp)
)
SELECT commitment_arn, end_time,
       SUM(on_demand_cost) AS on_demand_cost,
       SUM(effective_cost) AS effective_cost
FROM covered
WHERE from_iso8601_timestamp(end_time) <= current_timestamp + INTERVAL '90' DAY
GROUP BY commitment_arn, end_time
ORDER BY end_time

The difference between the two sums roughly shows how much monthly cost rises without a replacement. If you have privately negotiated prices, your actual On-Demand rate differs from the public one. For Azure, the utilisation view under Reservations gives the equivalent starting point; in cost details, ChargeType = UnusedReservation marks the unused share.

Renewal decision table

Finding from the reviewDecision
Usage stable, no change plannedRenew; reassess term and payment option
Part of the commitment went unusedRenew at a lower amount or quantity
Instance family or region changes during a new termChoose a more flexible type or a shorter term
Workload retired before a new term would endLet it lapse and budget On-Demand cost until then
Usage has grownRenew the existing commitment; decide extra capacity as a separate purchase
Azure VM, App Service or SQL reservation renewing on or after 1 February 2027Model a savings plan as the alternative, because exchanges end
No owner or no data 30 days beforeEscalate to management; do not renew silently

Where Costfluent helps

Costfluent reads cost data from AWS, Azure and Google Cloud through read-only connectors. Cost reports show amortised cost by service and account, and cost insights show unusual changes. Budget alert notifications are Planned. A renewal decision can be recorded as a savings opportunity with its estimate and tracked as open, accepted, implemented or rejected; savings verification against actual cost (Custom) is Planned, as is commitment coverage analysis. Costfluent does not buy, renew or cancel commitments. See savings; the monthly cloud cost review keeps the commitment calendar.

Sources and method

Checked on 2026-10-10. AWS: Managing your Savings Plans alerts, AWS: Renewing a Savings Plan, AWS: Returning a purchased Savings Plan, AWS CLI: describe-savings-plans, AWS: Understanding reservations in Cost Explorer, AWS: Buy Reserved Instances (queue, renew), AWS Data Exports Savings Plan columns, reservation columns, line item columns and pricing columns, Microsoft Learn: automatically renew Azure reservations, Microsoft Learn: automatically renew your savings plan, Microsoft Learn: savings plans in Partner Center, Microsoft Learn: exchanges and refunds for Azure reservations, Microsoft Learn: savings plan cancellation policies, Microsoft Learn: cost details fields. The review plan, query and decision table are Costfluent recommendations. Provider terms change; recheck them before every purchase.