For Fabric Admin Add configurable background operations utilization alert to Fabric Capacity
Summary
Microsoft Fabric currently alerts administrators only when overall capacity hits 100 percent. However, this alert is typically triggered by short-lived interactive operation spikes, which resolve quickly and rarely pose long-term risk. The real operational threat comes from high background operations utilization, which runs continuously and can quietly consume capacity over a 24-hour rolling window. Fabric should introduce a separate, configurable alert for background operations thresholds to support proactive capacity management.
Problem
Interactive workload spikes—such as report queries or user-driven actions—may momentarily push capacity to 100 percent, but they are brief and predictable. Capacity typically stabilizes once user activity subsides.
Background operations behave differently:
They run on a continuous 24-hour rolling cycle
They accumulate load instead of dropping off quickly
They can slowly consume large portions of available capacity
They can create sustained, system-wide throttling long before admins realize there is a problem
By the time the current 100 percent alert fires, background utilization has often been building for hours, and remediation options are limited.
Proposed Solution
Introduce a dedicated admin alert that triggers when background operations utilization exceeds a configurable percentage threshold (e.g., 40%, 60%, 80%). Key characteristics:
Separates background consumption from interactive spikes
Provides early warning before a choke point occurs
Supports proactive workload scheduling and capacity planning
Reduces the likelihood of long-lasting throttling scenarios
Why This Matters
High background utilization is a slow-burn risk that impacts the environment across the entire day. Without visibility into rising background load, admins cannot intervene early enough to prevent throttling or degraded user experience.
In short:
Interactive spikes = noise
Background operations = signal
Fabric’s alerting model should reflect this difference to ensure stable and predictable capacity performance.
Requested Outcome
Add a configurable background operations utilization alert to Microsoft Fabric Capacity to enable proactive governance and avoid sustained system throttling.
Recent ideas
Shell/Console/Terminal for Fabric CLI, etc. in Fabric Portal
Regularly, when I start working for a client, I'm unable to use Fabric CLI due to device compliance issues. I don't want my consulting laptop to join their domain. I just want to be able to use Fab...PeterDaniels1 hour agoAdvocate IIINew3Views0likes0CommentsFile level commit - Need the ability to edit the commit description
I tried the recently announce file level commit for Fabric items. One notable issue I have with the feature (testing this with a Fabric warehouse, I'm assuming this would hold true for other items): ...DataBard13 hours agoMost Valuable ProfessionalNew36Views0likes3CommentsAdd the known commit ID by the "updates" subtab
Often I have a git commit that I want to sync into a fabric workspace, today I never know if the browser tab has actually picked up the latest commit or if it is going to throw an error on conflicts-...T-Rez13 hours agoAdvocate INew9Views0likes1Comment