Frequently Asked Questions
Everything you need to know about SpendWeave and Microsoft Fabric cost management.
FAQ answers
How does BYON (Bring Your Own Network) security work?
Our Pro tier allows you to deploy the FinOps scanner directly within your own VNet. We never extract raw data out of your environment. We only ingest aggregated metadata and cost telemetry necessary for analysis, ensuring your sensitive Fabric artifacts remain secure and compliant.
How do you bypass the standard 14-day retention limit in Fabric?
Fabric natively retains detailed capacity telemetry for only 14 days. Our platform continuously captures the Capacity Metrics semantic model — the same source Microsoft's own monitoring app reads — into an Eventhouse/KQL vault that you can query directly, building a long-term historical baseline. This enables year-over-year cost comparisons and seasonal trend analysis without manual re-exports. Enrichment from Activity Events is on the roadmap.
What is CU rounding logic and why does it matter?
Microsoft Fabric bills based on Capacity Units (CUs). However, short-running jobs or specific engine types are subject to minimum billing durations (rounding logic). Our analysis surfaces cost-per-operation outliers — workloads where you are paying for unused capacity due to rounding — so you know where batching or scheduling changes will save money.
What is Active Orchestration?
Available in the Enterprise tier, Active Orchestration allows the platform to automatically pause, resume, or scale your Fabric capacities based on schedules or usage thresholds, directly interfacing with the Azure Management API via SPN. This moves beyond alerting to automated cost remediation.
Ready to take control of your Fabric spend?
Join data teams optimizing their cloud costs with intelligent, automated insights.