Nothing installed.
No data out.
Every number traceable.
Two questions decide whether a governance tool ever gets as far as a business case. Where does our data go, and what does it cost. Both answers are short, and both are on this page before anything else.
Five concerns.
Answered before you ask.
You have evaluated tools before, so you know which five things decide it. Here they are in that order, with the architecture first, because that is what a security review opens on.
Where our metadata goes, and who else can reach it.
What we install, and who owns it for the next three years.
Whether a reported figure can be traced back to its source.
What you can actually hand an auditor.
What Power BI is costing you, measured rather than assumed.
Microsoft keeps 30 days.
You keep the rest.
Defending a number has two halves: showing where it came from, and showing what happened around it. The first is lineage. The second is an activity trail that has to still exist when someone asks, which is where the 30 day window quietly becomes a problem.
From the visual to the source table
Every dependency behind a reported number: gateway sources, refresh schedules, Power Query steps and the SQL underneath. Shared workspaces across Power BI and Microsoft Fabric, down to source table level.
Who changed it, and who could see it
Changes to reports, permissions, tenant settings and workspace configuration, logged with full user attribution. Historic permission snapshots, on the Discovery tier, rebuild the state of the estate on any past date, as compliance evidence or incident root cause.
What the measure actually does
Semantic model documentation covering DAX measures, Power Query steps, column usage, relationships and measure dependencies. The paperwork behind a definition, for an audit, a handover or an onboarding.
What it finds, and
what it costs you.
Two numbers matter in a business case: the waste you can evidence, and the line item you are adding. Both are below, and the second one is small enough that the first usually settles it.
One tier note worth knowing before you scope it. Intra-day activity tracking is available on Enterprise tier and above, so if your reporting cycle depends on seeing activity within the day rather than the next morning, that is the tier to price.
Seven questions your security team
is going to send back
Answered here so you can forward the page rather than relay the answers, including the two things Power BI Sentinel deliberately does not do.
What identity does it use, and what can it read?
A Service Principal, or SSO using a user token. There is no agent to install, no gateway to stand up and no invasive tenant configuration, so the connection is something your admins set up, review and can revoke.
What it reads is metadata only: workspace, report, dataset, permission, tenant setting and activity metadata. It never reads the data inside your reports.
The setup guide has the prerequisites in full, if your team wants to scope it before you commit to anything.
Where does everything it extracts physically live?
In a database you own: either an Azure SQL Database or a Microsoft Fabric Data Warehouse, inside your own Azure environment. Report backups go to your own Azure Blob Storage.
Data never passes through our servers. Audit logs and backups go directly to your own Azure environment, which is what makes the data residency question a short one.
What assurance can you give our security team?
Power BI Sentinel is certified to ISO 27001:2022 and Cyber Essentials.
Because the architecture keeps your metadata in your own tenant, the vendor risk assessment is narrower than it usually is for a governance tool: there is no vendor-side copy of your estate to assess.
Do we not already have Microsoft Purview for this?
Power BI Sentinel is not a Purview replacement and does not claim to be. Purview is a broad data governance platform that needs significant configuration and ongoing maintenance to cover Power BI properly.
Power BI Sentinel is purpose built for Power BI and Microsoft Fabric, and is deliberately far lighter touch. If Purview is already running well in your estate, the two are complementary. Read the side by side comparison.
What happens to the history we build up if we stop?
It stays where it already is. The database is yours, in your tenant, and everything Power BI Sentinel extracts sits in it as queryable tables. You can report on it using the supplied Power BI template files, or query the raw tables directly with whatever you already use.
So the governance history is an asset you keep rather than something you rent, and there is no proprietary store to migrate out of.
Does lineage cover every workspace in the tenant?
Shared workspaces, not personal workspaces. Lineage maps every dependency from report visuals down to source tables, including gateway sources, refresh schedules, Power Query steps and SQL analysis, across the shared workspaces in Power BI and Microsoft Fabric.
Content that only ever lives in somebody’s personal workspace is outside that map. For most finance and compliance work that is the right boundary, because anything being reported on should be in a shared workspace in the first place, but it is better said now than discovered later. What lineage covers.
Will it change the permissions it recommends changing?
No, and that is by design. Least-privilege analysis compares each user’s assigned role against their actual measured activity, the reports they opened, the content they published, the admin actions they took, and recommends the least-privilege role that fits what they really do.
It recommends only. Power BI Sentinel does not write permission changes back to your tenant. There is no one-click accept and no bulk permission-review scheduling. Your admin makes the change in Power BI, and Power BI Sentinel then logs it via change tracking. Nothing alters your estate without a person deciding to.
For a CTO signing off a third-party connection, that is usually the point: the tool produces evidence and recommendations, and your own change process stays the only thing that can move access. How access governance works.
Reading this on somebody else’s behalf?
The same estate looks different depending on which chair you sit in. Send the right page to the right person, and skip the translation.
Senior Leadership
Accountability, compliance evidence, and the questions that land on a leadership agenda without a straight answer attached.
Finance & CTO
Data residency, vendor risk, traceability of reported figures, audit trails, and what Power BI is actually costing you.
BI Developer & Admin
Impact analysis before a change, refresh failures, migration mapping, and the undocumented models somebody else left behind.
Bring the questions
your security team asked
Forty five minutes, screen shared. We will walk the architecture, trace a figure back to its source table, and price it against your actual estate size. If the answer is that you do not need us yet, that is a useful session too.
Already decided? Self-serve checkout at subscriptions.powerbisentinel.com. Large estate, or need a dedicated host? Email Hello@PowerBISentinel.com.