Opens in a new tab
MIP Logo

What Is Power BI Sentinel? Governance, Auditing and Disaster Recovery, Explained

What Is Power BI Sentinel? Governance, Auditing and Disaster Recovery, Explained
What is Power BI Sentinel?

Power BI Sentinel is a software-as-a-service governance tool for Power BI and Microsoft Fabric. It provides three things the platform does not give you in one place: governance (a complete, live picture of your estate, its content, access and usage), auditing (a durable record of who did what, kept for as long as you need it), and disaster recovery (automated backups and change tracking for your reports and semantic models, with the ability to restore a previous version).

The simplest way our group consulting director Russell explains the distinction: “Power BI is a reporting tool, it lets you create dashboards and surface insights. Power BI Sentinel gives you the ability to govern your Power BI estate.”

One builds the reports. The other keeps the growing pile of reports safe, visible and under control.

Why do organisations need a governance tool for Power BI?

Because Power BI succeeds. It spreads through an organisation precisely because anyone can build with it, and the same self-service freedom that makes it valuable makes it sprawl. Russell hears the same phrase in client meetings again and again: “it’s becoming the wild west out there.”

No client has ever rung us asking for “a Power BI monitoring tool.” They describe problems:

  • “We have a hundred licences and we don’t know who is actually using them, or if they are using them at all.”
  • “A new CDO has arrived and is asking how many reports we have, how often they refresh, who uses them. Our admins spent four days trying to find out.”
  • “We had a scare and we cannot see who accessed the data or whether anyone exported it.”
  • “We have to meet compliance obligations and we cannot evidence any of this.”

Those four problems, licence waste, blindness, breach anxiety and compliance pressure, are what Sentinel exists to solve. The triggers that finally push an organisation to act are almost always one of the last two: a regulatory directive, or a fright.

What does Power BI look like without Sentinel?

Fragmented, is Russell’s summary. The information exists, but it is scattered across consoles that were each built for a different job. Want to know one person’s access across the estate? You open a workspace, open its security roles, note what you find, then repeat for every other workspace, manually assembling the picture. Want usage history? The activity log API gives you 28 days, and even the Purview audit log defaults to 180, a limitation big enough that we wrote a separate guide on it.

Technically strong teams sometimes script against the APIs to stitch this together themselves. It works until Microsoft changes something behind the scenes, the scripts quietly break, and the person who wrote them has moved on. We look at the build-it-yourself question honestly later in this article.

What do clients actually see in the first week?

Sentinel starts collecting the moment it is installed, and the first-week findings follow a pattern we now consider routine. The most common headline: the estate is far bigger than anyone believed.

Russell’s favourite example is our own. “When we plugged it into MIP’s estate, most of us thought we had 30 or 40 reports. We had about 1,200.” That discovery shock repeats at client after client, thousands of reports and semantic models nobody knew existed, refreshing on schedules nobody reviews, consuming capacity nobody costed.

The other first-week findings:

  • Access surprises. Who holds admin rights, in which workspaces, and whether the admin-to-user ratio makes any sense. It usually does not.
  • Licence waste. Users sitting on paid licences their actual usage does not justify, some of whom can move to free licences. This finding alone has a habit of funding the tool.
  • Abandoned content. Reports and models with no users, still refreshing, still consuming capacity that could be reclaimed.
  • Personal gateways. Data pipelines running from an individual’s laptop. When that person leaves, those models silently stop refreshing. Finding these early is pure risk reduction.

After a few weeks, the machine-learning-driven usage analysis matures and the estate moves from visibility to action: rights-sizing admin roles, downgrading licences, retiring dead content, closing risky gateways.

How does a Sentinel deployment work?

This is usually the shortest conversation in the sales cycle, because there is very little to it. Sentinel is SaaS, so there is nothing to build. Deployment means granting it access to your Power BI tenant via Microsoft Entra, opening the firewall connection, and providing two things in your own environment: a SQL database for the data model, and storage for backups.

