Skip to content

Commit ddf762d

Browse files
Merge pull request #300437 from maddieminn/fix-bill-ownership
Fix Ownership on Bill
2 parents f797231 + 6f84af5 commit ddf762d

File tree

3 files changed

+8
-30
lines changed

3 files changed

+8
-30
lines changed

articles/cost-management-billing/manage/cost-management-automation-scenarios.md

Lines changed: 3 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Automation scenarios for Azure billing and cost management
33
description: Learn how common billing and cost management scenarios are mapped to different APIs.
4-
author: KennyDay
5-
ms.reviewer: adwise
4+
author: maddieminn
5+
ms.reviewer: maminn
66
ms.service: cost-management-billing
77
ms.subservice: common
88
ms.topic: reference
99
ms.date: 01/22/2025
10-
ms.author: kenday
10+
ms.author: maminn
1111
---
1212

1313
# Automation scenarios for billing and cost management
@@ -75,30 +75,8 @@ Web Direct and Enterprise customers can use all the following APIs, except where
7575

7676
- [Invoices API](/rest/api/billing/2019-10-01-preview/invoices): Get the download URL for an invoice for a billing period in PDF form.
7777

78-
### Enterprise consumption
79-
The following APIs are for Enterprise only:
80-
81-
- Balance Summary API: Get a monthly summary of information on balances, new purchases, Azure Marketplace service charges, adjustments, and overage charges. You can get this information for the current billing period or any period in the past. Enterprises can use this data to compare with manually calculated summary charges. This API does not provide resource-specific information or an aggregate view of costs.
82-
83-
- Usage Details API: Get information about Azure usage (of Microsoft offerings) for the current month, a specific billing period, or a custom date period. Enterprises can use this data to manually calculate bills based on rate and consumption. Enterprises can also use department/organization information to attribute costs across organizations. The data provides a resource-specific view of usage/cost.
84-
85-
- Marketplace Store Charge API: Get information about Azure usage (of partner offerings) for the current month, a specific billing period, or a custom date period. Enterprises can use this data to manually calculate bills based on rate and consumption. Enterprises can also use department/organization information to attribute costs across organizations. This API provides a resource-specific view of usage/cost.
86-
87-
- Price Sheet API: Get the applicable rate for each meter for the given enrollment and billing period. You can use this rate information in combination with usage details and marketplace usage information to manually calculate the expected bill.
88-
89-
- Billing Periods API: Get a list of billing periods. The API also gives you a property that points to the API route for the four sets of Enterprise API data that pertain to the billing period: BalanceSummary, UsageDetails, Marketplace Charges, and PriceSheet.
90-
91-
- Reserved Instance Recommendations API: Look at 7 days, 30 days, or 60 days of virtual machine usage and get Single and Shared Purchase recommendations. You can use this API to analyze expected cost savings and recommended purchase amounts. For more information, see [APIs for Azure reservation automation](../reservations/reservation-apis.md).
92-
9378
## Frequently asked questions
9479

95-
### What's the difference between the Enterprise Reporting APIs and the Consumption APIs? When should I use each?
96-
These APIs have a similar set of functionality and can answer the same broad set of questions in the billing and cost management space. But they target different audiences:
97-
98-
- Enterprise Reporting APIs are available to customers who have signed an Enterprise Agreement with Microsoft that grants them access to negotiated Azure Prepayment (previously called monetary commitment) and custom pricing. The APIs require a key that you can get from the Azure portal.
99-
100-
- Consumption APIs are available to all customers, with a few exceptions. For more information, see [Cost Management automation overview](../automate/automation-overview.md). We recommend the provided APIs as the solution for the latest development scenarios.
101-
10280
### What's the difference between the Invoice API and the Usage Details API?
10381
These APIs provide a different view of the same data:
10482

articles/cost-management-billing/troubleshoot-subscription/troubleshoot-not-available-conflict.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Not available due to conflict error
33
description: Provides the solutions for a problem where you can't select a management group for a reservation or a savings plan.
4-
author: KennyDay
4+
author: pri-mittal
55
ms.reviewer: onwokolo
66
ms.service: cost-management-billing
77
ms.subservice: common

articles/cost-management-billing/understand/billing-meter-location.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22
title: Shared billing meter regions
33
titleSuffix: Microsoft Cost Management
44
description: Learn about shared billing meter regions in Azure, how they affect cost calculations, and the difference between billing meter regions and resource locations.
5-
author: KennyDay
6-
ms.reviewer: v-minasyanv
5+
author: maddieminn
6+
ms.reviewer: kyleikeda
77
ms.service: cost-management-billing
88
ms.subservice: common
99
ms.topic: concept-article
10-
ms.date: 02/21/2025
11-
ms.author: v-minasyanv
10+
ms.date: 05/27/2025
11+
ms.author: kyleikeda
1212
---
1313

1414
# Shared billing meter regions

0 commit comments

Comments
 (0)