What causes TeamsAppBlockedInTenant?

The Microsoft Teams administrator blocked or did not allow the Fabric Activator app in the Teams Admin Center. A tenant-wide policy requires admin approval for third-party or Microsoft apps before they can be used. The Activator Teams app was previously allowed but was later blocked as part of a Teams governance review

How do I fix TeamsAppBlockedInTenant?

Ask your Microsoft Teams administrator to check the Teams Admin Center under Manage apps > Fabric Activator.. The admin should change the app's status from 'Blocked' to 'Allowed' for the tenant.. As a workaround while waiting for admin action, switch the Activator rule's alert delivery from Teams to email.

Medium severityfabricMicrosoft Fabric →

Microsoft Fabric Error:
TeamsAppBlockedInTenant

What does this error mean?

A Fabric Activator rule configured to send Teams alerts cannot deliver messages because the Fabric Activator Teams app has been blocked by a Teams administrator at the tenant level. All Activator-to-Teams notifications are silently dropped until the app is unblocked.

Common causes

1The Microsoft Teams administrator blocked or did not allow the Fabric Activator app in the Teams Admin Center
2A tenant-wide policy requires admin approval for third-party or Microsoft apps before they can be used
3The Activator Teams app was previously allowed but was later blocked as part of a Teams governance review

How to fix it

1Ask your Microsoft Teams administrator to check the Teams Admin Center under Manage apps > Fabric Activator.
2The admin should change the app's status from 'Blocked' to 'Allowed' for the tenant.
3As a workaround while waiting for admin action, switch the Activator rule's alert delivery from Teams to email.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1If your organization uses app permission policies, ensure the Fabric Activator app is included in the allowed list for the relevant users

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