Skip to content
BI Pixie Workload in Microsoft Fabric
Generally Available

Account

In the Account view of the BI Pixie item, you can see your BI Pixie subscription and how much of your plan you are using. Every BI Pixie user can open the Account view, admins included. The SAS Token on the Account view belongs to the license you are assigned to, and a BI Pixie admin sees the Token of the default license.

Microsoft Fabric handles identity and sign-in, so your Microsoft Entra ID identity comes from Fabric. Data Residency describes where BI Pixie stores your telemetry and how you can keep it in your own OneLake. For how BI Pixie uses the dashboard data source SAS Token, see Set up BI Pixie Dashboard.

Account Info

Account Info displays your name and email (from your Microsoft Entra ID identity), and the subscription that is currently entitling this BI Pixie item. On the Enterprise plan with multiple licenses, the license assigned to you is also shown.

If a payment has failed (past-due status), a Payment failed banner appears at the top of the Account view with a link to Update payment method. For subscriptions billed through Azure Marketplace, this link is replaced with Check Azure Billing, which opens the Azure portal where you can manage the SaaS subscription.

Screenshot: Account view in the BI Pixie item showing subscription summary and Plan & Usage.

Plan Usage

In the Plan Usage section of the Usage tab, you can see your current subscription and how much of your plan you have used.

Subscription Information

Subscription Information gives your plan (for example, the Pro plan), its start date, and its renewal or expiry date. BI Pixie admins upgrade or downgrade the plan on the Plan tab of the Account view, and can also manage the subscription in the BI Pixie subscription portal. For full details on plans, see Licenses.

License Utilization

A progress bar shows the one quantity your plan is measured by:

  • Tracked Items Used. The number of tracked items in use out of your plan's allowance. A tracked item is a report with Pixies, or a semantic model or data agent you are preparing for AI. On the Free plan, reports are counted separately from semantic models and data agents, and on every other plan they share one count. A tracked item keeps counting after you remove a report's Pixies or delete the item. To read how tracked items are counted, select the info icon.
  • Claude queries today. On the Free plan, this tile shows how many queries Claude ran on your semantic models through BI Pixie's cloud today, out of the 25 a Free account has each day. Everyone in the account shares the count, and it starts again at midnight UTC, shown in your own time. Queries from the BI Pixie MCP server on a person's own computer never reach BI Pixie and are not counted. Paid plans have no daily limit and show no tile.

Limits

  • Full data reloads. The number of full reloads of your dashboard data run today, against your plan's daily limit. A full reload reads your entire telemetry history again, and ordinary incremental refreshes are not counted or limited.

Enforcement Banners

When usage thresholds are reached, banners appear in the Plan Usage section:

  • Usage limit warning. You are approaching your plan's usage limits, and BI Pixie pauses event collection if usage keeps rising.
  • Data refresh access blocked. You have used today's refresh limit, and the banner gives an estimated time when refresh becomes available again.

BI Pixie admins also see a link to manage billing in the Plan Usage section: Manage in Azure for a subscription billed through Azure Marketplace, or Billing & Invoices for a subscription paid by card.

Your cost is always fixed: BI Pixie has no usage meters and no overage charges, and how heavily your audience uses your reports never changes your bill. Every plan includes a fair-use session allowance. Going past the allowance never results in a charge, and Above the Fair-Use Allowance describes what happens when usage goes over it. With data residency your telemetry lands in your own OneLake, and there is no session quantity to meter at all.

How BI Pixie identifies report viewers

In the Features and data kept section of the Account view, a BI Pixie administrator chooses how BI Pixie identifies the people who view your reports. Each license has its own choice, and changing the choice for one license does not change the others. A member who is not an administrator sees the choice for their own license and cannot change it.

The section starts closed, and its heading says how many licenses it covers. Select How BI Pixie identifies report viewers to open it. Each license has its own card with the three choices below.

The choice applies only while Capture user identity is on in Tracking Setup. That setting is off for every new account. While it is off, BI Pixie collects no user names, whichever choice is made, and counts viewers by a masked IP address.

  • Email address is the default. BI Pixie stores each viewer's Power BI user name, which is usually their email address, and your reports can show who viewed what.
  • Masked user names stores a masked ID made with a secret key held for the license. The ID cannot be turned back into the user name without that key, and it ends in @masked.bipixie.
  • Not collected stores no identity. BI Pixie groups viewers by a masked IP address, which is less accurate when many viewers share a corporate network or a VPN.

A change applies to events recorded from then on, within 5 minutes, and Pixies do not need to be added again. Events already recorded keep the identity they were stored with, so the same person can appear twice in user counts for the period that spans the change.

Allowed Link Destinations in Managed Reports

When a report tracks link clicks, every link a viewer selects in it passes through BI Pixie on its way to the destination. With a list of allowed link destinations, you make sure those links open only to websites you trust. A link to any other website shows the viewer a short notice instead of opening.