Two architectural points matter to Australian risk teams. First, there is an Australian instance, the service runs onshore. Second, Sentinel is metadata-driven: your BI data and your audit history do not go into the vendor’s cloud. They land in the SQL database inside your own estate. The enriched usage model Sentinel builds is yours, to report on, to analyse, or to feed into your machine learning and AI work.

Day one is connectivity. Within the first week, usage data is accumulating and the discovery findings start landing. Within a month, usage patterns are established and the estate is being actively managed instead of guessed at.

Can’t we just build this ourselves with the APIs?

The most common reason a Sentinel conversation stalls, and a fair question, so here is the fair answer. Yes, the same APIs are available to you. What the do-it-yourself estimate always misses is everything after the API call. Sentinel does not just pull raw events: it enriches them with calculations and business rules, builds a proper data model, keeps that model refreshed on a managed schedule, runs the backup and disaster recovery engine, and keeps all of it working every time Microsoft changes the platform underneath, with a full-time development team maintaining it.

Then there is what we call key-person risk. Some organisations do have an administrator who knows this territory back to front. Russell’s caution comes from watching what happens next: “These experts leave the company, and then you’ve got a big hole to fill.” A product survives resignations. A folder of one person’s scripts does not.

How does Sentinel relate to Microsoft Purview?

They are complementary, and it is worth being precise because the two get conflated. Purview provides broad governance across your entire data estate, cataloguing, classification, estate-wide lineage, and it usefully extends activity log retention. Sentinel provides Power BI-specific depth: continuous auditing, granular estate visibility, change tracking, backups and recovery. Broad plus deep is the pattern that holds up, and it is the same guidance we give in our full Purview explainer.

How do you buy Power BI Sentinel in Australia?

Power BI Sentinel is developed by Purple Frog Systems in the UK. In Australia and New Zealand, MIP is the exclusive distribution partner so local implementations, licensing and support run through us, including for other consulting firms. For clients, that means the people deploying the tool are the same people who govern Power BI estates for a living, and support sits in your timezone.

One honest qualifier: Sentinel governs Power BI and Fabric. If your analytics runs elsewhere, Sentinel is not your answer yet, though migrating estates onto Power BI is work we do regularly.

Frequently asked questions

What is Power BI Sentinel in simple terms?

Power BI Sentinel is a SaaS governance tool for Power BI and Fabric. It gives you a live picture of your entire estate, a permanent audit trail of who did what, automated backups with change tracking, and the ability to restore previous versions of reports and semantic models.

Is Power BI Sentinel a Microsoft product?

No. It is developed by Purple Frog Systems and works alongside Microsoft’s own tools, connecting to your tenant via Microsoft Entra. It complements Microsoft Purview rather than competing with it.

What is the difference between Power BI and Power BI Sentinel?

Power BI is the reporting and analytics platform where dashboards are built and consumed. Power BI Sentinel is the governance layer over the top: it monitors, audits, backs up and helps you administer everything your teams build in Power BI.

Does Power BI Sentinel see my report data?

Sentinel is metadata-driven. Your BI data and audit history stay in your own environment, stored in a SQL database you control, and the service offers an Australian instance. The usage model it builds belongs to you.

How long does Power BI Sentinel keep audit data?

For as long as you need. This matters because the Power BI activity log API provides 28 days of history and Purview audit retention defaults to 180 days. Sentinel collects continuously from installation with no forced expiry.

Do I need Power BI to use Sentinel?

Yes. Sentinel governs Power BI and Microsoft Fabric estates, so the platform is a prerequisite. Organisations on other BI tools would migrate to Power BI first, which MIP also delivers.

Russell is Group Consulting Director at MIP and has spent 25 years in data and analytics. If any of the four problems above sounded familiar, the fastest way to find out what is really in your estate is to switch Sentinel on and look. Talk to us. 

Share this post