Merge pull request #281235 from bandersmsft/ea-transfers

MCM - Update ea-transfers for Pri

Author: prmerger-automator[bot]

articles/cost-management-billing/manage/ea-transfers.md

@@ -6,7 +6,7 @@ ms.reviewer: sapnakeshari
 ms.service: cost-management-billing
 ms.subservice: enterprise
 ms.topic: conceptual
-ms.date: 03/05/2024
+ms.date: 07/15/2024
 ms.author: banders
 ---
 
@@ -22,7 +22,7 @@ This section is for informational purposes only. An enterprise administrator doe
 
 Keep the following points in mind when you transfer an enterprise account to a new enrollment:
 
-- Only the accounts specified in the request are transferred. If all accounts are chosen, then they're all transferred.
+- Only the accounts specified in the request are transferred. If all accounts are chosen, then they all get transferred.
 - The source enrollment keeps its status as active or extended. You can continue using the enrollment until it expires.
 - You can't change account ownership during a transfer. After the account transfer is complete, the current account owner can change account ownership in the Azure portal. Keep in mind that an EA administrator can't change account ownership.
 
@@ -47,27 +47,25 @@ Other points to keep in mind before an account transfer:
 
 An enrollment transfer is considered when:
 
-- A current enrollment's Prepayment term ends.
+- A current enrollment's prepayment term ends.
 - An enrollment is in expired/extended status and a new agreement is negotiated.
 - You have multiple enrollments and want to combine all the accounts and billing under a single enrollment.
 
 This section is for informational purposes only. An enterprise administrator doesn't perform the transfer actions. A support request is needed to transfer an enterprise enrollment to a new one, unless the enrollment qualifies for [Auto enrollment transfer](#auto-enrollment-transfer).
 
 When you request to transfer an old enterprise enrollment to a new enrollment, the following actions occur:
 
-- Usage transferred might take up to 72 hours to be reflected in the new enrollment. 
-
-- Prices for the new enrolment might take at least 72 hours to be reflected in the Price sheet download and the Azure Pricing calculator.  
-
+- Usage transferred might take up to 72 hours to be reflected in the new enrollment.
+- Prices for the new enrollment might take at least 72 hours to be reflected in the Price sheet download and the Azure Pricing calculator.
 - If department administrator (DA) or account owner (AO) view charges were enabled on the previously transferred enrollment, they must be enabled on the new enrollment.
 - If you're using API reports or Power BI, see [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs overview](../automate/migrate-ea-reporting-arm-apis-overview.md).
     - All APIs use either the old enrollment or the new one, not both, for reporting purposes. If you need reports from APIs for the old and new enrollments, you must create your own reports.
 - All Azure services, subscriptions, accounts, departments, and the entire enrollment structure, including all EA department administrators, transfer to a new target enrollment.
 - The enrollment status is set to `Transferred` for the old enrollment. The old enrollment that was transferred is available for historic usage reporting purposes only.
 - You can't add roles or subscriptions to the old enrollment that was transferred. `Transferred` status prevents any new usage against the old enrollment.
 - Any remaining Azure Prepayment balance in the agreement is lost, including future terms.
--    If the old enrollment that you're transferring from has any reservation purchases, the historic (past) reservation purchasing fee remains in the old source enrollment. All future purchasing fees transfer to the new enrollment. Additionally, all reservation benefits are transferred across for use in the new enrollment.
--    The historic marketplace one-time purchase fee and any monthly fixed fees already incurred on the old enrollment aren't transferred to the new enrollment. Consumption-based marketplace charges are transferred.
+- If the old enrollment that you're transferring from has any reservation purchases, the historic (past) reservation purchasing fee remains in the old source enrollment. All future purchasing fees transfer to the new enrollment. Additionally, all reservation benefits are transferred across for use in the new enrollment.
+- The historic marketplace one-time purchase fee and any monthly fixed fees already incurred on the old enrollment aren't transferred to the new enrollment. Consumption-based marketplace charges are transferred.
 
 ### Effective transfer date
 
@@ -93,15 +91,14 @@ Other points to keep in mind before an enrollment transfer:
 - If an enrollment transfer doesn't meet your requirements, consider an account transfer.
 - The source enrollment status is updated to `Transferred` and is available for historic usage reporting purposes only.
 - There's no downtime during an enrollment transfer.
-- Usage might take up to 24 - 48 hours to be reflected in the target enrollment. 
+- Usage might take up to 24 - 48 hours to be reflected in the target enrollment.
 
 - Cost view settings for department administrators or account owners don't carry over.
   - If previously enabled, settings must be enabled for the target enrollment.
-- Exports, Views, Budget alert, Scheduled actions - The existing rules at billing scopes (billing account, enrollment account and department scopes) need to be recreated after the enrolment transfer. All rules at management group, subscription and resource group scopes will be transferred to the new enrolment and no further action will be required.  
+- Exports, views, budget alerts, and scheduled actions - The existing rules at billing scopes (billing account, enrollment account, and department scopes) need to be recreated after the enrollment transfer. All rules at management group, subscription, and resource group scopes get transferred to the new enrollment and no further action is required.
 
-- Reservation utilization alert, Cost allocation rules - These features are supported only at billing account scope and hence they need to be recreated after the enrolment transfer.  
-
-- Anomaly alerts - This feature is supported at subscription scope and hence will be transferred to the new enrolment requiring no further action.    
+- Reservation utilization alert and cost allocation rules - These features are supported only at billing account scope. They need to get recreated after the enrollment transfer.
+- Anomaly alerts - This feature is supported at the subscription scope. They get transferred to the new enrollment requiring no further action.
 
 - If the source and destination enrollments are on different cloud instances, the transfer fails. Support personnel can transfer only within the same cloud instance. Cloud instances are the global Azure cloud and individual national clouds. For more information about national clouds, see [National clouds](../../active-directory/develop/authentication-national-cloud.md).
 - For reservations (reserved instances):
@@ -110,8 +107,7 @@ Other points to keep in mind before an enrollment transfer:
 
   - When there's is 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 next monthly payment for an individual reservation. This cancellation is intentional and affects only the monthly reservation purchases.
   - You might have to repurchase the canceled monthly reservations from the source enrollment using the new enrollment in the local or new currency. If you repurchase a reservation, the purchase term (one or three years) is reset. The repurchase doesn't continue under the previous term.
-- If there's a backdated enrollment transfer, any savings plan benefit is applicable from the transfer request submission date - not from the effective transfer date.
-
+- If there's a backdated enrollment transfer, any reservation or savings plan benefit is applicable from the transfer request submission date - not from the effective transfer date.
 
 ### Auto enrollment transfer