Skip to content

Commit d01147d

Browse files
authored
Merge pull request #112103 from flanakin/patch-14
Data refresh cleanup + add data retention
2 parents 8070e08 + 4358ec0 commit d01147d

File tree

2 files changed

+16
-23
lines changed

2 files changed

+16
-23
lines changed

articles/cost-management-billing/costs/get-started-partners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -241,7 +241,7 @@ When the **PartnerEarnedCreditApplied** property is _True_, the associated cost
241241

242242
When the **PartnerEarnedCreditApplied** property is _False_, the associated cost hasn't met the required eligibility for the credit. Or, the service purchased isn't eligible for partner earned credit.
243243

244-
Service usage data normally takes 8-24 hours to appear in Cost Management. For more information, see [Usage data update frequency varies](understand-cost-mgt-data.md#usage-data-update-frequency-varies). PEC credits appear within 48 hours from time of access in Azure Cost Management.
244+
Service usage data normally takes 8-24 hours to appear in Cost Management. For more information, see [Cost and usage data updates and retention](understand-cost-mgt-data.md#cost-and-usage-data-updates-and-retention). PEC credits appear within 48 hours from time of access in Azure Cost Management.
245245

246246

247247
You can also group and filter by the **PartnerEarnedCreditApplied** property using the **Group by** options. Use the options to examine costs that do and don't have PEC.

articles/cost-management-billing/costs/understand-cost-mgt-data.md

Lines changed: 15 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,12 @@ The following offers aren't supported yet:
7070
| **Support Plans** | Azure Government Pro-Direct Support | Default_2014-09-01 | MS-AZR-USGOV-0042P |
7171
| **Support Plans** | Azure Government Developer Support | Default_2014-09-01 | MS-AZR-USGOV-0043P |
7272

73-
## Determine your offer type
73+
### Free trial to pay-as-you-go upgrade
74+
75+
For information about the availability of free tier services after you upgrade to pay-as-you-go pricing from a Free trial, see the [Azure free account FAQ](https://azure.microsoft.com/free/free-account-faq/).
76+
77+
### Determine your offer type
78+
7479
If you don't see data for a subscription and you want to determine if your subscription falls under the supported offers, you can validate that your subscription is supported. To validate an Azure subscription is supported, sign in to the [Azure portal](https://portal.azure.com). Then select **All Services** in the left menu pane. In the list of services, select **Subscriptions**. In the subscription list menu, select the subscription that you want to verify. Your subscription is shown on the Overview tab and you can see the **Offer** and **Offer ID**. The following image shows an example.
7580

7681
![Example of the Subscription Overview tab showing Offer and Offer ID](./media/understand-cost-mgt-data/offer-and-offer-id.png)
@@ -101,15 +106,15 @@ Azure Cost Management receives tags as part of each usage record submitted by th
101106
- Resource tags are only supported for resources deployed to resource groups.
102107
- Some deployed resources may not support tags or may not include tags in usage data – see [Tags support for Azure resources](../../azure-resource-manager/tag-support.md).
103108
- Resource tags are only included in usage data while the tag is applied – tags are not applied to historical data.
104-
- Resource tags are only available in Cost Management after the data is refreshed – see [Usage data update frequency varies](#usage-data-update-frequency-varies).
109+
- Resource tags are only available in Cost Management after the data is refreshed – see [Cost and usage data updates and retention](#cost-and-usage-data-updates-and-retention).
105110
- Resource tags are only available in Cost Management when the resource is active/running and producing usage records (e.g. not when a VM is deallocated).
106111
- Managing tags requires contributor access to each resource.
107112
- Managing tag policies requires either owner or policy contributor access to a management group, subscription, or resource group.
108113

109114
If you do not see a specific tag in Cost Management, consider the following:
110115

111116
- Was the tag applied directly to the resource?
112-
- Was the tag applied more than 24 hours ago? See [Usage data update frequency varies](#usage-data-update-frequency-varies)
117+
- Was the tag applied more than 24 hours ago? See [Cost and usage data updates and retention](#cost-and-usage-data-updates-and-retention)
113118
- Does the resource type support tags? The following resource types do not support tags in usage data as of December 1, 2019. See [Tags support for Azure resources](../../azure-resource-manager/tag-support.md) for the full list of what is supported.
114119
- Azure Active Directory B2C Directories
115120
- Azure Firewalls
@@ -129,24 +134,22 @@ Here are a few tips for working with tags:
129134
- Use the Tags API in conjunction with either Query or UsageDetails to get all cost based on the current tags.
130135

131136

132-
## Free trial to pay-as-you-go upgrade
133-
134-
For information about the availability of free tier services after you upgrade to pay-as-you-go pricing from a Free trial, see the [Azure free account FAQ](https://azure.microsoft.com/free/free-account-faq/).
135-
136-
## Rated usage data refresh schedule
137+
## Cost and usage data updates and retention
137138

138-
Cost and usage data is available in Cost Management + Billing in the Azure portal and [supporting APIs](../index.yml). Keep the following points in mind as you review costs:
139+
Cost and usage data is typically available in Cost Management + Billing in the Azure portal and [supporting APIs](../index.yml) within 8-24 hours. Keep the following points in mind as you review costs:
139140

141+
- Each Azure service (such as Storage, Compute, and SQL) emits usage at different intervals – You might see data for some services sooner than others.
140142
- Estimated charges for the current billing period are updated six times per day.
141143
- Estimated charges for the current billing period can change as you incur more usage.
142144
- Each update is cumulative and includes all the line items and information from the previous update.
143145
- Azure finalizes or _closes_ the current billing period up to 72 hours (three calendar days) after the billing period ends.
144146

145-
The following examples illustrate how billing periods could end.
147+
The following examples illustrate how billing periods could end:
146148

147-
Enterprise Agreement (EA) subscriptions – If the billing month ends on March 31, estimated charges are updated up to 72 hours later. In this example, by midnight (UTC) April 4.
149+
* Enterprise Agreement (EA) subscriptions – If the billing month ends on March 31, estimated charges are updated up to 72 hours later. In this example, by midnight (UTC) April 4.
150+
* Pay-as-you-go subscriptions – If the billing month ends on May 15, then the estimated charges might get updated up to 72 hours later. In this example, by midnight (UTC) May 19.
148151

149-
Pay-as-you-go subscriptions – If the billing month ends on May 15, then the estimated charges might get updated up to 72 hours later. In this example, by midnight (UTC) May 19.
152+
Once cost and usage data becomes available in Cost Management + Billing, it will be retained for at least 7 years.
150153

151154
### Rerated data
152155

@@ -162,16 +165,6 @@ Costs shown in Cost Management are rounded. Costs returned by the Query API aren
162165
- Aggregate charge rendered: 0.004 + 0.004 = 0.008. The charge shown is $0.01.
163166
- Query API - Charges are shown at eight decimal places and rounding doesn't occur.
164167

165-
166-
## Usage data update frequency varies
167-
168-
The availability of your incurred usage data in Cost Management depends on a couple of factors, including:
169-
170-
- How frequently Azure services (such as Storage, Compute, CDN, and SQL) emit usage.
171-
- The time taken to process the usage data through the rating engine and cost management pipelines.
172-
173-
Some services emit usage more frequently than others. So, you might see data in Cost Management for some services sooner than other services that emit data less frequently. Typically, usage for services takes 8-24 hours to appear in Cost Management. Keep in mind that data for an open month gets refreshed as you incur more usage because updates are cumulative.
174-
175168
## Historical data might not match invoice
176169

177170
Historical data for credit-based and pay-in-advance offers might not match your invoice. Some Azure pay-as-you-go, MSDN, and Visual Studio offers can have Azure credits and advanced payments applied to the invoice. However, the historical data shown in Cost Management is based on your estimated consumption charges only. Cost Management historical data doesn't include payments and credits. So, historical data shown for the following offers may not match exactly with your invoice.

0 commit comments

Comments
 (0)