🆕 New in September 2024
- 📗 Implementing FinOps guide introduced a new FinOps best practices library.
- 📊 Power BI reports expanded to include new Governance and Workload optimization reports, and the cost data now includes a customizable set of tags promoted as columns to simplify tag extraction.
- 🏦 FinOps hubs added support for all Cost Management datasets and parquet and GZip CSV support. All datasets are normalized to FOCUS conventions.
- 📒 FinOps workbooks have been packaged together into a single deployment template to deploy both workbooks together.
- 🔍 Azure Optimization Engine replaced storage account key-based auth with Entra ID auth and added a troubleshooting guide.
- 🌐 Open data files adds support for the FOCUS 1.1 ServiceSubcategory column in the Services mapping file.
ℹ️ Updated
- 🏦 FinOps hubs changed the structure of ingested data to support streamlined data queries and future support for ingestion into other systems, as well as various small fixes and improvements.
- 📊 Power BI reports had various small fixes and improvements across all reports.
- 🔍 Azure Optimization Engine improved SQL database security and various other small fixes and improvements.
- 🌐 Open data files were all updated.
🚨 Breaking changes
- FinOps hubs 0.6 changes the storage path data gets written to in the ingestion container.
- What changed?
- 0.5 path:
{scope}/yyyyMM/focuscost
- 0.6 path:
{dataset}/yyyy/MM/{scope}
- 0.5 path:
- Why is it changing?
- Improves performance of Power BI queries.
- Necessary to clearly differentiate between different datasets.
- Unblocks streamlined ingestion into other systems (e.g., Azure Data Explorer, Microsoft Fabric).
- Do I need to re-backfill historical data?
- No. 0.6 Power BI reports will work with existing exports from FinOps hubs 0.2 or later.
- What about customized reports?
- Customized reports from 0.5 or earlier will not work with FinOps hubs 0.6 due to the storage path change.
- To update custom reports, use the advanced editor to copy each query from 0.6 into your custom report.
- If you changed the queries, start a discussion to share what you're trying to accomplish so we can attempt to find a way for you to make those changes without being impacted by query updates.
- What changed?
Thanks to @aromano2, @akiskips, @nteyan, @jamelachahbar, @Zeo-shark, @ro100e, @MSBrett, @helderpinto, @arthurclares, and @flanakin for their contributions!
Thanks to @saadmsft, @KevDLR, @akiskips, @didayal-msft, @Springstone, @SCuffy, @CaddyG, @sebassem, and @chris-bowman for their support!