Prerequisites

  • Your account is on the Enterprise plan. On other plans, the section offers Compare plans instead of the list.
  • You are an account admin. Members can see the list but cannot change it.
  • At least one report tracks link clicks, through Track clicks on links in Tracking Setup. A report that does not track link clicks opens no links through BI Pixie, so the list has no effect on it. When no report on the account tracks link clicks, the section says so and offers Open Tracking Setup.

Add allowed link destinations

  1. In the BI Pixie item, open the Account view and select the Security tab.
  2. In Allowed link destinations in managed reports, type a website name or an address prefix in Website or address prefix, and then select Add.
  3. Repeat for each destination. The list holds up to 200 destinations, and each can be up to 500 characters long.
  4. Select Save list. When you save the first entries, BI Pixie asks you to confirm, because links to every other website stop opening.

Your reports use the saved list within five minutes.

How an entry matches a link

  • A website name, such as contoso.com, matches every address on that website and on its subdomains, such as finance.contoso.com. It never matches a different website whose name merely contains it, such as notcontoso.com.
  • An address prefix that starts with https:// or http:// matches every address that begins with it. For example, https://contoso.sharepoint.com/sites/finance/ allows that SharePoint site and nothing else on SharePoint.

Remove a destination or clear the list

  1. Next to the destination, select the remove button.
  2. Select Save list.

When you save an empty list, links in reports that track link clicks open to any website again within five minutes.

Considerations and limitations

  • One list applies to the whole account, across every license, workspace and report.
  • The list applies only to links that pass through BI Pixie, which are the links in reports that track link clicks. Other links in Power BI reports are ordinary links, and the list does not affect them.
  • Viewers do not see which destinations are allowed. A blocked link shows them a notice page instead.
  • If BI Pixie cannot load or save the list, your reports keep using the list that was last saved.
  • If your account moves to a plan below Enterprise, BI Pixie keeps the saved list but stops applying it. The list applies again if the account returns to Enterprise. See Plans.

API and connectors

People in your account can use BI Pixie from scripts that call the BI Pixie API and from connectors, such as BI Pixie in Claude, that act for them. With the API and connectors setting, you decide whether your account allows that at all. When you turn it off, BI Pixie refuses those calls for everyone in your account, and nobody has to remove a script or disconnect a connector first.

Prerequisites

  • You are an administrator of your BI Pixie account. Members can see the setting but cannot change it.

Turn off the BI Pixie API and connectors

  1. Open the Account view and select the Security tab.
  2. In API and connectors, turn off Allow the BI Pixie API and connectors.
  3. In Turn off the BI Pixie API and connectors?, select Turn off.

The change applies to the next call each script or connector makes, including scripts that run on a schedule.

Turn the BI Pixie API and connectors back on

  1. Open the Account view and select the Security tab.
  2. In API and connectors, turn on Allow the BI Pixie API and connectors.

BI Pixie does not ask for confirmation when you turn the setting on, and calls are accepted again from the next one.

What people see while the setting is off

  • A script or AI agent that calls BI Pixie receives this message: "Your organization has turned off access to BI Pixie from scripts and AI agents. An administrator of your BI Pixie account can turn it on in Account settings."
  • On the AI Assistants page, the Use the BI Pixie API card says that your organization has turned off the BI Pixie API and connectors.
  • The Use BI Pixie MCP Server card says that BI Pixie refuses changes from AI agents while the BI Pixie API and connectors are turned off, and that questions about usage still work.
  • Administrators also see Change this in Account settings on both cards, which opens the setting.

Considerations and limitations

  • One setting applies to everyone in the account, administrators included, across every license.
  • The setting does not stop anyone from using BI Pixie in the BI Pixie workload in Fabric.
  • The BI Pixie MCP server can still answer usage questions while the setting is off. Those questions read the BI Pixie semantic model through Power BI, with the person's own access, and do not call the BI Pixie API.
  • The setting does not change what a person can reach while it is on. A script or connector acts with the same access as the person it acts for.
  • BI Pixie records each change to the setting, with who made it and when.

Claude queries through BI Pixie's cloud

When someone adds the BI Pixie connector in Claude's Connectors settings, on claude.ai or in another Claude app, Claude runs queries on your semantic models as that person, with their row-level security, and the results pass through BI Pixie's cloud on the way to Claude. The BI Pixie MCP server on a person's own computer runs its queries there instead, so its results never pass through BI Pixie's cloud. If your organization's policy does not allow a vendor's cloud to handle query results, you can turn off Allow Claude to query through BI Pixie's cloud, a second switch inside API and connectors.

Turn off Claude queries through BI Pixie's cloud

  1. Open the Account view and select the Security tab.
  2. In API and connectors, turn off Allow Claude to query through BI Pixie's cloud.
  3. In Turn off Claude queries through BI Pixie's cloud?, select Turn off.

