Manually reviewing Azure costs through the portal each month is time-consuming and inconsistent. Cost Management Exports solve this by delivering structured cost data to a storage account on a scheduled basis, enabling automation, Power BI reporting, and finance integration without manual intervention.
This post walks through setting up scheduled exports and accessing the exported data for downstream processing.
1. What Are Azure Cost Management Exports
Azure Cost Management Exports are scheduled jobs that write cost and usage data as CSV files to an Azure Blob Storage container. Exports can be configured at the subscription, resource group, or management group scope.
There are three export types available:
- Daily export of month-to-date costs: appends data daily, useful for real-time tracking
- Weekly export of the last 7 days: a rolling weekly snapshot
- Monthly export of the last billing month: the most common choice for finance reporting
2. Creating a Scheduled Export
- Navigate to Cost Management + Billing > Cost Management > Exports
- Select + Add
- Provide an Export name and select the Export type (Monthly is recommended for finance use cases)
- Under Storage, select an existing storage account or create a new one
- Specify a Container name and Directory path. A path such as
cost-exports/monthlykeeps exports organised - Select Create
Following is the recommended storage account configuration for cost exports:
- Redundancy: LRS is sufficient, as this data can be regenerated
- Access tier: Cool, since cost data is written once and read infrequently
- Soft delete: Enabled with a 7-day retention window
Once created, the export runs automatically on schedule. You can also select Run now to trigger an immediate export for testing.y on schedule. You can also select Run now to trigger an immediate export for testing.
3. Accessing the Exported Data
Exported files are delivered to the storage container as CSV files named with a date suffix, for example:
cost-exports/monthly/20250501-20250531/export_20250601.csv
Each row represents an individual resource's cost for the period, including fields such as ResourceId, ResourceType, ResourceGroupName, MeterCategory, CostInBillingCurrency, and any resource tags.
Following is the recommended approach for accessing the data:
- Azure Storage Explorer: for ad hoc review and validation
- Power BI: connect directly to the blob container using the Azure Blob Storage connector for monthly dashboards
- Logic App or Azure Function: for automated processing such as sending cost summaries by email or posting to a Teams channel
4. Filtering and Enriching Export Data
The raw CSV export includes all resources. For team-level reporting, filter rows by the CostCenter or Team tag columns. Consistent tagging is therefore a prerequisite for meaningful cost reports.
If tags are missing from a significant portion of resources, review the tagging coverage in Azure Policy > Compliance before relying on exports for chargeback purposes.
Summary
Azure Cost Management Exports provide a reliable, low-maintenance mechanism for delivering cost data to storage for downstream reporting and automation. Configuring a monthly export early in a project's lifecycle ensures that historical data is available when finance teams need it, removing the need for manual extraction from the portal each month.
No comments:
Post a Comment