BI Pixie Workload in Microsoft Fabric
Public Preview

Coming soon

This feature is part of the BI Pixie Workload's upcoming general availability release. The documentation is published in advance; the capability will be available once the Workload reaches GA.

Data Residency: Store Events in Your 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 new events delivered to your own Microsoft OneLake, in the lakehouse of the workspace where your BI Pixie item is installed. 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 your raw events rest: the BI Pixie cloud (the default) or your own OneLake.

Choosing where your events are stored

You manage this from the Account 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. Pick whether undelivered events are deleted (maximum privacy) or kept with BI Pixie until delivery recovers.
  3. Confirm. New events begin flowing to your lakehouse. Your dashboard history resets: events collected before now stay in the BI Pixie cloud and are not moved.

Enabling is a fresh start, not 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.

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.

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.

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