To turn it back on, turn on the same switch. BI Pixie does not ask for confirmation when you turn it on.

While it is off, Claude still gets everything else BI Pixie offers it:

  • BI Pixie on a person's own computer still runs queries.
  • Claude can still read which fields and values people use in your reports, the Report usage and Prep for AI context that make its answers better.
  • Claude benchmarks still run.

On the AI Assistants page, the Use BI Pixie MCP Server card says that your organization has turned off Claude queries through BI Pixie's cloud, so people in your account learn it before Claude refuses a query. Administrators also see Change this in Account settings.

The switch depends on Allow the BI Pixie API and connectors. While that switch is off, BI Pixie already refuses every call from a connector, so this switch cannot be changed. It keeps its position and applies again when the API and connectors are turned back on.

Related content

Pixies Missing Emails

BI Pixie emails every admin of your account when it has received no usage for seven days from a report it used to receive usage from. A report goes quiet like this when someone publishes it again without its Pixies, and also when nobody opens it for a week, so the email names the missing Pixies as the likely cause rather than the certain one. Members of the account do not receive the email.

Turn the email on or off

  1. In the BI Pixie item, open the Account view and select the Overview tab.
  2. In Email notifications, turn Email the admins when BI Pixie stops receiving usage from a report on or off. BI Pixie saves the change at once.

The email is on for every new account.

Considerations and limitations

  • The setting applies to the whole account. Only an account admin can change it. Members see it with an Admins only label.
  • BI Pixie shows the Pixies Missing status on the report's row in Managed Reports whether this email is on or off.
  • BI Pixie does not receive the usage of a report whose usage goes to your own backend, so it does not email you about that report. When every license on the account sends usage to your own backend, the setting is shown but cannot be changed.

Dashboard Data Source

BI Pixie uses this SAS Token for the OneLake shortcut that points your lakehouse at your telemetry. The semantic model behind your BI Pixie Dashboard is connected to that lakehouse with Direct Lake, so there is no credential for you to enter anywhere. The Dashboard Data Source card shows a single SAS Token (masked by default). To reveal it, select Show. To copy it, select Copy Token. To issue a new Token, select Rotate SAS (BI Pixie admins only).

You do not paste the SAS Token anywhere to install the dashboard. When you rotate the SAS Token, BI Pixie moves the OneLake shortcut behind your BI Pixie Dashboard to the new Token, so rotating does not interrupt the dashboard. For the full walkthrough, see Set up BI Pixie Dashboard.

Data Residency: Store Your Data in Your Own OneLake

By default, BI Pixie stores your raw telemetry in the BI Pixie cloud and gives your lakehouse a OneLake shortcut to it, and BI Pixie processes the telemetry with the BI Pixie ETL notebook on your own Fabric capacity. On the Enterprise plan, you can turn on Data residency to have your data kept instead in your own Microsoft OneLake, in the lakehouse of the workspace where your BI Pixie item is installed. Data residency covers new events and your AI Readiness work. When you turn data residency on, BI Pixie moves the assessments and benchmark runs you already have into your lakehouse. You keep full control of the data and can revoke access at any time. Processed dashboard data lives in your Fabric workspace either way.

The Data residency card on the Architecture view 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. BI Pixie delivers each license's data to a folder of its own in the OneLake of the workspace where that license's BI Pixie item lives.

Accounts on the Enterprise plan also have a third option: Bring Your Own Storage (BYOS), where you run BI Pixie on Azure (BI Pixie's self-hosted edition) and keep telemetry in your own Azure Data Lake Storage account so events never enter BI Pixie infrastructure. See BYOS in the Fabric Workload, or the Data Residency overview for a side-by-side of all three storage options.

Turning on data residency takes three steps in the Data residency card: you grant a one-time consent, choose what happens to undelivered events, and confirm. For the full walkthrough, delivery health, and how to switch back, see Data Residency: Store Your Data in Your Own OneLake.

Subscription Management

BI Pixie admins change the plan on the Plan tab of the Account view. You can also manage plan changes, billing provider switches, payment methods, and cancellations in the BI Pixie subscription portal. A single BI Pixie subscription covers every BI Pixie product, so any changes you make there apply to your BI Pixie items in Microsoft Fabric automatically.

Removing BI Pixie from a Workspace

To stop using BI Pixie in a workspace, remove Pixies from your tracked reports (see Managed Reports), then delete the BI Pixie item from the workspace using Fabric's standard item-delete action. Deleting the item stops tracking. You delete the telemetry data permanently from Data Management.

Related Resources

  • Data Management: Configure data retention and manage user privacy.
  • Team Access: How Fabric workspace roles control BI Pixie access.
  • Licenses: Subscription tiers and Enterprise license assignment.
  • Set up BI Pixie Dashboard: What BI Pixie installs in your workspace, how to load your data, and how to keep it fresh.

What's Next

  • Contact Support: Get help with account or billing issues.
  • FAQ: Answers to common questions.