Skip to content

Commit 445614c

Browse files
authored
Update migrate-consumption-usage-details-api.md
1 parent 76a3847 commit 445614c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cost-management-billing/automate/migrate-consumption-usage-details-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.reviewer: jojoh
1515

1616
This article discusses migration away from the [Consumption Usage Details API](/rest/api/consumption/usage-details/list), which is planned for deprecation. The exact date of deprecation is still being determined. We recommend that you don't build your reporting pipelines using this API and migrate away from it as soon as possible.
1717

18-
The Enterprise Agreement (EA) reporting APIs, that use an API key for authentication, are retired. EA customers using these APIs should migrate to the Cost Management [Cost Details](/rest/api/cost-management/generate-cost-details-report) API. These older EA reporting APIs are only available to customers with an Enterprise Agreement.
18+
The Enterprise Agreement (EA) reporting APIs, that use an API key for authentication and are accessed through the consumption.azure.com URI endpoint, are retired. EA customers using these APIs should migrate to the Cost Management [Cost Details](/rest/api/cost-management/generate-cost-details-report) API. These older EA reporting APIs are only available to customers with an Enterprise Agreement.
1919

2020
If you use the [Consumption Usage Details API](/rest/api/consumption/usage-details/list) we *recommend*, but don't require that you migrate to the Cost Management [Cost Details](/rest/api/cost-management/generate-cost-details-report) API.
2121

0 commit comments

Comments
 (0)