microsoft / microsoft/finops-toolkit

Power BI report ADX -> Regions show incorrect position on map

Open
#2,192 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Status: ▶️ Ready Tool: Power BI Type: Feature 💎
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

Hi, take this as question first, I created internal PoC for Finops hub v14 and was showing Power BI reports.
And received question why it shows that we have cost spending in China, when we cannot have anything there.
Then I noticed all of the location are in incorrect position.

🐛 Problem

PowerBi CostSummary.Report have tab, where users can see cost spending on map view. Problem is the point on map correctly don`t represent data.

👣 Repro steps

In PowerBi report go to regions tab

🤔 Expected

Regions (datacenter locations) should be correctly show with mirror error+/- 100-200 km in reality error is more than 1000 km in many cases.

📷 Screenshots

West Europe -> Netherlands -> But shown in eastern Europe -> Slovakia
Image

Southeast Asia -> Singapore but shown in Thailand
Image

East Asia -> Hong kong -> but shown in middle of China

Image

🔧 Environment

  • FinOps hub version: 14
  • Billing account type: MCA
  • Power BI report type: ADX (Azure Data Explorer)
  • Power Bi report: Cost summary
  • Cost Management export: FOCUS 1.2-preview

Thanks

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.

Research direction

Start in the Power BI CostSummary.Report and reproduce the issue from the Regions tab using the ADX report and FOCUS 1.2-preview environment described here. Compare the plotted datacenter locations for West Europe, Southeast Asia, and East Asia with their expected regions; done means the map positions are within the stated 100–200 km tolerance.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
data-visualization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.