You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cost-management-billing/manage/ea-transfers.md
+16-17Lines changed: 16 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.reviewer: sapnakeshari
6
6
ms.service: cost-management-billing
7
7
ms.subservice: enterprise
8
8
ms.topic: conceptual
9
-
ms.date: 03/07/2023
9
+
ms.date: 04/10/2023
10
10
ms.author: banders
11
11
ms.custom: contperf-fy21q1
12
12
---
@@ -17,9 +17,9 @@ This article provides an overview of enterprise transfers.
17
17
18
18
## Transfer an enterprise account to a new enrollment
19
19
20
-
An account transfer moves an account owner from one enrollment to another. All related subscriptions under the account owner will move to the target enrollment. Use an account transfer when you have multiple active enrollments and only want to move selected account owners.
20
+
An account transfer moves an account owner from one enrollment to another. All related subscriptions under the account owner move to the target enrollment. Use an account transfer when you have multiple active enrollments and only want to move selected account owners.
21
21
22
-
This section is for informational purposes only as the action can't be performed by an enterprise administrator. A support request is needed to transfer an enterprise account to a new enrollment.
22
+
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 account to a new enrollment.
23
23
24
24
Keep the following points in mind when you transfer an enterprise account to a new enrollment:
25
25
@@ -44,28 +44,28 @@ Other points to keep in mind before an account transfer:
44
44
- Your account shows the end date corresponding to the effective transfer date on the source enrollment. The same date is the start date on the target enrollment.
45
45
- Your account usage incurred before the effective transfer date remains under the source enrollment.
46
46
47
-
## Transfer enterprise enrollment to a new one
47
+
## Transfer old enrollment to a new enrollment
48
48
49
49
An enrollment transfer is considered when:
50
50
51
51
- A current enrollment's Prepayment term has come to an end.
52
52
- An enrollment is in expired/extended status and a new agreement is negotiated.
53
53
- You have multiple enrollments and want to combine all the accounts and billing under a single enrollment.
54
54
55
-
This section is for informational purposes only as the action can't be performed by an enterprise administrator. 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).
55
+
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).
56
56
57
-
When you request to transfer an entire enterprise enrollment to an enrollment, the following actions occur:
57
+
When you request to transfer an old enterprise enrollment to a new enrollment, the following actions occur:
58
58
59
59
- Usage transferred may take up to 72 hours to be reflected in the new enrollment.
60
-
- If department administrator (DA) or account owner (AO) view charges were enabled on the transferred enrollment, they must be enabled on the new enrollment.
60
+
- If department administrator (DA) or account owner (AO) view charges were enabled on the old transferred enrollment, they must be enabled on the new enrollment.
61
61
- If you're using API reports or Power BI, generate a new API key under your new enrollment.
62
-
-For reporting, all APIs use either the old enrollment or the new one, not both. If you need reporting from APIs for the old and new enrollments, you must create your own reports.
62
+
-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.
63
63
- All Azure services, subscriptions, accounts, departments, and the entire enrollment structure, including all EA department administrators, transfer to a new target enrollment.
64
-
- The enrollment status is set to _Transferred_. The transferred enrollment is available for historic usage reporting purposes only.
65
-
- You can't add roles or subscriptions to a transferred enrollment. Transferred status prevents more usage against the enrollment.
64
+
- 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.
65
+
- You can't add roles or subscriptions to the old enrollment that was transferred. `Transferred` status prevents any new usage against the enrollment.
66
66
- Any remaining Azure Prepayment balance in the agreement is lost, including future terms.
67
-
- If the enrollment you're transferring from has reservation purchases, the historic (past) reservation purchasing fee will remain in the source enrollment. All future purchasing fees transfer to the new enrollment. Additionally, all reservation benefits will be transferred across for use in the new enrollment.
68
-
- 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 will be transferred.
67
+
- 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.
68
+
- 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.
69
69
70
70
### Effective transfer date
71
71
@@ -89,20 +89,19 @@ Other points to keep in mind before an enrollment transfer:
89
89
90
90
- Approval from both target and source enrollment EA Administrators is required.
91
91
- If an enrollment transfer doesn't meet your requirements, consider an account transfer.
92
-
- The source enrollment status will be updated to transferred and will only be available for historic usage reporting purposes.
92
+
- The source enrollment status is updated to `Transferred` and is available for historic usage reporting purposes only.
93
93
- There's no downtime during an enrollment transfer.
94
94
- Usage may take up to 24 - 48 hours to be reflected in the target enrollment.
95
95
- Cost view settings for department administrators or account owners don't carry over.
96
96
- If previously enabled, settings must be enabled for the target enrollment.
97
97
- Any API keys used in the source enrollment must be regenerated for the target enrollment.
98
-
- If the source and destination enrollments are on different cloud instances, the transfer will fail. Support personnel can transfer only within the same cloud instance.
98
+
- If the source and destination enrollments are on different cloud instances, the transfer fails. Support personnel can transfer only within the same cloud instance.
99
99
- For reservations (reserved instances):
100
100
- The enrollment or account transfer between different currencies affects monthly reservation purchases. The following image illustrates the effects.
101
101
:::image type="content" source="./media/ea-transfers/cross-currency-reservation-transfer-effects.png" alt-text="Diagram illustrating the effects of cross currency reservation transfers." border="false" lightbox="./media/ea-transfers/cross-currency-reservation-transfer-effects.png":::
102
-
-Whenever there's is a currency change during or after an enrollment transfer, reservations paid for monthly are canceled for the source enrollment at the time of next monthly payment for an individual reservation. This cancellation is intentional and affects only the monthly reservation purchases.
102
+
-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.
103
103
- You may 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.
104
-
- In case of backdated enrollment transfer, Savings plan benefit is applicable from the transfer request submission date and not from the effective transfer date.
105
-
104
+
- 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.
0 commit comments