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
Get Secret from Azure Key Vault using Fabric Workspace Identity
Users can access key vault secrets using notebookutils.credentials.getSecret. This is based purely on the user's access (or object owner's access, if the notebook is being run in a pipeline). In larg...sean_cochran5 hours agoResolver INew3.2KViews14likes4CommentsPer-visual Data Freshness Badge with configurable staleness alerts
Problem: Report consumers can’t tell whether the data behind a specific visual is current. Page-level “last refreshed” workarounds ignore that different tables refresh on different schedules, which l...gopinathtk14 hours agoNew MemberNew1View1like0CommentsNative Master Data Management Solution
Microsoft Fabric currently lacks a native Master Data Management (MDM) capability, creating a gap for organizations that need to manage and govern business-critical reference data such as customers, ...bradcoles15 hours agoRegular VisitorNew314Views1like4CommentsAllow Power BI subscriptions to use a no-reply sender instead of the subscription owner's mailbox
Following the migration to the new email delivery platform, subscription emails now appear to come from the subscription owner. This generates large volumes of Out of Office replies, auto-replies, an...tm8215 hours agoNew MemberNew90Views19likes3Comments