Skip to content

Commit a88e0bc

Browse files
authored
Merge pull request #300271 from hinallur/mcataxcertificate
updated article for mca tax certificate
2 parents b179b18 + 440430e commit a88e0bc

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

articles/cost-management-billing/manage/mca-setup-account.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.reviewer: jkinma
66
ms.service: cost-management-billing
77
ms.subservice: billing
88
ms.topic: how-to
9-
ms.date: 03/21/2025
9+
ms.date: 05/22/2025
1010
ms.author: jkinma
1111
---
1212

@@ -408,6 +408,7 @@ Enterprise administrators and department administrators are listed as invoice se
408408
- EA API keys - Azure Enterprise Reporting APIs are retired aren't available on MCA. Instead, you use Microsoft Cost Management APIs. For more information, see [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs overview](../automate/migrate-ea-reporting-arm-apis-overview.md).
409409
- Automatic purchases - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
410410
- 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. For more information, see [Azure RBAC scopes](../costs/understand-work-scopes.md#azure-rbac-scopes).
411+
- Tax exemption certificates - If your EA account has a tax exemption certificate, you need to create an Azure support request to have a support representative associate your existing tax exempt certificate to your new Microsoft Customer Agreement account. Create a support request in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
411412

412413
Here are some points to consider after migration.
413414

articles/cost-management-billing/microsoft-customer-agreement/onboard-microsoft-customer-agreement.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: bandersmsft
55
ms.service: cost-management-billing
66
ms.subservice: microsoft-customer-agreement
77
ms.topic: conceptual
8-
ms.date: 03/28/2025
8+
ms.date: 05/22/2025
99
ms.author: banders
1010
ms.reviewer: clionabolger
1111
---
@@ -234,6 +234,7 @@ This section of the onboarding guide describes the steps you follow to migrate f
234234
- EA API keys - Azure Enterprise Reporting APIs are retired aren't available on MCA. Instead, you use Microsoft Cost Management APIs. For more information, see [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs overview](../automate/migrate-ea-reporting-arm-apis-overview.md).
235235
- Automatic purchases - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
236236
- 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. For more information, see [Azure RBAC scopes](../costs/understand-work-scopes.md#azure-rbac-scopes).
237+
- Tax exemption certificates - If your EA account has a tax exemption certificate, you need to create an Azure support request to have a support representative associate your existing tax exempt certificate to your new Microsoft Customer Agreement account. Create a support request in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
237238

238239
Here are some points to consider after migration.
239240

0 commit comments

Comments
 (0)