microsoft / microsoft/finops-toolkit

FinOps Hub v13 + Power BI (Storage report) do not show AWS costs when parquet file is dropped directly under ingestion/

Open
#2,046 12 comments 0 reactions 1 assignee View on GitHub

@BoubakriMohamed404 is already working on this.

Since Mar 10, 2026.

Needs: Attention 👋 Tool: Power BI
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

Description:

With FinOps Hub v13, AWS cost data does not appear in Power BI Storage‑based reports when the AWS parquet file (exported as FOCUS 1.0) is manually copied to the hub storage path:
ingestion/costs/<year>/<month>/awstest/

Azure costs render correctly. AWS costs ignored.

Expected behavior:

Storage‑based Power BI reports should display AWS costs also

Actual behavior:

Juste Azure costs are loaded successfully .

Steps to reproduce

  1. Deploy FinOps Hub v13.
  2. Export AWS costs as FOCUS 1.0 parquet (outside the hub pipelines).
  3. Manually copy the parquet to ingestion/costs/<year>/<month>/awstest/ focusfile and add an empty manifest.json file
  4. Open Power BI Storage reports and refresh.
  5. Observe AWS data are not loaded .

Environment

FinOps Hub: v13
Power BI: FinOps toolkit Storage‑based reports
Data sources:
Azure data lake gen 2 → hub (OK)
with AWS parquet (FOCUS 1.0) manually placed in ingestion/costs/<year>/<month>/awstest/

Doc link
How to create and update FinOps hubs - Cloud Computing | Microsoft Learn
https://learn.microsoft.com/en-us/cloud-computing/finops/toolkit/hubs/deploy?tabs=azure-portal%2Cadx-dashboard#ingest-from-other-data-sources

Can you please provide me with the correcte steps to use FinOpsHub with AWS data in PowerBI storage report ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.