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/automate/migrate-ea-balance-summary-api.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
4
4
description: This article has information to help you migrate from the EA Balance Summary API.
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 02/23/2024
7
+
ms.date: 04/23/2024
8
8
ms.topic: conceptual
9
9
ms.service: cost-management-billing
10
10
ms.subservice: cost-management
@@ -13,14 +13,14 @@ ms.reviewer: jojoh
13
13
14
14
# Migrate from EA Balance Summary API
15
15
16
-
EA customers who were previously using the Enterprise Reporting consumption.azure.com API to get their balance summary need to migrate to a replacement Azure Resource Manager API. Instructions to do this are outlined below along with any contract differences between the old API and the new API.
16
+
EA customers who were previously using the Enterprise Reporting consumption.azure.com API to get their balance summary need to migrate to a replacement Azure Resource Manager API. The following instructions help you migrate and discuss any contract differences between the old API and the new API.
17
17
18
18
> [!NOTE]
19
19
> On May 1, 2024, Azure Enterprise Reporting APIs will be retired. [Migrate to Microsoft Cost Management APIs](migrate-ea-reporting-arm-apis-overview.md) before then.
20
20
21
-
## Assign permissions to an SPN to call the API
21
+
## Assign permissions to a service principal to call the API
22
22
23
-
Before calling the API, you need to configure a Service Principal with the correct permission. You use the service principal to call the API. For more information, see [Assign permissions to ACM APIs](cost-management-api-permissions.md).
23
+
Before calling the API, you need to configure a Service Principal with the correct permission. You use the service principal to call the API. For more information, see [Assign permissions to Cost Management APIs](cost-management-api-permissions.md).
24
24
25
25
### Call the Balance Summary API
26
26
@@ -32,7 +32,7 @@ Use the following request URIs when calling the new Balance Summary API. Your en
Copy file name to clipboardExpand all lines: articles/cost-management-billing/automate/migrate-ea-marketplace-store-charge-api.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
4
4
description: This article has information to help you migrate from the EA Marketplace Store Charge API.
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 02/22/2024
7
+
ms.date: 04/23/2024
8
8
ms.topic: conceptual
9
9
ms.service: cost-management-billing
10
10
ms.subservice: cost-management
@@ -26,9 +26,9 @@ Endpoints to migrate off:
26
26
|`/v3/enrollments/{enrollmentNumber}/billingPeriods/{billingPeriod}/marketplacecharges`| • API method: GET <br><br> • Synchronous (non polling) <br><br> • Data format: JSON |
27
27
|`/v3/enrollments/{enrollmentNumber}/marketplacechargesbycustomdate?startTime=2017-01-01&endTime=2017-01-10`| • API method: GET <br><br> • Synchronous (non polling) <br><br> • Data format: JSON |
28
28
29
-
## Assign permissions to an SPN to call the API
29
+
## Assign permissions to a service principal to call the API
30
30
31
-
Before calling the API, you need to configure a service principal with the correct permission. You use the service principal to call the API. For more information, see [Assign permissions to ACM APIs](cost-management-api-permissions.md).
31
+
Before calling the API, you need to configure a service principal with the correct permission. You use the service principal to call the API. For more information, see [Assign permissions to Cost Management APIs](cost-management-api-permissions.md).
32
32
33
33
### Call the Marketplaces API
34
34
@@ -51,17 +51,20 @@ For subscription, billing account, department, enrollment account, and managemen
> The new response is missing the `AccountId`, `AccountOwnerId`, and `DepartmentId` fields. For account and department information, use the `AccountName` and `DepartmentName` fields.
Copy file name to clipboardExpand all lines: articles/cost-management-billing/automate/migrate-ea-price-sheet-api.md
+66-50Lines changed: 66 additions & 50 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
4
4
description: This article has information to help you migrate from the EA Price Sheet API.
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 02/22/2024
7
+
ms.date: 04/23/2024
8
8
ms.topic: conceptual
9
9
ms.service: cost-management-billing
10
10
ms.subservice: cost-management
@@ -13,41 +13,63 @@ ms.reviewer: jojoh
13
13
14
14
# Migrate from EA Price Sheet API
15
15
16
-
EA customers who were previously using the Enterprise Reporting consumption.azure.com API to get their price sheet need to migrate to a replacement Azure Resource Manager API. Instructions to do this are outlined below along with any contract differences between the old API and the new API.
16
+
EA customers who were previously using the Enterprise Reporting consumption.azure.com API to get their price sheet need to migrate to a replacement Azure Resource Manager API. The following instructions help you migrate and they also describe any contract differences between the old API and the new API.
17
17
18
18
> [!NOTE]
19
19
> On May 1, 2024, Azure Enterprise Reporting APIs will be retired. [Migrate to Microsoft Cost Management APIs](migrate-ea-reporting-arm-apis-overview.md) before then.
20
20
21
-
## Assign permissions to an SPN to call the API
21
+
## Assign permissions to a service principal to call the API
22
22
23
-
Before calling the API, you need to configure a Service Principal with the correct permission. You use the service principal to call the API. For more information, see [Assign permissions to ACM APIs](cost-management-api-permissions.md).
23
+
Before calling the API, you need to configure a service principal (SPN) with the correct permission. You use the service principal to call the API. For more information, see [Assign permissions to Cost Management APIs](cost-management-api-permissions.md).
24
24
25
25
### Call the Price Sheet API
26
26
27
-
Use the following request URIs when calling the new Price Sheet API.
27
+
The Price Sheet API generates the price sheet asynchronously and produces a file that you download.
28
+
29
+
Use the following request URIs when calling the new Price Sheet API:
POST https://management.azure.com/providers/Microsoft.Billing/billingAccounts/{billingAccountId}/billingPeriods/{billingPeriodName}/providers/Microsoft.CostManagement/pricesheets/default/download?api-version=2023-11-01
40
41
```
41
42
42
-
[Get for specified Billing Period](/rest/api/consumption/pricesheet/getbybillingperiod)
43
+
The POST request returns a location to poll the report generation status as outlined in the following response:
### Sample request to poll report generation status
67
+
68
+
```HTTP
69
+
GET https://management.azure.com/providers/Microsoft.Billing/billingAccounts/0000000/providers/Microsoft.CostManagement/operationResults/00000000-0000-0000-0000-000000000000?api-version=2023-09-01
70
+
```
49
71
50
-
Old response:
72
+
### Response body changes
51
73
52
74
```json
53
75
[
@@ -74,43 +96,37 @@ Old response:
74
96
"currencyCode": "USD"
75
97
},
76
98
...
77
-
]
99
+
]
78
100
```
79
101
80
-
New response:
81
-
82
-
Old data is now in the `pricesheets` field of the new API response. Meter details information is also provided.
| basePrice | string | The unit price at the time the customer signs on or the unit price at the time of service meter GA launch if it is after sign-on.<br><br>It applies to Enterprise Agreement users |
109
+
| currencyCode | string | Currency in which the Enterprise Agreement was signed |
110
+
| effectiveEndDate | string | Effective end date of the Price Sheet billing period |
111
+
| effectiveStartDate | string | Effective start date of the Price Sheet billing period |
112
+
| enrollmentNumber | string | Unique identifier for the EA billing account. |
113
+
| includedQuantity | string | Quantities of a specific service to which an EA customer is entitled to consume without incremental charges. |
114
+
| marketPrice | string | The current list price for a given product or service. This price is without any negotiations and is based on your Microsoft Agreement type.<br><br>For PriceType Consumption, market price is reflected as the pay-as-you-go price.<br><br>For PriceType Savings Plan, market price reflects the Savings plan benefit on top of pay-as-you-go price for the corresponding commitment term.<br><br>For PriceType ReservedInstance, market price reflects the total price of the one or three-year commitment.<br><br>Note: For EA customers with no negotiations, market price might appear rounded to a different decimal precision than unit price. |
115
+
| meterCategory | string | Name of the classification category for the meter. For example, Cloud services, Networking, etc. |
116
+
| meterId | string | Unique identifier of the meter |
117
+
| meterName | string | Name of the meter. The meter represents the deployable resource of an Azure service. |
118
+
| meterRegion | string | Name of the Azure region where the meter for the service is available. |
119
+
| meterSubCategory | string | Name of the meter subclassification category. |
120
+
| meterType | string | Name of the meter type |
121
+
| partNumber | string | Part number associated with the meter |
122
+
| priceType | string | Price type for a product. For example, an Azure resource with a pay-as-you-go rate with priceType as Consumption. Other price types include ReservedInstance and Savings Plan. |
123
+
| product | string | Name of the product accruing the charges. |
124
+
| productId | string | Unique identifier for the product whose meter is consumed. |
125
+
| serviceFamily | number | Type of Azure service. For example, Compute, Analytics, and Security. |
126
+
| skuId | string | Unique identifier of the SKU |
127
+
| term | string | Term length for Azure Savings Plan or Reservation term – one year or three years (P1Y or P3Y) |
128
+
| unitOfMeasure | string | How usage is measured for the service |
129
+
| unitPrice | string | The per-unit price at the time of billing for a given product or service, inclusive of any negotiated discounts on top of the market price.<br><br>For PriceType ReservedInstance, unit price reflects the total cost of the one or three-year commitment including discounts.<br><br>Note: The unit price isn't the same as the effective price in usage details downloads when services have differential prices across tiers.<br><br>If services are multi-tiered pricing, the effective price is a blended rate across the tiers and doesn't show a tier-specific unit price. The blended price or effective price is the net price for the consumed quantity spanning across the multiple tiers (where each tier has a specific unit price). |
Copy file name to clipboardExpand all lines: articles/cost-management-billing/automate/migrate-ea-reporting-arm-apis-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
4
4
description: This article provides an overview about migrating from Azure Enterprise Reporting to Microsoft Cost Management APIs.
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 02/22/2024
7
+
ms.date: 04/23/2024
8
8
ms.topic: conceptual
9
9
ms.service: cost-management-billing
10
10
ms.subservice: cost-management
@@ -17,7 +17,7 @@ This article informs developers that have built custom solutions using the [Azur
17
17
18
18
**Key points**:
19
19
- Migration recommended - We strongly recommend that you consider migrating your custom solutions to the Microsoft Cost Management APIs. They're actively being developed and offer improved functionality.
20
-
- Retirement date - The Azure Enterprise Reporting APIs will be retired on **May 1, 2024**. After this date, the APIs will stop responding to requests.
20
+
- Retirement date - The Azure Enterprise Reporting APIs will be retired on **May 1, 2024**.
21
21
22
22
**This article provides**:
23
23
- An overview of the differences between [Azure Enterprise Reporting APIs](../manage/enterprise-api.md) and Cost Management APIs.
0 commit comments