FinOps hubs compatibility guide
FinOps hubs support in-place upgrades by redeploying the template. But what happens with the data? Might it break Power BI reports? What about my customized reports? This guide helps you identify what dependencies need to change when moving from one version of FinOps hubs to another. If you have any questions, start a discussion.
Versioning in the FinOps toolkit
All FinOps toolkit tools and resources maintain the same version number to make it easier to know which tools work together. As of today, it's mostly about FinOps hubs, but will expand as more tools are added in the future. If you can, we recommend updating all resources at the same time. However, we know it isn't always feasible. The intent of this guide is to help you understand what you can expect when you upgrade some but not all tools.
Compatibility chart
The following table conveys different scenarios with specific types of Cost Management exports and FinOps hubs releases. Based on the combination you have (or plan to have), make note of the storage path and the Power BI version.
The storage path is important for any client that's utilizing the same datasets. It might be toolkit Power BI reports (covered by the Power BI version), Microsoft Fabric shortcuts, or other tools.
The Power BI version refers to the Power BI reports made available within that specific version of the FinOps toolkit. If you customized an older version of the reports, make note of the version you started with, as that is what is useful here.
| Cost Management exports | FinOps hubs | Storage path | Power BI | Notes |
|---|---|---|---|---|
| FOCUS costs, Prices, Reservation datasets | 0.6 | {dataset}/{yyyy}/{MM}/{scope} | 0.6+ | Reservation recommendations pulled from hub storage |
| FOCUS 1.0-preview(v1) or 1.0 costs | 0.6 | {dataset}/{yyyy}/{MM}/{scope}¹ | 0.6+² | Storage path updated; Reservation recommendations pulled from a separate, nonhub storage URL (or excluded from report) |
| FOCUS 1.0-preview(v1) or 1.0 costs | 0.5 | {scope}/{yyyyMM}/{dataset} | 0.4+² | Reservation recommendations pulled from a separate, nonhub storage URL (or excluded from report) |
| FOCUS 1.0-preview(v1) or 1.0 costs | 0.4 | {scope}/{yyyyMM}/{dataset} | 0.4+² | Supports a mix of FOCUS 1.0 and 1.0-preview(v1) data; Reservation recommendations pulled from the Cost Management connector for Power BI |
| FOCUS 1.0-preview(v1) only | 0.4 | {scope}/{yyyyMM}/{dataset}¹ | 0.2+ | Storage path updated |
| FOCUS 1.0-preview(v1) costs only | 0.2 - 0.3 | {path}/{yyyyMM}/{dataset} | 0.2+² | Switched to FOCUS data only |
| Actual or Amortized costs (not both) | 0.1 - 0.1.1 | {path}/{yyyyMM}/{dataset} | 0.0.1 - 0.1.1 | Enterprise Agreement and Microsoft Customer Agreement |
| Actual or Amortized costs (not both) | 0.0.1 | {path}/{yyyyMM}/{dataset} | 0.0.1 - 0.1.1 | Enterprise Agreement |
¹ When storage paths update, there's a risk that re-exported data lands in a new place and might cause duplicate data. To resolve, remove the old folders in the ingestion container.
² Older Power BI reports don't work with this combination of FinOps hubs version and exported datasets.
Looking for more?
Did this guide give you the answers you needed? If not, ask a question or share feedback to let us know how we can improve it. We're here to help!