analytics, charts, graphs, traffic, marketing, internet, web, macbook, laptop, computer, technology, blue computer, blue technology, blue laptop, blue marketing, blue internet, blue web, charts, graphs, marketing, marketing, marketing, marketing, marketing, web
Photo by StockSnap on Pixabay

Data Governance

Part of BI access and data governance

Reviewing who can export detailed datasets in Power BI

Review detailed BI exports by purpose, permission route and effective access, then verify revoked or expired grants.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Governance.

undefined

Review detailed-data export in Power BI separately from report viewing. For each shared semantic model, identify people and groups with Build permission, the report's Export data setting, and any workspace role or app grant that can provide access. Compare those permissions with the approved audience, then remove grants that no longer serve the task.

Map Power BI detailed-data export routes

A chart may show an aggregate while an export or model connection exposes more detail. In Power BI, review report-visual exports to Excel, including underlying-data export, and access to shared semantic models through Build permission, Analyze in Excel or the XMLA endpoint. Classify each by output: visual summary, underlying records, connected spreadsheet or model connection. Include direct model access, group membership, workspace roles and app-publishing grants.

Ask the business owner to describe the need. A regional manager may need monthly sales totals; a reconciliation analyst may need transaction rows for an approved period. Those uses call for different detail levels and handling rules. If a recurring summary meets the task, it need not carry broad detailed-data access.

Review Power BI export permissions

Power BI report settings allow readers to export summarised or underlying visual data by default; Export data can restrict a report to summarised data or no export (Microsoft). Build permission is required to export underlying data and access the XMLA endpoint. Workspace Contributors have Build permission on their semantic models; Admins or Members can grant app users Build permission during app publishing. Row-level security restricts data access only for Viewers.

Review report settings alongside model and workspace permissions. Blocking export in one report does not establish what the same person can do through another report, a model connection or an elevated workspace role. Build permission alone does not prove that a particular report export will succeed: report settings, visual type and other limitations also matter.

Key Power BI Export Permissions and Controls

Default Export Setting
Summarised or underlying data allowed
Block Export Option
No export allowed (report setting)
Required for Underlying Data
Build permission on semantic model
Workspace Contributor Role
Includes Build permission
Row-Level Security Effect
Applies only to Viewers, not to users with Build permission

Record and verify Power BI export access

For each sensitive dataset, keep an entitlement register with the person or group, business purpose, approved detail level, grant route, approver, date granted and next review trigger. For Power BI, record the report's Export data setting and inspect shared semantic-model Build permissions, workspace roles and any Build permission granted through app publishing. Compare those entries with the approved audience, record exceptions and give temporary access an end date.

Where verification is appropriate, use representative accounts to test allowed and blocked routes in Power BI. Export from a report visual to Excel and inspect the file's columns and row population, not just whether an Export button appears. Include a Viewer subject to row-level security, an account with Build permission and one with an elevated workspace role; use data and an environment authorised for the check.

Report owners can classify and label reports with Microsoft Purview Information Protection sensitivity labels. If a label has protection settings, Power BI applies them to exported Excel, PowerPoint or PDF files; security and Power BI administrators can use Microsoft Defender for Cloud Apps to monitor user access and activity and configure a policy that prevents downloading sensitive Power BI data to unmanaged devices (Microsoft).

Revoke and recheck export access

When someone changes role or an approval expires, remove the underlying grants and verify the effective result. Check each grant route separately, including app permissions and semantic model Build permissions. Keep the decision and any unresolved exception so a future reviewer can tell why detailed export was allowed and whether it is still needed.

The OAIC says a data breach happens when personal information is accessed or disclosed without authorisation or is lost. If the Privacy Act 1988 covers your organisation or agency, you must notify affected individuals and the OAIC when a breach involving personal information is likely to result in serious harm (OAIC).

More from Data Governance