Skip to content

Commit bf21efe

Browse files
committed
minor update
1 parent 1727841 commit bf21efe

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ The following examples illustrate how billing periods could end:
157157
* 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.
158158
* 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.
159159

160-
After your billing period ends and your invoice created, it can take up to 48 hours later for the usage data to get finalized. If usage file isn't ready, you'll see a message on the Invoices page in the Azure portal stating `Your usage and charges file is not ready`. After the usage file is available, you can download it.
160+
After your billing period ends and your invoice is created, it can take up to 48 hours later for the usage data to get finalized. If usage file isn't ready, you'll see a message on the Invoices page in the Azure portal stating `Your usage and charges file is not ready`. After the usage file is available, you can download it.
161161

162162
Once cost and usage data becomes available in Cost Management, it will be retained for at least seven years. Only the last 13 months is available from the portal. For historical data before 13 months, please use [Exports](tutorial-export-acm-data.md) or the [Cost Details API](../automate/usage-details-best-practices.md#cost-details-api).
163163

0 commit comments

Comments
 (0)