POWER BI & FABRIC DISCOVERY

Fabric Beacon

One place to search workspaces, reports, semantic models, measures, and lineage — with governance scores and refresh health — so the team stops portal-hopping and tribal knowledge.

Web app + APIDeep search & lineageDemo or live workspace

Goal

Build an internal discovery platform so the team can search, browse, and understand every Power BI / Fabric asset in scope — with lineage, governance scores, and refresh health in one place.

Description

Fabric Beacon is a centralized catalog for workspaces, datasets, reports, paginated reports, measures, columns, and DAX/M definitions. It replaces portal-hopping with deep search, reverse lookup, interactive lineage, and workspace-level governance so anyone can find what exists, what it depends on, and whether it is still trustworthy.

Success looks like

Every in-scope workspace is synced into a searchable catalog; any report, dataset, table, column, or measure can be found in seconds; lineage shows source → model → report clearly; governance surfaces stale datasets and orphaned measures; refresh status is visible; analysts self-serve without admin help.

What we can achieve

One source of truth instead of scattered bookmarks; faster impact analysis before model changes; proactive governance; fewer duplicate reports; a foundation for data trust and release readiness.

What we can use it for

Onboarding; “which reports use this table or measure?” before a change; workspace health before a release; stale content cleanup; migration decisions; leadership view of the BI estate.

What you will see

On the screenIn simple words
Discovery / catalogWorkspaces, reports, datasets, paginated reports in one browse view.
SearchFind assets by name, table, column, measure, or DAX text.
LineageSee how sources, models, and reports connect.
GovernanceHealth scores, stale models, orphaned measures.
JiraTicket-scoped analysis — what already exists before you build.
DocumentationBusiness-friendly report pages (Summary, When to Use).

Who this is for

Insights analysts, BI developers, and leads who need catalog, impact analysis, and governance across Fabric / Power BI workspaces.

Before vs after

Without Fabric Beacon

Ten admin tabs, bookmarks, and memory. Impact analysis takes hours. Duplicates slip into releases.

With Fabric Beacon

One catalog, search, lineage, and Jira context. You know what exists before you change it.

Find any asset in seconds, not meetings

How it works

flowchart TD A["Open Fabric Beacon"] --> B{"Demo or live?"} B -->|Demo| C["Sample catalog"] B -->|Live| D["Setup: sign in once"] D --> E["Sync workspace catalog"] E --> F["Search · lineage · governance"] F --> G["Optional Jira ticket scope"]

Setup — once

  1. Clone the engineering repo (see README on GitHub).
  2. Run .\start-dev.ps1 → open the app in the browser.
  3. Use Demo with no credentials, or complete Setup for live Power BI / Fabric.
  4. Optional: connect Jira for ticket analyzer flows.
You are done when you can open Discovery, search a report name, and open lineage for a dataset.

Daily use

Before a model or report change: search the table or measure → open lineage → note impacted reports. For tickets: open Jira analyzer with the ticket key. Before release: check governance and refresh health for the workspace.

Example

Search: "New Members" Results: 2 reports, 1 dataset, 12 measures Lineage: gold_layer.dim_branch → semantic model → New Members dashboard Governance: dataset refresh OK · health score 82/100 Jira AN-XXXX: matched workspace QA · no duplicate report name

If something fails

What you seeWhat to do
Empty catalog (live)Finish Setup wizard; confirm workspace access in Power BI Service.
Search returns nothingRun catalog sync; confirm the workspace is in scope.
Jira panel emptyAdd Jira credentials in Setup; paste ticket key on Jira page.