What causes PowerBiSourceNotFoundOrInsufficientPermission?

The Power BI semantic model referenced by the Activator rule was deleted. Workspace permissions changed after the Activator object was connected — the Activator identity lost access. The semantic model was moved to a different workspace that the Activator cannot reach. The user who created the Activator rule lost access to the dataset and the rule runs under their identity

How do I fix PowerBiSourceNotFoundOrInsufficientPermission?

Check if the Power BI semantic model referenced by the Activator object still exists in its original workspace.. If the dataset exists, go to Settings > Manage access on the dataset and confirm the Activator identity has at least Viewer permissions.. If the dataset was deleted, delete the broken Activator objects and rules and recreate them on a replacement semantic model.

High severityfabricMicrosoft Fabric →

Microsoft Fabric Error:
PowerBiSourceNotFoundOrInsufficientPermission

What does this error mean?

Fabric Activator cannot access the Power BI semantic model associated with an alert or rule. The dataset was deleted after the alert was created, or permissions on the dataset were changed and the Activator identity no longer has access.

Common causes

1The Power BI semantic model referenced by the Activator rule was deleted
2Workspace permissions changed after the Activator object was connected — the Activator identity lost access
3The semantic model was moved to a different workspace that the Activator cannot reach
4The user who created the Activator rule lost access to the dataset and the rule runs under their identity

How to fix it

1Check if the Power BI semantic model referenced by the Activator object still exists in its original workspace.
2If the dataset exists, go to Settings > Manage access on the dataset and confirm the Activator identity has at least Viewer permissions.
3If the dataset was deleted, delete the broken Activator objects and rules and recreate them on a replacement semantic model.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1If workspace permissions changed, restore the Activator identity's access or reconnect the Activator object under a different identity with valid access

Frequently asked questions

Does this error affect Power BI reports in the same workspace?

Depends on the error type. Semantic model failures affect report freshness directly. Dataflow or pipeline failures may cascade into downstream semantic model failures.

How is debugging Fabric errors different from classic Power BI errors?

Fabric errors often require checking capacity utilization alongside the item-level error. The Fabric admin portal shows capacity pressure that Power BI Service doesn't expose.

Can Fabric errors be caused by capacity limits?

Yes — Fabric capacities have concurrent operation limits. An undersized capacity causes failures during peak usage.

Does this error appear in Power BI Desktop?

No — Fabric items are cloud-native. Desktop can connect to Fabric semantic models but cannot trigger or observe Fabric-specific errors.

Source · learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-troubleshooting