🆕 New in November 2024
- 📗 Implementing FinOps guide added enterprise app patterns.
- 🏦 FinOps hubs added support for Azure Data Explorer, private endpoints, storage account infrastructure encryption, and FOCUS 1.0r2. Data Explorer is recommended for high-performance advanced analytics when monitoring over $1M in total cost.
- 📊 Power BI reports are now split into separate storage and KQL versions to support FinOps hubs with Data Explorer. Storage reports added partial support for OneLake URLs.
NOTE: Power BI downloads have been renamed. Please use:
- PowerBI-storage.zip for templates that connect to storage (with or without FinOps hubs)
- PowerBI-kql.zip for templates that connect to FinOps hubs with Data Explorer
- PowerBI-demo.zip for reports with sample data
ℹ️ Updated
- 📗 Implementing FinOps guide updated FOCUS conversion instructions.
- 📊 Power BI reports had various small fixes and improvements across all reports.
- 🏦 FinOps hubs changed the structure of ingested data to support ingestion into Azure Data Explorer, as well as various small fixes and improvements.
- 📒 FinOps workbooks had various small fixes and improvements.
- 🔍 Azure Optimization Engine had various small fixes and improvements.
- 🌐 Open data files were all updated.
🚨 Breaking changes
- FinOps hubs 0.7 changes the storage path data gets written to in the ingestion container.
- What changed?
- 0.6 path:
{export-dataset}/yyyy/MM/{scope}
- 0.7 path:
{hub-dataset}/yyyy/MM/{scope}
- Dataset mapping:
- focuscost → Costs
- pricesheet → Prices
- reservationdetails → CommitmentDiscountUsage
- reservationrecommendations → Recommendations
- reservationtransactions → Transactions
- 0.6 path:
- Why is it changing?
- Necessary to support ingesting different export datasets into the same Data Explorer table.
- Aligns to table names in Azure Data Explorer.
- Do I need to re-backfill historical data?
- If using storage-based reports, no. 0.7 reports will work with existing exports from FinOps hubs 0.2 or later.
- If using Data Explorer, yes.
- What about customized reports?
- Customized reports from 0.6 or earlier will not work with FinOps hubs 0.7 due to the storage path change.
- To update custom reports, use the advanced editor to copy the
ftk_Storage
function from 0.7 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 @elbarnit, @ro100e, @juyamagu, @nteyan, @MSBrett, @helderpinto, @arthurclares, and @flanakin for their contributions!
Thanks to @aromano2, @akiskips, @jamelachahbar, @Zeo-shark, @saadmsft, @KevDLR, @akiskips, @didayal-msft, @Springstone, @SCuffy, @CaddyG, and @chris-bowman for their support!