Skip to main content
For finance and technology leaders · Power BI and Microsoft Fabric

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.

Power BI Sentinel connects through a Service Principal or SSO using a user token, and writes to a database you own. Metadata only, never the data inside your reports, in your own Azure environment. Setup takes as little as an hour.

Power BI Sentinel: Deployment Architecture
Where the metadata goes
Your Power BI and Microsoft Fabric tenant
Metadata is read. The data inside your reports is not.
A Service Principal, or SSO using a user token
No agent, no gateway, no invasive tenant configuration.
Your Azure SQL Database or Microsoft Fabric Data Warehouse
Everything extracted lands here, in your own Azure environment.
Your infrastructure
Nothing leaves your tenant
Data never passes through our servers. Audit logs and backups go directly to your own Azure environment.
Metadata only
Power BI Sentinel never reads the data inside your reports. It processes metadata, and nothing else
Your database
Everything extracted lands in an Azure SQL Database or a Microsoft Fabric Data Warehouse that you control. Data never passes through our servers
No agent
Nothing to install and nothing running inside your estate. Setup takes as little as an hour, end to end
ISO 27001
Power BI Sentinel is certified to ISO 27001:2022, alongside Cyber Essentials
In the order you will raise them

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.

The concern
A governance tool normally means giving a vendor a route into the tenant and accepting that a copy of something now sits in their cloud. That is a data protection assessment, a security review and a procurement conversation before anyone sees value.
The answer
Everything lands in a database you own. Power BI Sentinel connects through a Service Principal or SSO using a user token, and writes what it extracts to an Azure SQL Database or a Microsoft Fabric Data Warehouse in your own Azure environment. It processes metadata only, never the data inside your reports, and data never passes through our servers.
How the connection is set up →

What we install, and who owns it for the next three years.

The concern
New platform tooling usually arrives with an agent, a gateway or tenant configuration that someone on your team then maintains, patches and gets paged about. The licence is rarely the expensive part.
The answer
There is nothing to install. No agent, no gateway and no invasive tenant configuration. Your team connects it with a Service Principal or SSO using a user token, and provisions the database and storage account, and that is the whole footprint. Setup takes as little as an hour, end to end, and nothing then runs inside your estate to maintain.
Compared with Microsoft Purview →

Whether a reported figure can be traced back to its source.

The concern
When a figure in a board pack or a statutory return is queried, the trail runs through whoever built the report. If they have moved on, it runs cold, and the number stays unconfirmed while the decision it supports has already been taken.
The answer
Lineage from the visual to the source table. Every dependency mapped, including gateway sources, refresh schedules, Power Query steps and the SQL underneath, across shared workspaces in Power BI and Microsoft Fabric. Alongside it, the semantic model documented: DAX measures, column usage, relationships and measure dependencies.
Data lineage →

What you can actually hand an auditor.

The concern
Power BI shows the estate as it is today. An auditor asks what it looked like on a date in the past, and who could see what at the time. Screenshots taken this morning are not evidence of last March.
The answer
Change tracking with full user attribution. Every change to reports, permissions, tenant settings and workspace configuration is logged with who, what and when. Historic permission snapshots, on the Discovery tier, reconstruct the state of the estate at any point in time, which is usually what the request really means.
Governance and permissions →

What Power BI is costing you, measured rather than assumed.

The concern
Licence allocation is visible. Actual adoption is not, so spend follows headcount rather than use. Microsoft keeps only 30 days of raw activity, so by the time a renewal comes round the evidence has already expired.
The answer
Adoption measured against allocation. Activity across the portal, mobile, Excel exports and embedded reports, plus unused Pro licences, idle Premium capacity and orphaned workspaces. Kept in your own database rather than expiring, so the evidence is there when the renewal is.
Auditing and usage analytics →
If your security team has a sixth, send it over before any call. We will answer it in writing, and you can forward the answer rather than relay it.
Traceability and retention

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.

Power BI Sentinel: Activity Retention
Raw activity data in MicrosoftWhat you have without Power BI Sentinel
30 daysthen it is gone
The same activity in your own databaseWritten there by Power BI Sentinel
Your retention policyit is your database
Relative comparison, not a timeline to scale. Microsoft retains 30 days of raw activity. Power BI Sentinel writes that activity into your Azure SQL Database or Microsoft Fabric Data Warehouse, where it stays for as long as your own retention policy says. An audit question about last year is then a query rather than an apology.
All three are generated continuously and stored in your own database. Nothing to compile at year end, and nothing that expires while you are still going to need it.
Trace a figure with us How auditing works
Cost, both directions

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.

What Power BI Sentinel finds in your Power BI spend
Unused Pro licences
Seats you renew every year for people who have not opened a report, identified from measured activity rather than from a survey.
Idle Premium capacity
Capacity you are paying to keep warm for workloads that are no longer landing on it.
Orphaned workspaces
Workspaces nobody has opened in months, still carrying content, still carrying access, still counting.
Adoption against licence allocation
Real usage across the portal, mobile, Excel exports and embedded reports, with the highest traffic datasets ranked. The evidence arrives before the renewal rather than after it.
How usage and adoption analytics work →
What Power BI Sentinel itself costs
Example cost
from $0.02
per report, per day
Illustrative only. Basis: Enterprise licence, largest tier at full estate capacity. Priced against the number of reports rather than the number of people, so it does not move every time somebody joins. Current rates are on the pricing page.
What that covers, on every report
Documentation and lineage, kept current
DAX measures, Power Query steps, column usage, relationships and measure dependencies, plus every dependency down to the source table
Activity and audit logs
Who opened it, when and from where, held in your own database rather than expiring with the 30 day window
Backups with one-click rollback
Report files backed up to your own Azure Blob Storage, restorable from the portal, with change tracking on every file
Permissions, settings and adoption
Permission snapshots, tenant setting changes, refresh health and adoption against licence allocation, with the change history behind all of it
Tiers
Core, Enterprise, Discovery, and Dedicated Host. Discovery is a licence tier, and Discovery AI is the feature that tier unlocks rather than an add-on to every plan.
Counted by
Total reports across the estate, and the licence has to cover the whole estate rather than the parts you switch on. An Enterprise 1000 licence (E-1000) covers 1,000 reports.
Data centres
US, EU and Australia on every tier. UK on Enterprise and above.
Guarantee
30 day money back guarantee, and up to 20% off multi-year terms.

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.

Send us your estate size and we will tell you which tier fits and what it would cost. No call needed unless you want one.
See pricing and tiers Book a product demo
The security review, in advance

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?
Worth being clear about

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?
Worth being clear about

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.

An eighth question we have not covered? Send it over and we will answer it in writing before any call, so you have something to forward.
Ask us a question Read the FAQs
Three seats, one estate

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.

Next step

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.

ISO 27001:2022 certified
Cyber Essentials certified
Your data never leaves your tenant

Already decided? Self-serve checkout at subscriptions.powerbisentinel.com. Large estate, or need a dedicated host? Email Hello@PowerBISentinel.com.