Data Residency

You own your engagement telemetry in every BI Pixie configuration. This page is the single place that explains the three ways your telemetry can be stored, helps you choose, and links to the step-by-step setup for each. Wherever your raw events rest, the BI Pixie experience (managing reports, adding Pixies, the dashboard, Event Viewer, and Data Management) stays the same.

The three storage options

BI Pixie storage

Default · all plans

A dedicated, RBAC-isolated Azure container that belongs to you alone, inside BI Pixie's Azure. We automatically place it in the region closest to your Power BI home, so there is nothing to configure and no other customer can reach it.

OneLake delivery

Microsoft Fabric

If you run BI Pixie inside Microsoft Fabric, new events are delivered straight to your own OneLake lakehouse in the workspace where your BI Pixie item lives. Your telemetry stays in your Fabric tenant; we do not retain it in our cloud.

How OneLake delivery works →

Bring Your Own Storage (BYOS)

Enterprise

Keep telemetry entirely in your own Azure Data Lake Storage Gen2 account. You run BI Pixie on Azure (BI Pixie's self-hosted edition), so events land directly in your account and BI Pixie never stores them. You optionally grant scoped, revocable read access for the in-product Data Management tools.

About BYOS →

BYOS is available on both BI Pixie surfaces: the BI Pixie Cloud portal and the Fabric Workload. OneLake delivery is specific to Microsoft Fabric.

Compare the options

  BI Pixie storage OneLake delivery BYOS
Where telemetry rests Your isolated container in BI Pixie's Azure Your own OneLake lakehouse Your own Azure Data Lake account
Telemetry web trigger Hosted by BI Pixie Hosted by BI Pixie, then delivered to you Hosted by you (BI Pixie on Azure)
Region control Auto-assigned to the region closest to your Power BI home Your Fabric capacity region Your Azure account, any region you choose
BI Pixie's access to the data Full (it is our storage) Read for delivery; revocable by you None, unless you grant scoped read access
Available on Cloud and Fabric Workload Fabric Workload Cloud and Fabric Workload
Plan All plans All plans (Fabric) Enterprise

Which should you choose?

  • Most teams: BI Pixie storage. Zero setup, full isolation, and the region is picked for you. This is the default and needs no decision.
  • On Microsoft Fabric and want telemetry in your own tenant: OneLake delivery. Events flow into your lakehouse so you can govern them with your Fabric capacity and tenant policies, while BI Pixie still operates the pipeline.
  • Strict data-residency or sovereignty mandates: BYOS. You run BI Pixie on Azure and host the storage yourself, so your telemetry never enters BI Pixie infrastructure at all. Choose BYOS when policy requires that raw events stay entirely within your boundary.

Deletion and retention

Who can delete your raw telemetry depends on where it rests:

  • BI Pixie storage. BI Pixie acts as your processor and runs the opt-in deletion and retention tools in Data Management on your behalf.
  • BYOS in the Cloud portal. Deletion is your own action: you may grant an optional read and delete tier so you can erase data yourself (for example, GDPR requests) from the in-product tools.
  • BYOS or OneLake delivery in the Fabric Workload. The data lives in your tenant, so deletion and retention run as customer notebooks on your own Fabric capacity. BI Pixie is never the one deleting.

Full processing terms for all three storage models are set out in our Data Processing Agreement.

What's Next