Skip to content

Commit 98376fc

Browse files
Merge pull request #227024 from bandersmsft/ri-exchange-policy-change
MCM - Adding RI exchange policy change article
2 parents 2c7f66d + d307084 commit 98376fc

File tree

7 files changed

+62
-7
lines changed

7 files changed

+62
-7
lines changed

articles/cost-management-billing/reservations/exchange-and-refund-azure-reservations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: cost-management-billing
77
ms.subservice: reservations
88
ms.custom: ignite-2022
99
ms.topic: how-to
10-
ms.date: 01/27/2023
10+
ms.date: 02/10/2023
1111
ms.author: banders
1212
---
1313

@@ -20,9 +20,9 @@ However, you can't exchange dissimilar reservations. For example, you can't exch
2020
You can also exchange a reservation to purchase another reservation of a similar type in a different region. For example, you can exchange a reservation that's in West US 2 region for one that's in West Europe region.
2121

2222
> [!NOTE]
23-
> Exchanges will be unavailable for Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations **purchased on or after January 1, 2024**. Microsoft launched Azure savings plan for compute and it's designed to help you save broadly on predictable compute usage. The savings plan provides more flexibility needed to accommodate changes such as virtual machine series and regions. With savings plan providing the flexibility automatically, we’re adjusting our reservations exchange policy. You can continue to exchange VM sizes (with instance size flexibility) but we'll no longer support exchanging instance series or regions for these Azure reserved instances. Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations purchased **prior to January 1, 2024** will reserve the right to **exchange one more time** after the policy change goes into effect.
23+
> Exchanges will be unavailable for all compute reservations - Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations - purchased on or after **January 1, 2024**. Compute reservations purchased **prior to January 1, 2024** will reserve the right to **exchange one more time** after the policy change goes into effect. Microsoft launched Azure savings plan for compute and it's designed to help you save broadly on predictable compute usage. The savings plan provides more flexibility needed to accommodate changes such as virtual machine series and regions. With savings plan providing the flexibility automatically, we’re adjusting our reservations exchange policy. You can continue to exchange VM sizes (with instance size flexibility) but we'll no longer support exchanging instance series or regions for these compute reservations. For more information about the exchange policy change, see [Changes to the Azure reservation exchange policy](reservation-exchange-policy-changes.md).
2424
>
25-
> For a limited time you may [trade-in](../savings-plan/reservation-trade-in.md) your Azure reserved instances for compute for a savings plan. Or, you may continue to use and purchase reservations for those predictable, stable workloads where you know the specific configuration you’ll need and want additional savings. Learn more about [Azure savings plan for compute](../savings-plan/index.yml) and how it works with reservations.
25+
> For a limited time you may [trade-in](../savings-plan/reservation-trade-in.md) your Azure compute reservations for a savings plan. Or, you may continue to use and purchase reservations for those predictable, stable workloads where you know the specific configuration you’ll need and want additional savings. Learn more about [Azure savings plan for compute](../savings-plan/index.yml) and how it works with reservations.
2626
2727
When you exchange a reservation, you can change your term from one-year to three-year.
2828

articles/cost-management-billing/reservations/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,8 @@ landingContent:
6363
url: manage-reserved-vm-instance.md
6464
- text: Exchange and refund reservations
6565
url: exchange-and-refund-azure-reservations.md
66+
- text: Changes to the reservation exchange policy
67+
url: reservation-exchange-policy-changes.md
6668

6769
# Card (optional)
6870
- title: Report costs after purchase
Loading
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Changes to the Azure reservation exchange policy
3+
description: Learn how changes to the Azure reservation exchange policy might affect you.
4+
author: bandersmsft
5+
ms.author: banders
6+
ms.reviewer: nitinarora
7+
ms.service: cost-management-billing
8+
ms.subservice: reservations
9+
ms.topic: conceptual
10+
ms.date: 02/14/2023
11+
---
12+
13+
# Changes to the Azure reservation exchange policy
14+
15+
Exchanges will be unavailable for all compute reservations - Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations - purchased on or after **January 1, 2024**. Compute reservations purchased **prior to January 1, 2024** will reserve the right to **exchange one more time** after the policy change goes into effect.
16+
17+
Microsoft launched Azure savings plan for compute and it's designed to help you save broadly on predictable compute usage. The savings plan provides more flexibility needed to accommodate changes such as virtual machine series and regions. With savings plans providing the flexibility automatically, we’re adjusting our reservations exchange policy.
18+
19+
You can continue to exchange VM sizes (with instance size flexibility). However, Microsoft is ending exchanges for regions and instance series for these Azure compute reservations.
20+
21+
The current cancellation policy for reserved instances isn't changing. The total canceled commitment can't exceed 50,000 USD in a 12-month rolling window for a billing profile or single enrollment.
22+
23+
You may [trade in](../savings-plan/reservation-trade-in.md) your Azure reserved instances for compute for a savings plan. You can continue to use and purchase reservations for those predictable, stable workloads where you know the specific configuration and need or want more savings.
24+
25+
Learn more about [Azure savings plan for compute](../savings-plan/index.yml) and how it works with reservations.
26+
27+
:::image type="content" source="./media/reservation-exchange-policy-changes/exchange-timeline-diagram.png" alt-text="Diagram showing the exchange policy timeline." border="false" lightbox="./media/reservation-exchange-policy-changes/exchange-timeline-diagram.png":::
28+
29+
## Example scenarios
30+
31+
The following examples describe scenarios that might represent your situation.
32+
33+
### Scenario 1
34+
35+
You purchase a one-year compute reservation between October 2022 and January 2024. The compute reservation can be exchanged one more time through the end of its term, even after January 2024. Before January 2024, you can exchange it under current policy. However, when the reservation is exchanged after January 2024, the reservation is no longer exchangeable because exchanges are processed as a cancellation and new purchase. You can still trade in the reservation for a savings plan.
36+
37+
### Scenario 2
38+
39+
You purchase a three-year compute reservation before January 2024. You exchange the compute reservation after January 2024. Because an exchange is processed as a cancellation and new purchase, the reservation is no longer exchangeable. However, you can still trade in the reservation for a savings plan.
40+
41+
### Scenario 3
42+
43+
You purchase a one-year compute reservation after January 2024. It can’t be exchanged. However, you can trade in the reservation for a savings plan.
44+
45+
### Scenario 4
46+
47+
You purchase a three-year compute reservation after January 2024. It can’t be exchanged. However, you can trade in the reservation for a savings plan.
48+
49+
## Next steps
50+
51+
- Learn more about [Self-service exchanges and refunds for Azure Reservations](exchange-and-refund-azure-reservations.md).
52+
- Learn more about [Self-service trade-in for Azure savings plans](../savings-plan/reservation-trade-in.md).

