1import{j as a}from"./index-BmmDLC6A.js";import{I as e}from"./IntegrationDetailLayout-D-tN8GAA.js";import{g as i}from"./integrations-rIPA8gGQ.js";import{d as o,D as r}from"./Navigation-CZqnNp_G.js";import{T as n}from"./trending-up-DcgvuuEe.js";import{S as s}from"./shield-check-B3jGQaNd.js";import{R as c}from"./receipt-CgvER212.js";import{C as p}from"./chart-column-BBeTxKgJ.js";import"./Footer-D9oToavW.js";import"./gemini-CCG4WpZS.js";import"./link-2-NiDdCzzV.js";import"./circle-check-CwDFWA_r.js";import"./microsoft-copilot-8g02ldo7.js";import"./langfuse-5_SES_5z.js";function S(){const t=i("microsoft-fabric");return a.jsx(e,{slug:t.slug,name:"Microsoft Fabric",logo:t.logo,tagline:t.tagline,darkTile:t.darkTile,heroDesc:"Govern Microsoft Fabric capacity spend down to the workspace, artifact, and workload â tracking Capacity Units (CU), OneLake storage, and compute usage across Synapse, Data Factory, and Power BI.",whatItTracks:["Capacity Unit (CU) consumption across Fabric F-SKUs, reserved instances, and pay-as-you-go tiers","Compute spend across Synapse Data Warehouse, Spark Data Engineering, Data Factory, and Real-Time Analytics","OneL
1ake storage growth, disaster recovery replication, and cross-region egress costs","Interactive vs. Background operations, CU smoothing, and throttling risk detection","Cost allocation by Fabric workspace, capacity, domain, and tenant","Copilot in Microsoft Fabric usage and AI capacity allocation"],benefits:[{icon:o,title:"CU-Level Transparency",desc:"Gain full visibility into Capacity Unit consumption per workload, pipeline, and notebook."},{icon:n,title:"Capacity Forecasting",desc:"Forecast future Fabric capacity needs based on workload patterns and seasonal spikes."},{icon:s,title:"Smoothing & Throttling Guardrails",desc:"Monitor 24-hour CU burn rates to prevent capacity overload and interactive query throttling."},{icon:c,title:"Workspace Chargeback",desc:"Accurately attribute Fabric costs to business units, domains, and project teams."},{icon:r,title:"OneLake Storage Optimization",desc:"Track delta table storage and identify redundant datasets to optimize OneLake spend."},{icon:p,title:"Anomaly Detection",desc:"Instantly detect runaway Spark jobs, long-running pipelines, or rogue queries."}],setupSteps:[{step:"01",title:"Connect",desc:"Grant read-only access via Azure App Registration and Fabric Admin APIs."},{step:"02",title:"Sync",desc:"Finomics ingests Fabric capacity metrics, workspace activity, and Azure billing telemetry."},{step:"03",title:"Attribute",desc:"Map Fabric capacities, domains, and workspaces to teams and cost centers."},{step:"04",title:"Govern",desc:"Set CU budgets, smoothing threshold alerts, and capacity rightsizing policies."}]})}export{S as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.