Data loss prevention policies for Power BI
To help organizations detect and protect their sensitive data, Power BI supports Microsoft Purview Data Loss Prevention (DLP) polices. When a DLP policy for Power BI detects a sensitive semantic model, a policy tip can be attached to the semantic model in the Power BI service that explains the nature of the sensitive content, and an alert can be registered on the data loss prevention Alerts page in the Microsoft Purview compliance portal for monitoring and management by administrators. In addition, email alerts can be sent to administrators and specified users.
This article describes how DLP in Power BI works, lists considerations and limitations as well as licensing and permissions requirements, and explains how DLP CPU usage is metered. For further information, see:
- Configure a DLP policy for Power BI to see how to configure DLP policies for Power BI.
- Respond to a DLP policy violation in Power BI to see how to respond when a policy tip tells you your semantic model has a DLP policy violation.
Considerations and limitations
- DLP policies for Power BI are defined in the Microsoft Purview compliance portal.
- DLP policies apply to workspaces. Only workspaces hosted in Premium capacities are supported.
- DLP semantic model evaluation workloads impact capacity. See CPU metering for DLP policy evaluation for more information.
- DLP policy templates aren't yet supported for Power BI DLP policies. When creating a DLP policy for Power BI, choose the "custom policy" option.
- Power BI DLP policy rules currently support sensitivity labels and sensitive info types as conditions.
- DLP policies for Power BI aren't supported for sample semantic models, streaming datasets, or semantic models that connect to their data source via DirectQuery or live connection. This includes semantic models with mixed storage, where some of the data comes via import-mode and some comes via DirectQuery.
- Exact data match (EDM) classifiers and trainable classifiers aren't supported by DLP for Power BI. If you select an EDM or trainable classifier in the condition of a policy, the policy will yield no results even if the semantic model does in fact contain data that satisfies the EDM or trainable classifier. Other classifiers specified in the policy will return results, if any.
- DLP policies for Power BI aren't supported in the China North region. See How to find the default region for your organization to learn how to find your organization's default data region.
Licensing and permissions
SKU/subscriptions licensing
Before you get started with DLP for Power BI, you should confirm your Microsoft 365 subscription. The admin account that sets up the DLP rules must be assigned one of the following licenses:
- Microsoft 365 E5
- Microsoft 365 E5 Compliance
- Microsoft 365 E5 Information Protection & Governance
Permissions
Data from DLP for Power BI can be viewed in Activity explorer. There are four roles that grant permission to activity explorer; the account you use for accessing the data must be a member of any one of them.
- Global administrator
- Compliance administrator
- Security administrator
- Compliance data administrator
CPU metering for DLP policy evaluation
DLP policy evaluation uses CPU from the premium capacity associated with the workspace where the semantic model being evaluated is located. CPU consumption of the evaluation is calculated as 30% of the CPU consumed by the action that triggered the evaluation. For example, if a refresh action costs 30 milliseconds of CPU, the DLP scan will cost another 9 milliseconds. This fixed 30% additional CPU consumption for DLP evaluation helps you predict the impact of DLP policies on your overall Capacity CPU utilization, and perform capacity planning when rolling out DLP policies in your organization.
Use the Power BI Premium Capacity Metrics App to monitor the CPU usage of your DLP policies. For more information, see Use the Microsoft Fabric Capacity Metrics app.
Note
Users with PPU licenses do not incur the DLP policy evaluation costs described above, as these costs are covered for them up front by their PPU license.
How do DLP policies for Power BI work
You define a DLP policy in the data loss prevention section of the compliance portal. In the policy, you specify the sensitivity labels and/or sensitive info types you want to detect. You also specify the actions that will happen when the policy detects a semantic model that contains sensitive data of the kind you specified. DLP policies for Power BI support two actions:
- User notification via policy tips.
- Alerts. Alerts can be sent by email to administrators and users. Additionally, administrators can monitor and manage alerts on the Alerts tab in the compliance portal.
When a semantic model is evaluated by DLP policies, if it matches the conditions specified in a DLP policy, the actions specified in the policy occur. A semantic model is evaluated against DLP policies whenever one of the following events occurs:
- Publish
- Republish
- On-demand refresh
- Scheduled refresh
Note
DLP evaluation of the semantic model does not occur if either of the following is true:
- The initiator of the event (publish, republish, on-demand refresh, scheduled refresh) is an account using service principal authentication.
- The semantic model owner is a service principal.
What happens when a semantic model is flagged by a Power BI DLP policy
When a DLP policy detects an issue with a semantic model:
If "user notification" is enabled in the policy, the semantic model will be marked in the Power BI service with a shield that indicates that a DLP policy has detected an issue with the semantic model.
Open the semantic model details page to see a policy tip that explains the policy violation and how the detected type of sensitive information should be handled.
Note
If you hide the policy tip, it doesn’t get deleted. It will appear the next time you visit the page.
If alerts are enabled in the policy, an alert will be recorded on the data loss prevention Alerts page in the compliance portal, and (if configured) an email will be sent to administrators and/or specified users. The following image shows the Alerts page in the data loss prevention section of the compliance portal. To get to the Alerts page, in the compliance portal, expand the Data loss prevention solution and choose Alerts.
Monitor and manage policy alerts
Log into the Microsoft Purview compliance portal, expand the Data loss prevention solution, and choose Alerts.
Select an alert to start drilling down to its details and to see management options.