articles/cost-management-billing/reservations/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,6 +150,8 @@
150150
items:
151151
- name: Exchange and refund reservations
152152
href: exchange-and-refund-azure-reservations.md
153+
- name: Changes to the reservation exchange policy
154+
href: reservation-exchange-policy-changes.md
153155
- name: Renew reservations
154156
items:
155157
- name: Renew a reservation

articles/cost-management-billing/savings-plan/discount-application.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,9 @@ The benefit is first applied to the product that has the greatest savings plan d
2222

2323
A savings plan discount only applies to resources associated with Enterprise Agreement, Microsoft Partner Agreement, and Microsoft Customer Agreements. Resources that run in a subscription with other offer types don't receive the discount.
2424

25-
## Savings plans and VM reserved instances
25+
## Savings plans and VM reservations
2626

27-
If you have both dynamic and stable workloads, you likely will have both Azure savings plans and VM reserved instances. Since reservation benefits are more restrictive than savings plans, and usually have greater discounts, Azure applies reservation benefits first.
27+
If you have both dynamic and stable workloads, you likely will have both Azure savings plans and VM reservations. Since reservation benefits are more restrictive than savings plans, and usually have greater discounts, Azure applies reservation benefits first.
2828

2929
For example, VM *X* has the highest savings plan discount of all savings plan-eligible resources you used in a particular hour. If you have an available VM reservation that's compatible with *X*, the reservation is consumed instead of the savings plan. The approach reduces the possibility of waste and it ensures that you’re always getting the best benefit.
3030

articles/cost-management-billing/savings-plan/reservation-trade-in.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,7 @@ The following reservations aren't eligible to be traded in for savings plans:
2828
- SUSE Linux plans
2929

3030
> [!NOTE]
31-
> Exchanges will be unavailable for Azure reserved instances for compute services purchased on or after **January 1, 2024**. Azure savings plan for compute is designed to help you save broadly on predictable compute usage. The savings plan provides more flexibility needed to accommodate changes such as virtual machine series and regions. With savings plan providing the flexibility automatically, we’re adjusting our reservations exchange policy. You can continue to exchange VM sizes (with instance size flexibility) but we'll no longer support exchanging instance series or regions for Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations. For a limited time you may trade-in your Azure reserved instances for compute for a savings plan. Or, you may continue to use and purchase reservations for those predictable, stable workloads where you know the specific configuration you’ll need and want additional savings. For more information, see [Self-service exchanges and refunds for Azure Reservations](../reservations/exchange-and-refund-azure-reservations.md).
32-
31+
> Exchanges will be unavailable for all compute reservations - Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations - purchased on or after **January 1, 2024**. Compute reservations purchased **prior to January 1, 2024** will reserve the right to **exchange one more time** after the policy change goes into effect. Azure savings plan for compute is designed to help you save broadly on predictable compute usage. The savings plan provides more flexibility needed to accommodate changes such as virtual machine series and regions. With savings plan providing the flexibility automatically, we’re adjusting our reservations exchange policy. You can continue to exchange VM sizes (with instance size flexibility) but we'll no longer support exchanging instance series or regions for Azure Reserved Virtual Machine Instances, Azure Dedicated Host reservations, and Azure App Services reservations. For a limited time you may trade-in your Azure compute reservations for a savings plan. Or, you may continue to use and purchase reservations for those predictable, stable workloads where you know the specific configuration you’ll need and want additional savings. For more information, see [Self-service exchanges and refunds for Azure Reservations](../reservations/exchange-and-refund-azure-reservations.md).
3332
3433
- You must have owner access on the Reservation Order to trade in an existing reservation. You can [Add or change users who can manage a savings plan](manage-savings-plan.md#who-can-manage-a-savings-plan).
3534
- Microsoft isn't currently charging early termination fees for reservation trade ins. We might charge the fees made in the future. We currently don't have a date for enabling the fee.

0 commit comments

Comments
 (0)