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/microsoft-customer-agreement/onboard-microsoft-customer-agreement.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,9 +211,9 @@ This section of the onboarding guide describes the steps you follow to migrate f
211
211
### Changes after migration
212
212
213
213
- 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.
214
-
- Reservations - When there's a currency change during or after an enrollment transfer, reservations paid for monthly are cancelled 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.
214
+
- 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.
215
215
- Savings Plans - If they were purchased in a non-USD currency, they get canceled during migration. You can repurchase them after migration.
216
-
-API's – If used, you need to migrate to using replacement APIs. For more information, see [Migrate from Enterprise Agreement to Microsoft Customer Agreement APIs](../costs/migrate-cost-management-api.md).
216
+
-APIs – If used, you need to migrate to using replacement APIs. For more information, see [Migrate from Enterprise Agreement to Microsoft Customer Agreement APIs](../costs/migrate-cost-management-api.md).
217
217
- Automatic purchases - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
218
218
- Management groups – Subscriptions in management groups under a Microsoft Customer Agreement aren’t supported in Cost Management yet. Cost Management + Billing is managed with APIs and Azure portal functionality.
219
219
@@ -229,7 +229,7 @@ Here are some points to consider after migration.
| Multi-tenancy | - Multiple enrollments. <br>- Sharing MACCand ACD across multiple enrollments is complex. | - A single MCA support multiple tenants. <br>- Associate multiple tenants to a billing account in the primary tenant. <br>- Provide access to MCA for users in associated tenants without guesting users into the primary tenant. <br>- MACC and ACD can be shared. |
232
+
| Multi-tenancy | - Multiple enrollments. <br>- Sharing Microsoft Azure Consumption Commitment (MACC) benefit and Azure Consumption Discount (ACD) across multiple enrollments is complex. | - A single MCA supports multiple tenants. <br>- Associate multiple tenants to a billing account in the primary tenant. <br>- Provide access to MCA for users in associated tenants without guesting users into the primary tenant. <br>- MACC and ACD can be shared. |
233
233
| Historical charges | Cost data stays under your EA enrollment billing scope. | MCA scope shows cost data starting from the migration date. |
234
234
| EA accounts | They’re supported by your EA. | - Not supported in MCA. <br>- The account’s subscriptions belong to the invoice section created for their respective departments. <br>- Account owners become Azure subscription creators. They can create and manage subscriptions for their invoice sections. |
235
235
| Marketplace | Marketplace offers can be purchased with an EA | - Marketplace offers can be purchased with an MCA. <br>- Invoices can be configured to show Marketplace purchases on the same invoice with Azure or on a separate invoice. |
@@ -246,8 +246,8 @@ For more information, see the following articles:
246
246
The following points help you plan for your migration from EA to MCA:
247
247
248
248
- Migrating from EA to MCA redirects your charges from your EA enrollment to your MCA billing account after you complete the subscription migration. The change goes into effect immediately. Any charges incurred up to the point of migration are invoiced to the EA and must be settled on that enrollment. There's no effect on your services and no downtime.
249
-
- You can continue to see your historic charges in the Azure portal under your EA enrollment billing scope. Historical charges are visible in cost analysis when migration completes if you are an Account Owner or Enterprise Administrator for the enrollment.
250
-
- Subscription ownership does not provide access to historical data since there is no access to the EA Billing Scope. We recommend that you [download your cost and usage data and invoices](../understand/download-azure-daily-usage.md) before you transfer subscriptions.
249
+
- You can continue to see your historic charges in the Azure portal under your EA enrollment billing scope. Historical charges are visible in cost analysis when migration completes if you're an Account Owner or Enterprise Administrator for the enrollment.
250
+
- Subscription ownership doesn't provide access to historical data since there's no access to the EA Billing Scope. We recommend that you [download your cost and usage data and invoices](../understand/download-azure-daily-usage.md) before you transfer subscriptions.
251
251
- Depending on the timing of your migration, you might receive two invoices, one EA and one MCA, in the transition month. The MCA invoice covers usage for a calendar month and is generated from the fifth to the seventh day of the month following the usage.
252
252
- To ensure your MCA invoice gets received by the right person or group, you must add an accounts payable email address as an invoice recipient's contact to the MCA. For more information, see [share your billing profiles invoice](../understand/download-azure-invoice.md#share-your-billing-profiles-invoice).
253
253
- If you use Cost Management APIs for reporting purposes, familiarize yourself with [Other actions to manage your MCA](#other-actions-to-manage-your-mca).
0 commit comments