Merge pull request #303939 from hinallur/mcasetupRIASP

clarification regarding RI and ASP behavior after migration

Author: prmerger-automator[bot]

articles/cost-management-billing/manage/mca-setup-account.md

@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 05/22/2025
+ms.date: 08/06/2025
 ms.author: jkinma
 ---
 
@@ -239,7 +239,7 @@ Access to Azure resources that was set using Azure role-based access control (Az
 
 ### Azure reservations and savings plans
 
-Any Azure reservations and savings plan in your Enterprise Agreement enrollment are moved to your new billing account. During the transition, there are no changes to the reservation discounts that are being applied to your subscriptions. If you have a savings plan that's getting transferred and it was purchased in USD, there are no changes to the saving plan discounts.
+Any Azure reservations and savings plan in your Enterprise Agreement enrollment are moved to your new billing account. During the transition, there are no changes to the reservation discounts that are being applied to your subscriptions. If you have a savings plan that's getting transferred and it was purchased in USD, there are no changes to the saving plan discounts. For more details, refer to the **Changes after migration** section below. 
 
 ### Savings plan transfers with a non-USD billing currency
 
@@ -262,7 +262,16 @@ Close the Exchange savings plan page and then select the **I have viewed and agr
 
 ### Azure Marketplace products
 
-Any Azure Marketplace consumption-based products in your Enterprise agreement enrollment are moved along with the subscriptions. There are no changes to the service access of the Marketplace products during the transition. Purchases continue to remain in the source agreement.
+When you transfer a subscription from an Enterprise Agreement to a Microsoft Customer Agreement, Marketplace purchases transfer with it when the following conditions are met: 
+
+- The Marketplace purchase in the EA subscription must be active. 
+
+- The Marketplace purchase must pass all eligibility checks before transfer. For example, the purchase must be available for use in the target agreement. 
+    - Marketplace private offer purchased under EA in Netherland cannot be transferred to the MCA-E billing account in US, as the eligibility check fails for this scenario. 
+
+- All other assets in the source subscription must also be able to successfully be transferred. Otherwise, the transfer fails. 
+
+- Please note Marketplace purchased through AppSource is not associated with any subscription, and cannot be transferred with this method. 
 
 ### Support plan
 
@@ -400,7 +409,7 @@ Enterprise administrators and department administrators are listed as invoice se
 - Cost Management using third-party providers like Cloud health and Cloud easier - Organizations transitioning to MCA need to update their provider that they're transitioning to MCA. Most of them have a documented process to pull the MCA cost data.
 - Historical data – It isn’t available to account owners or users with the Subscription owner Azure role-based access control (RBAC) role after migration. Access for existing users, groups, or service principals that was assigned using [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md) isn't affected during the transition.
     - Cost data transition - Cost data before the transition remains in the EA scope. It doesn't move to the MCA scope. You can access the data by switching scopes.
-- Reservations - When there's a currency change during or after an enrollment transfer, reservations paid for monthly are canceled for the source enrollment. Cancellation happens at the time of the next monthly payment for an individual reservation. The cancellation is intentional and only affects monthly reservation purchases. You can repurchase them after migration.
+- Reservations - When there's a currency change during or after an enrollment transfer, reservations paid for monthly are canceled for the source enrollment. Cancellation happens at the time of the next monthly payment for an individual reservation. The cancellation is intentional and only affects monthly reservation purchases. You can repurchase them after migration. **Reservations cancellations triggered by this migration do not count toward the cancellation threshold of USD 50,000 within a rolling 12-month window**. For the cancellation policy, please refer to [Self-service exchanges and refunds for Azure Reservations](../reservations/exchange-and-refund-azure-reservations.md) 
 - Savings Plans - If they were purchased in a non-USD currency, they get canceled during migration. You can repurchase them after migration.
 - API changes - API endpoints differ between EA and MCA. Existing EA API calls don't work with MCA. You need to use Microsoft Cost Management APIs instead if using consumption APIs. For more information, see:
     - [Migrate EA to Microsoft Customer Agreement APIs](../costs/migrate-cost-management-api.md)