topic Re: How to stop rule firing in Activator

How to stop rule firing

sunil_sabat — Tue, 30 Dec 2025 16:22:53 GMT

I attached paid capacity now. I still get rule fired emails. How can I stop them?

Thanks

Sunil

Re: How to stop rule firing

v-aatheeque — Wed, 31 Dec 2025 13:18:04 GMT

Thanks for reaching out to Microsoft Fabric Community Forum.
It appears you’re still receiving rule-firing emails even after moving to a paid capacity. As a first step, please verify the following baseline checks, since alerts in Microsoft Fabric / Power BI can be configured at multiple levels:

Check the Power BI Service – Capacity Metrics App.
Open the capacity and turn off alert rules (CPU, Memory, Throttling).
In the Azure Portal → Azure Monitor → Alerts, locate alerts tied to the Power BI/Fabric capacity and disable or delete them.
Verify workspace settings to ensure the workspace is assigned to the paid capacity (not shared).
To help us pinpoint the source of these notifications, could you please confirm:
- Which alert type is firing (refresh failure, threshold/capacity metric ?
- How notifications are being sent (email, Teams, mobile), and whether those channels can be modified?

Re: How to stop rule firing

Mauro89 — Sat, 03 Jan 2026 07:47:12 GMT

Hi sunil_sabat,

as suggested by v-aatheeque @can you please give us some more context to your problem?
One of my last post was also about activator firing so Iam keen to help you out 😊

Best regards!

Re: How to stop rule firing

sunil_sabat — Sat, 03 Jan 2026 09:25:20 GMT

I recieved message like this, I clicked the Manage Rule link. It took me to RTI Rules tab. I clicked the rule to reset. Then the error went away. It seems to be related to async relation between change in capacities and built in Activator's capacity rules. Rule on capacity excess should auto reset if somebody moves from trial to paid. v-aatheeque please make a note of it.

Re: How to stop rule firing

v-aatheeque — Mon, 05 Jan 2026 09:51:09 GMT

Hi sunil_sabat

Thanks for the update! Happy to hear the issue is resolved after resetting the rule.