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/checklist-microsoft-customer-agreement-billing-migration.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,30 +24,30 @@ Before migrating from an Enterprise Agreement (EA), Microsoft Customer Agreement
24
24
- Align stakeholders on required actions
25
25
- Top customer actions with MCA. [Learn More](https://www.microsoft.com/licensing/news/top_customer_actions_after_accepting_microsoft_customer_agreement?rtc=1)
26
26
27
-
## Validate Contract and Roles
27
+
## Validate contract and roles
28
28
29
29
Confirm access to both the source and the destination MCA as a Billing Account Owner.
30
30
31
31
- EA → MCA: Ensure EA Admin and MCA Billing Account Owner roles are assigned.
32
32
- PAYG → MCA: Ensure a Global Admin for the PAYG subscription and MCA Billing Account Owner role.
33
33
- MCA → MCA: Confirm Billing Account Owner roles exist in both source and destination MCA billing accounts.[Learn More](https://learn.microsoft.com/azure/cost-management-billing/manage/understand-mca-roles)
34
34
35
-
## No Service Downtime ##
35
+
## No service downtime ##
36
36
37
37
Azure services in your subscription keep running without any interruption. We only transition the billing relationship for your Azure subscriptions. There are no changes to existing resources, resource groups, or management groups.
38
38
39
39
>[!NOTE]
40
40
>Marketplace Private Offers are market specific. Subscriptions that are associated with Marketplace Private Offers may be blocked from transfer during a country/region change. This happens when the Private Offer is published for a specific market and isn't available in the destination market (EA–Sweden to MCA–United States). This mismatch results in a validation failure. Market eligibility for a Private Offer is defined by the ISV at the time of offer publishing and can't be modified after the offer is accepted. To proceed with the subscription transfer to MCA, the existing Private Offer must be canceled and repurchased, if available in the target market.
41
41
42
-
## Download Historical Data
42
+
## Download historical data
43
43
44
44
- Export historical cost and usage data before migration. Historical data doesn't transfer to MCA. We recommend that you save invoices and customer reports for compliance. [View and download Azure usage and charges - Microsoft Cost Management | Microsoft Learn](https://learn.microsoft.com/azure/cost-management-billing/understand/download-azure-daily-usage)
45
45
- You can continue to view historical charges in the Azure portal under the source billing scope, depending on your billing roles:
46
46
- EA → MCA: Historical charges remain visible in Cost Analysis after migration if you're an Enterprise Administrator or Department Administrator on the EA enrollment. Subscription ownership alone doesn't provide access to EA historical charges because subscription roles don't grant access to the EA billing scope.
47
47
- MCA → MCA: Billing Account Owners and Billing Profile Owners/Contributors can continue to view all historical MCA charges in the Azure portal under the source MCA billing scope. Subscription owners without MCA billing roles can't access historical billing data because they don't have permissions to the MCA billing scope.
48
48
- PAYG → MCA: Subscription owners must download all historical invoices and usage data before the transfer, as this information is no longer accessible once the subscription is migrated.
49
49
50
-
## Review Billing Hierarchy Changes
50
+
## Review billing hierarchy changes
51
51
52
52
You use the billing account to manage billing for your Microsoft customer agreement.
@@ -103,7 +103,7 @@ Self-service reservation transfers: Supported when there's no currency change or
103
103
- APIs: Update endpoints to align with MCA's billing structure.
104
104
- Automation: Modify scripts that rely on Management Group-level scoping.
105
105
106
-
## API & Automation Updates
106
+
## API & automation updates
107
107
108
108
Replace legacy APIs with MCA APIs and updated billing properties. APIs & Automation need to be recreated in MCA.
109
109
@@ -116,37 +116,37 @@ Replace legacy APIs with MCA APIs and updated billing properties. APIs & Automat
116
116
>[!NOTE]
117
117
> EA and MCA API schemas differ. [Learn More](https://learn.microsoft.com/azure/cost-management-billing/costs/migrate-cost-management-api#apis-to-get-cost-and-usage)
118
118
119
-
## Technical Dependencies
119
+
## Technical dependencies
120
120
121
121
- After migrating to MCA, note that the transition is an evolutionary process involving both contractual and technical changes. As billing property IDs are updated, ensure all workloads are aligned with the new Billing Account ID, Billing Profile ID, and Invoice Section ID to maintain billing accuracy and business continuity.
122
122
- Check compatibility of dashboards (for example, Emissions Impact Dashboard) and update references to MCA billing scope.
123
123
124
-
## Invoice Setup
124
+
## Invoice setup
125
125
126
126
- Changes in billing constructs
127
127
- Getting started with MCA billing [Learn More](https://learn.microsoft.com/azure/cost-management-billing/understand/mca-overview)
128
128
- Organizing your invoice based on your business needs [Learn More](https://learn.microsoft.com/azure/cost-management-billing/manage/mca-section-invoice#structure-your-account-with-billing-profiles-and-invoice-sections)
129
129
130
-
## Payment Setup
130
+
## Payment setup
131
131
132
132
- MCA remit-to information differs from EA or PAYG. [Learn More](https://learn.microsoft.com/azure/cost-management-billing/understand/pay-bill#wire-bank-details)
133
133
- Notify your accounts payable team.
134
134
- Create separate records for EA and MCA invoices.
135
135
- Expect a final invoice from the source and new monthly MCA invoices.
136
136
- For bank detail verification letters, e invoicing, and third party invoicing requirements, contact your Microsoft Account team.
137
137
138
-
## Tax & Compliance
138
+
## Tax and compliance
139
139
140
140
- Tax exemption certificates: If your account has a tax exemption certificate, create an Azure support request to associate it with your MCA account.
141
141
- Billing profile alignment and currency usage: The billing profile's sold-to and bill-to country/region must correspond to the MCA market country/region.
142
142
143
-
## Support Plan
143
+
## Support plan
144
144
145
145
- Support plans don't transfer to MCA. You need to repurchase a Support Plan on your MCA.
146
146
- Cancel existing plans per contract terms, otherwise you continue to be billed until the end of your contract terms.
147
147
- Migration may affect Unified Support subscriptions. Contact your Microsoft Account Team.
148
148
149
-
## Next Steps
149
+
## Next steps
150
150
151
151
-[Set up billing for Microsoft Customer Agreement.](https://learn.microsoft.com/azure/cost-management-billing/manage/mca-setup-account#before-you-start-the-setup-we-recommend-you-do-the-following-actions)
152
152
-[Onboard to the Microsoft Customer Agreement (MCA).](https://learn.microsoft.com/azure/cost-management-billing/microsoft-customer-agreement/onboard-microsoft-customer-agreement#migrate-from-an-ea-to-an-mca)
0 commit comments