Skip to content
BI Pixie Workload in Microsoft Fabric
Generally Available

Data Residency: Store Your Data in Your Own OneLake

By default, BI Pixie stores your raw engagement telemetry in the BI Pixie cloud and provides it as a OneLake shortcut, so it then gets processed in your Fabric capacity. With Data residency, you can instead have your data kept in your own Microsoft OneLake, in the lakehouse of the workspace where your BI Pixie item is installed. That covers the events BI Pixie collects and the AI Readiness work you do on them. This keeps your telemetry inside your Fabric tenant, governed by your own capacity and tenant policies, which is what teams with data-sovereignty or regulatory requirements need. You keep full control and can switch back at any time.

Your processed dashboard data lives in your Fabric workspace either way. Data residency changes where the rest of your data rests: the BI Pixie cloud (the default) or your own OneLake. It covers your raw events, and it covers your AI Readiness assessments and benchmark runs.

Choosing where your data is stored

You manage this from the Architecture view of the BI Pixie item. The Data residency card shows two options side by side: BI Pixie cloud (the default) and Your OneLake. The choice is account-wide and applies to every license on your account. Each license delivers to its own per-license folder in the OneLake of the workspace where that license's BI Pixie item lives.

If you would rather keep the raw telemetry data in your own Azure storage outside Fabric entirely, Enterprise accounts can use Bring Your Own Storage (BYOS) instead. See the Data Residency overview for a side-by-side of all three storage options.

Turning it on

A BI Pixie admin (workspace admin) enables delivery to OneLake in three steps from the Data residency card:

  1. Grant access. A one-time consent provisions the BI Pixie Delivery app in your tenant so it can write to your OneLake. Your admin approves it once, and you can revoke it at any time.
  2. Choose what happens if delivery is interrupted. BI Pixie retries delivery for 72 hours. You pick what happens after that: undelivered events are deleted (maximum privacy, and the default), or BI Pixie keeps them for the number of days you choose, from 1 to 30, and then deletes them.
  3. Confirm. New events begin flowing to your lakehouse, and BI Pixie starts moving the AI Readiness work you already have. Your dashboard history resets: events collected before now stay in the BI Pixie cloud and are not moved.

For your events, enabling is a fresh start rather than a migration. The lakehouse folder begins empty and fills from new events forward. This requires that the license powers a dashboard in exactly one workspace, because OneLake delivery targets one lakehouse.

Your AI Readiness work

Your assessments and benchmark runs are the one thing BI Pixie does move. They exist in only one place, so leaving them in the BI Pixie cloud would make the promise of data residency only partly true. When you turn data residency on, BI Pixie moves the ones you already have into your OneLake and stops keeping its own copies.

The Data residency card reports the move while it runs and tells you when it is finished, and you can open all of your AI Readiness work throughout. If BI Pixie cannot finish, the card says why. The two most common reasons are a paused Fabric capacity and a change to BI Pixie's access to your workspace, and BI Pixie continues on its own once either is resolved.

Delivery health

While delivery is active, the card shows a live health summary: whether events are delivering normally, how many are waiting, when the last delivery succeeded, and a warning if any events could not be delivered. If your Fabric capacity is paused, delivery pauses and resumes automatically when the capacity comes back. If BI Pixie's access to your lakehouse is removed, the card shows an access issue so you can restore it.

Undelivered events

When your lakehouse cannot accept events for more than 72 hours, BI Pixie follows the choice you made when you turned delivery on. If you chose to keep undelivered events, BI Pixie keeps them for up to the number of days you chose, 30 by default and 30 at most, counted from the end of the 72 hours. BI Pixie delivers the events it keeps as soon as delivery recovers, and deletes each kept event that reaches the limit. A deleted event cannot be delivered afterwards.

Two days before BI Pixie starts deleting kept events, every admin of your BI Pixie account receives an email. The email says how many events BI Pixie is keeping, the limit, and the date deletion starts.

An admin can change the choice and the number of days at any time from the Undelivered events tile, under delivery health, without turning delivery off. A member sees the setting and cannot change it. Switching from keeping events to deleting them deletes nothing that BI Pixie already keeps. Choosing fewer days deletes the kept events that are already older than the new number of days, and the tile says so before you save.

Switching back

You can switch back to the BI Pixie cloud at any time, and it takes effect immediately. You confirm once, and new events begin routing to the BI Pixie cloud right away; there is no waiting period and no second step. The dashboard link is restored for you as part of the same action. A few events that were in flight at the moment you switch may not be delivered.

Switching back keeps your dashboard whole. The events that were captured while delivery to your OneLake was on stay in your lakehouse, in a dated folder kept next to your telemetry folder (its name ends with -local- and the date you switched), and BI Pixie keeps reading them. Your dashboard continues to show the full history with no gap. Nothing is moved out of your OneLake, and your data is never deleted.

Your AI Readiness work stays where it is too. Your assessments and benchmark runs stay in your OneLake, where the files remain yours to open in Fabric. BI Pixie keeps read-only access to them there, so your AI Readiness lists keep showing them and you can still open them. BI Pixie copies nothing into the BI Pixie cloud and writes nothing to those folders. The card says this before you confirm.

BI Pixie does not copy that work back out of your OneLake, and there is no option to ask it to. Once your data is in your tenant it stays there, which is the point of data residency: moving it back into the BI Pixie cloud would undo the decision you made, and is usually the thing your own policy rules out.

If enabling is blocked

If a license appears to power a dashboard in more than one workspace, enabling pauses for a choice. Often the extra workspace was deleted but its record lingered, so the card first offers a one-click cleanup that removes records for workspaces that no longer exist, then retries. If you genuinely run BI Pixie in more than one active workspace, the card lists the workspaces you can access and lets you continue with the one you are currently in. OneLake delivery sends data to that single workspace, so the dashboards in the other workspaces stop receiving new data until you switch the account back to the BI Pixie cloud.

Where your telemetry lives in Fabric

Whether you use the BI Pixie cloud or your own OneLake, telemetry stored in Fabric sits in the same Azure region as the Fabric capacity that backs your workspace, and it participates in Microsoft Fabric's data plane like your other items:

  • Region and retention. Data rests in your capacity's region, and you control how long it is kept from Data Management.
  • Lineage and labels. The BI Pixie item participates in Fabric lineage, and you can apply Microsoft Information Protection sensitivity labels the same way you would for a lakehouse or semantic model.
  • Custom analysis. The supported way to query your telemetry is the BI Pixie semantic model. When events are delivered to your own OneLake, you can also reach them directly from your lakehouse for custom Spark or SQL work.

What's Next