Merge pull request #245512 from bandersmsft/exchange-policy-chagne

MCM - Update for GH issue 111877

Author: prmerger-automator[bot]

articles/cost-management-billing/reservations/reservation-exchange-policy-changes.md

@@ -7,7 +7,7 @@ ms.reviewer: nitinarora
 ms.service: cost-management-billing
 ms.subservice: reservations
 ms.topic: conceptual
-ms.date: 04/14/2023
+ms.date: 07/19/2023
 ---
 
 # Changes to the Azure reservation exchange policy
@@ -16,6 +16,9 @@ Exchanges will be unavailable for all compute reservations - Azure Reserved Virt
 
 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.
 
+>[!NOTE]
+>Exchanges are changing only for the reservations explicitly mentioned previously. If you have any other type of reservation, then the policy change doesn't affect you. For example, if you have a reservation for Azure VMware Solution, then the policy change doesn't affect it. However, after January 1, 2024, if you exchange a reservation for a type affected by the policy change, the new reservation will be affected by the no-exchange policy.
+
 You can continue to use instance size flexibility for VM sizes, but Microsoft is ending exchanges for regions and instance series for these Azure compute reservations.
 
 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.