Skip to content

Commit 6ee4f0f

Browse files
authored
Refactor section headers for billing migration checklist
Updated section headers for consistency and clarity. Adjusted formatting for improved readability. Moved to sentence case per review feedback.
1 parent 60ad727 commit 6ee4f0f

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

articles/cost-management-billing/microsoft-customer-agreement/checklist-microsoft-customer-agreement-billing-migration.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -24,30 +24,30 @@ Before migrating from an Enterprise Agreement (EA), Microsoft Customer Agreement
2424
- Align stakeholders on required actions
2525
- Top customer actions with MCA. [Learn More](https://www.microsoft.com/licensing/news/top_customer_actions_after_accepting_microsoft_customer_agreement?rtc=1)
2626

27-
## Validate Contract and Roles
27+
## Validate contract and roles
2828

2929
Confirm access to both the source and the destination MCA as a Billing Account Owner.
3030

3131
- EA → MCA: Ensure EA Admin and MCA Billing Account Owner roles are assigned.
3232
- PAYG → MCA: Ensure a Global Admin for the PAYG subscription and MCA Billing Account Owner role.
3333
- 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)
3434

35-
## No Service Downtime ##
35+
## No service downtime ##
3636

3737
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.
3838

3939
>[!NOTE]
4040
>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.
4141
42-
## Download Historical Data
42+
## Download historical data
4343

4444
- 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)
4545
- You can continue to view historical charges in the Azure portal under the source billing scope, depending on your billing roles:
4646
- 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.
4747
- 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.
4848
- 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.
4949

50-
## Review Billing Hierarchy Changes
50+
## Review billing hierarchy changes
5151

5252
You use the billing account to manage billing for your Microsoft customer agreement.
5353
- Understand the MCA structure: Billing Account → Billing Profile → Invoice Section → Subscription.
@@ -87,7 +87,7 @@ Self-service reservation transfers: Supported when there's no currency change or
8787
- Cancellation occurs at the time of the next monthly payment for each individual reservation.
8888
- This cancellation is intentional and only affects monthly reservation purchases.
8989

90-
## Cost Management & Reporting
90+
## Cost management & reporting
9191

9292
- Recreate the following aspects under MCA:
9393
- Budgets [Learn More](https://learn.microsoft.com/azure/cost-management-billing/costs/tutorial-acm-create-budgets?tabs=psbudget)
@@ -103,7 +103,7 @@ Self-service reservation transfers: Supported when there's no currency change or
103103
- APIs: Update endpoints to align with MCA's billing structure.
104104
- Automation: Modify scripts that rely on Management Group-level scoping.
105105

106-
## API & Automation Updates
106+
## API & automation updates
107107

108108
Replace legacy APIs with MCA APIs and updated billing properties. APIs & Automation need to be recreated in MCA.
109109

@@ -116,37 +116,37 @@ Replace legacy APIs with MCA APIs and updated billing properties. APIs & Automat
116116
>[!NOTE]
117117
> 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)
118118
119-
## Technical Dependencies
119+
## Technical dependencies
120120

121121
- 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.
122122
- Check compatibility of dashboards (for example, Emissions Impact Dashboard) and update references to MCA billing scope.
123123

124-
## Invoice Setup
124+
## Invoice setup
125125

126126
- Changes in billing constructs
127127
- Getting started with MCA billing [Learn More](https://learn.microsoft.com/azure/cost-management-billing/understand/mca-overview)
128128
- 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)
129129

130-
## Payment Setup
130+
## Payment setup
131131

132132
- 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)
133133
- Notify your accounts payable team.
134134
- Create separate records for EA and MCA invoices.
135135
- Expect a final invoice from the source and new monthly MCA invoices.
136136
- For bank detail verification letters, e invoicing, and third party invoicing requirements, contact your Microsoft Account team.
137137

138-
## Tax & Compliance
138+
## Tax and compliance
139139

140140
- Tax exemption certificates: If your account has a tax exemption certificate, create an Azure support request to associate it with your MCA account.
141141
- 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.
142142

143-
## Support Plan
143+
## Support plan
144144

145145
- Support plans don't transfer to MCA. You need to repurchase a Support Plan on your MCA.
146146
- Cancel existing plans per contract terms, otherwise you continue to be billed until the end of your contract terms.
147147
- Migration may affect Unified Support subscriptions. Contact your Microsoft Account Team.
148148

149-
## Next Steps
149+
## Next steps
150150

151151
- [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)
152152
- [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

Comments
 (0)