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
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,10 @@ This section is for informational purposes only. An enterprise administrator doe
55
55
56
56
When you request to transfer an old enterprise enrollment to a new enrollment, the following actions occur:
57
57
58
-
- Usage transferred might take up to 72 hours to be reflected in the new enrollment.
58
+
- Usage transferred might take up to 72 hours to be reflected in the new enrollment.
59
+
60
+
- Prices for the new enrolment might take at least 72 hours to be reflected in the Price sheet download and the Azure Pricing calculator.
61
+
59
62
- 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.
60
63
- 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).
61
64
- 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.
@@ -90,14 +93,21 @@ Other points to keep in mind before an enrollment transfer:
90
93
- If an enrollment transfer doesn't meet your requirements, consider an account transfer.
91
94
- The source enrollment status is updated to `Transferred` and is available for historic usage reporting purposes only.
92
95
- There's no downtime during an enrollment transfer.
93
-
- Usage might take up to 24 - 48 hours to be reflected in the target enrollment.
96
+
- Usage might take up to 24 - 48 hours to be reflected in the target enrollment.
97
+
94
98
- Cost view settings for department administrators or account owners don't carry over.
95
99
- If previously enabled, settings must be enabled for the target enrollment.
96
-
- Any API keys used in the source enrollment must be regenerated for the target enrollment.
100
+
- 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.
101
+
102
+
- 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.
103
+
104
+
- Anomaly alerts - This feature is supported at subscription scope and hence will be transferred to the new enrolment requiring no further action.
105
+
97
106
- 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).
98
107
- For reservations (reserved instances):
99
108
- The enrollment or account transfer between different currencies affects monthly reservation purchases. The following image illustrates the effects.
100
-
:::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":::
109
+
:::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":::
110
+
101
111
- 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.
102
112
- 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.
103
113
- 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