The Complete Guide to Microsoft Fabric Pricing (2026)
- doramadhusudan
- Jul 14
- 13 min read
Updated: 4 days ago
When you're evaluating Microsoft Fabric, pricing isn't just about the monthly bill - it's about understanding when this unified data platform delivers measurable return on your investment.
This comprehensive guide breaks down Microsoft Fabric's capacity-based pricing model, explains how to calculate your true costs, compares Fabric to alternatives like Azure Synapse and Databricks, and provides strategies to optimize spending while maximizing value.
By the end, you'll know exactly what Fabric costs, how to model your specific scenarios, and when the platform pays for itself.
Table of Contents
1. Microsoft Fabric Pricing Fundamentals
2. Understanding Capacity Units (CUs)
3. Complete Pricing Breakdown by SKU
4. Cost Modeling Scenarios
5. Microsoft Fabric vs Azure Synapse Pricing
6. Microsoft Fabric vs Databricks Pricing
7. The Fabric Pricing Calculator
8. Cost Optimization Strategies
9. When Microsoft Fabric Pays for Itself
10. Hidden Costs to Watch For
11. Real-World Pricing Examples
12. FAQs
Microsoft Fabric Pricing Fundamentals
Unlike traditional analytics platforms that charge separately for each service, Microsoft Fabric uses a unified capacity-based pricing model. You purchase compute capacity measured in Capacity Units (CUs), and that capacity powers all Fabric workloads - data engineering, warehousing, real-time analytics, data science, and Power BI.
The Three-Layer Cost Structure
Cost Component | What It Covers | Typical Monthly Range |
Capacity License | Compute power (CUs) for all workloads | $262.80 - $269,107+ |
OneLake Storage | Unified data lake storage | $0.023 - $0.246 per GB |
User Licenses (if capacity < F64) | Individual Power BI Pro/PPU licenses | $10 - $20 per user |
Key Pricing Principle: Fabric consolidates what were previously separate Azure bills (Synapse, Data Factory, Power BI Premium, storage) into a simpler, predictable capacity model.
Two Licensing Paths
Path 1: Capacity + User Licenses (F2 - F32)
- Buy: Fabric capacity (F2, F4, F8, F16, or F32)
- Plus: Individual Power BI licenses for each user
- Power BI Pro: $10/user/month
- Power BI Premium Per User (PPU): $20/user/month
- Best for: Small to mid-sized teams (< 50 users)
Path 2: Capacity Only (F64+)
-Buy: Fabric capacity F64 or higher
- Power BI licenses included for all users
- Best for: Organizations with 50+ users or enterprise workloads
Example Cost Comparison
Scenario: 50-user organization
Option A: F32 + User Licenses
- F32 capacity: $4,204.80/month
- 50 Power BI Pro licenses: $500/month
- Total: $4,704.80/month
Option B: F64 (licenses included)
- F64 capacity: $8,409.60/month
- Power BI licenses: Included
- Total: $8,409.60/month
Winner: Option A saves $3,704.80/month for this size organization.
Understanding Capacity Units (CUs)
Capacity Units (CUs) are the fundamental pricing dimension in Microsoft Fabric. Think of CUs as a pool of compute resources shared across all your Fabric workloads.
What Exactly Is a Capacity Unit?
One CU represents:
- 2 Spark VCores (virtual CPU cores for data engineering)
- 0.5 Power BI VCores (for semantic modeling and reports)
- Proportional memory and I/O bandwidth
Important: CUs are not directly comparable to Azure VMs or vCPUs - they're a normalized measure of Fabric-specific compute power.
How CUs Map to Real Workloads
Workload Type | How CUs Are Consumed |
Spark Jobs (Notebooks, Lakehouses) | 1 CU = 2 Spark VCores of processing |
Power BI (Semantic models, refreshes) | 1 CU = 0.5 Power BI VCore |
Data Pipelines (Data Factory) | Varies by activity; copy/move = 1-4 CUs per hour |
Data Warehouse (T-SQL queries) | Query complexity + concurrency determine CU draw |
Real-Time Analytics (KQL queries) | Event volume + query frequency |
Critical Insight: Unlike dedicated Azure resources, CUs are shared dynamically across all workloads in your capacity. A heavy Spark job temporarily reduces capacity available for Power BI refreshes.
Capacity Smoothing & Burst
Fabric uses capacity smoothing to handle temporary spikes:
- Short bursts (< 10 minutes) are allowed above your purchased CU limit
- The system averages usage over a rolling window
- Sustained overages trigger throttling (queue delays, slower refreshes)
Practical implication: You can run occasional heavy workloads without upgrading capacity, but consistent overuse requires a larger SKU.
Complete Pricing Breakdown by SKU
Microsoft Fabric offers 11 capacity SKUs, ranging from development/test environments to enterprise-scale deployments.
Full Pricing Table (US Pricing, Pay-as-You-Go)
SKU | Capacity Units (CUs) | Spark VCores | Power BI VCores | Hourly Cost | Monthly Cost(730 hrs) |
F2 | 2 | 4 | 0.25 | $0.36 | $262.80 |
F4 | 4 | 8 | 0.5 | $0.72 | $525.60 |
F8 | 8 | 16 | 1 | $1.44 | $1,051.20 |
F16 | 16 | 32 | 2 | $2.88 | $2,102.40 |
F32 | 32 | 64 | 4 | $5.76 | $4,204.80 |
F64 | 64 | 128 | 8 | $11.52 | $8,409.60 |
F128 | 128 | 256 | 16 | $23.04 | $16,819.20 |
F256 | 256 | 512 | 32 | $46.08 | $33,638.40 |
F512 | 512 | 1,024 | 64 | $92.16 | $67,276.80 |
F1024 | 1,024 | 2,048 | 128 | $184.32 | $134,553.60 |
F2048 | 2,048 | 4,096 | 256 | $368.64 | $269,107.20 |
Pricing as of January 2026, US East region. Prices vary by Azure region.
OneLake, Fabric's unified data lake, charges separately for storage:
Storage Tier | Cost per GB/Month | Use Case |
Standard | $0.023 | Active data, frequent access |
Cool | $0.01 | Infrequent access (< monthly) |
Archive | $0.002 | Long-term retention, rare access |
Important: OneLake uses the same Delta Lake format as Databricks, stored on Azure Data Lake Storage Gen2 (ADLS Gen2).
Capacity Reservation Discounts , Commit to 1 or 3 years for significant savings:
Commitment | Discount vs Pay-as-You-Go |
1-Year Reserved | ~20-25% savings |
3-Year Reserved | ~40-45% savings |
Example: F64 capacity
- Pay-as-you-go: $8,409.60/month
- 1-year reserved: ~$6,728/month (saving ~$1,681/month)
- 3-year reserved: ~$4,625/month (saving ~$3,784/month)
You're locked into that capacity level. If you scale down, you still pay the reserved rate.
Cost Modeling Scenarios
Let's model real-world scenarios to estimate your Fabric costs.
Scenario 1: Small Business - Reporting & Basic Analytics
Profile:
- 25 business users consuming reports
- 2 data engineers building pipelines
- 500 GB OneLake data
- Daily Power BI refreshes, weekly ETL jobs
Recommended SKU: F16
Monthly Cost Breakdown:
F16 Capacity: $2,102.40
25 Power BI Pro ($10): $250.00
OneLake (500 GB): $11.50
─────────────────────
TOTAL: $2,363.90/month
Why F16? Enough capacity for light-duty Spark jobs and multiple concurrent Power BI refreshes without throttling.
Scenario 2: Mid-Market - Data Engineering + BI
Profile:
- 100 report consumers
- 5 data engineers, 2 data scientists
- 5 TB OneLake data
- Daily data pipelines (2 hours Spark processing)
- 20 Power BI semantic models with hourly refreshes
Recommended SKU: F64
Monthly Cost Breakdown:
F64 Capacity: $8,409.60
Power BI licenses: Included
OneLake (5 TB): $115.00
─────────────────────────
TOTAL: $8,524.60/month
Why F64? First tier with included Power BI licenses. 128 Spark VCores handle moderate workloads comfortably.
Scenario 3: Enterprise - Real-Time Analytics + ML
Profile:
- 500 report users
- 15 data engineers, 8 data scientists
- 50 TB OneLake data
- Real-time event streams (1M events/hour)
- Continuous Spark jobs (24/7 processing)
- 50+ semantic models
Recommended SKU: F256
Monthly Cost Breakdown:
F256 Capacity: $33,638.40
Power BI licenses: Included
OneLake (50 TB): $1,150.00
─────────────────────────
TOTAL: $34,788.40/month
Why F256? 512 Spark VCores and 32 Power BI VCores handle enterprise concurrency and real-time processing without throttling.
Scenario 4: Comparison for 75-User Organization
Architecture A: Separate Azure Services (Legacy)
Azure Synapse (DW500c): $5,475/month
Azure Data Factory: $1,200/month
Power BI Premium (P1): $4,995/month
ADLS Gen2 (5 TB): $115/month
─────────────────────────────
TOTAL: $11,785/month
Architecture B: Microsoft Fabric (F64)
F64 Capacity: $8,409.60/month
OneLake (5 TB): $115.00/month
─────────────────────────────────
TOTAL: $8,524.60/month
SAVINGS: $3,260.40/month (28% reduction)
Key insight: Fabric consolidates services, reducing both cost and complexity.
Microsoft Fabric vs Azure Synapse Pricing
Microsoft Fabric evolved from Azure Synapse Analytics. Understanding the pricing differences helps you decide when to migrate.
Synapse Pricing Model
Azure Synapse has component-based pricing:
Component | Pricing Model |
Dedicated SQL Pool | Data Warehousing Units (DWUs): $1.20 - $360/hour |
Serverless SQL Pool | Pay per TB scanned: $5/TB |
Spark Pools | Node-hour pricing: $0.144 - $3.48/node-hour |
Pipelines | Per-activity: $0.001/activity + execution time |
Storage (ADLS Gen2) | $0.018 - $0.15/GB/month |
Complexity: Each component bills separately. Forecasting total cost requires tracking usage across all services.
Direct Comparison: DW500c vs F64
Azure Synapse Dedicated SQL Pool (DW500c):
- Compute: 500 DWUs
- Cost: $7.50/hour = $5,475/month (730 hours)
- Use case: Data warehousing only
Microsoft Fabric (F64):
- Compute: 64 CUs (128 Spark VCores, 8 Power BI VCores)
- Cost: $11.52/hour = $8,409.60/month
- Use case: Data warehousing + engineering + BI + real-time analytics
Fabric advantage: For $2,934.60/month more, you get a unified platform eliminating separate Data Factory, Power BI Premium, and Spark costs.
Total Cost of Ownership Comparison
Scenario: Mid-sized BI & analytics workload
Synapse Stack:
Dedicated SQL Pool (DW500c): $5,475/month
Spark Pool (2 nodes, 8 hrs/day): $1,152/month
Data Factory (pipelines): $800/month
Power BI Premium (P1): $4,995/month
ADLS Gen2 (5 TB): $115/month
───────────────────────────────────
TOTAL: $12,537/month
Fabric (F128):
F128 Capacity: $16,819.20/month
OneLake (5 TB): $115.00/month
───────────────────────────────────────
TOTAL: $16,934.20/month
DIFFERENCE: +$4,397/month (35% more)
BUT: The Fabric F128 provides double the compute (256 Spark VCores vs Synapse's limited Spark). Apples-to-apples, Fabric's unified model often costs less when you factor in:
- No separate Data Factory charges
- Included Power BI capacity
- Simplified management (1 service vs 4)
When to Choose Synapse Over Fabric
Stick with Synapse if:
1. You need dedicated SQL pool control (specific collations, advanced T-SQL features)
2. Existing Synapse Link integrations for Azure Cosmos DB or SQL Server 2022
3. Mapping Data Flows (not yet in Fabric—use Power Query or notebooks instead)
4. On-premises hybrid with Azure Arc is critical
The Fabric Pricing Calculator
Microsoft provides a Fabric Capacity Calculator to estimate costs, but it's limited.
Official Calculator Limitations
No direct pricing calculator exists yet
- Microsoft states: "Currently, there is no formula that can provide an easy upfront estimate of the capacity size you'll need. The best way to size the capacity is to put it into use and measure the load."
Trial-and-error sizing
- Start with a capacity, monitor usage, adjust
What's available:
- Azure Pricing Calculator (general Fabric SKU pricing)
- Capacity Metrics App (post-deployment usage tracking)
DIY Cost Estimation Formula
Step 1: Estimate Spark VCore-Hours/Month
Spark Hours = (Daily Notebook Runtime × 30 days) + (Pipeline Hours × Frequency)
Example:
- 2 notebooks, 3 hours/day each = 180 hours/month
- 5 pipelines, 1 hour each, daily = 150 hours/month
- Total: 330 Spark hours/month
Step 2: Convert to Required CUs
CUs = Spark VCore-Hours ÷ 2 (since 1 CU = 2 Spark VCores)
Example: 330 ÷ 2 = 165 CU-hours/month
Step 3: Factor Peak Concurrency
If 3 notebooks run simultaneously:
- Need: 3 × (VCores per notebook) = 3 × 8 = 24 Spark VCores = 12 CUs
- Minimum capacity: F16 (provides 32 Spark VCores = 16 CUs)
Step 4: Add Power BI Load
Check current Power BI Premium usage:
- 1 Power BI VCore ≈ 1-2 semantic models with hourly refresh
- 8 Power BI VCores ≈ F64 capacity
Step 5: Add Storage
OneLake Cost = Data Size (GB) × Tier Rate × Months
Example: 5 TB × $0.023/GB = $115/month
Recommended Sizing Starting Points
Organization Profile | Suggested Start | Monthly Cost |
Proof of Concept | F2 or F4 | $262.80 - $525.60 |
Departmental Analytics (< 50 users) | F16 or F32 | $2,102.40 - $4,204.80 |
Enterprise BI + Light Data Engineering | F64 | $8,409.60 |
Heavy Data Science + Real-Time | F128 - F256 | $16,819.20 - $33,638.40 |
Mission-Critical, 24/7 Processing | F512+ | $67,276.80+ |
Pro tip: Start one SKU smaller than you think you need. Fabric's capacity smoothing handles short bursts, and you can upgrade anytime without downtime.
Cost Optimization Strategies
With capacity-based pricing, optimization is critical to avoid overspending.
1. Right-Size Your Capacity
Monitor with Capacity Metrics App:
- Track CU utilization over 7-30 days
- If avg utilization < 40%, downgrade one SKU
- If frequent throttling, upgrade one SKU
Example:
- F64 running at 30% avg utilization = wasting $5,886/month
- Downgrade to F32 = $4,204.80/month savings
2. Pause Capacity During Off-Hours
Fabric allows pausing and resuming capacity:
- Pause nights/weekends when no workloads run
- You only pay while capacity is active
Savings calculation:
F64 hourly rate: $11.52
Paused hours: 12 hours/night × 30 days = 360 hours
Savings: 360 × $11.52 = $4,147.20/month (49% reduction)
Automate pausing:
- Azure Logic Apps
- Azure Functions scheduled triggers
- Fabric APIs
3. Optimize OneLake Storage
Move cold data to Cool/Archive tiers:
Tier | Cost | Access Pattern |
Standard | $0.023/GB | Active, queried weekly |
Cool | $0.01/GB | Monthly access |
Archive | $0.002/GB | Compliance, rarely accessed |
Example:
- 20 TB data, 15 TB is >90 days old
- Move to Cool: 15 TB × ($0.023 - $0.01) = $195/month savings
4. Use Data Compaction
Compact small files in Delta Lake:
- Small files slow queries and inflate costs
- Run OPTIMIZE commands to merge files
- Reduces storage and improves query performance
Before: 100,000 small Parquet files (10 MB each) = slow scans
After: 1,000 optimized files (1 GB each) = faster queries, lower CU consumption
5. Schedule Heavy Workloads During Pause Windows
If you can't pause capacity 24/7:
- Run heavy Spark jobs during low-traffic hours (2 AM - 6 AM)
- Scale up temporarily for big jobs, scale down after
- Reduces contention and potential need for larger base capacity
6. Leverage Reserved Capacity
1-year commit:
- 20-25% discount
- Breakeven if you'll use Fabric for 12+ months
3-year commit:
- 40-45% discount
- Breakeven if long-term Fabric adoption is certain
Example (F128):
- Pay-as-you-go: $16,819.20/month
- 3-year reserved: ~$9,250/month
- Savings: $90,838/year
7. Implement Workspace Governance
Avoid "shadow workspaces" consuming capacity:
- Assign workspaces to specific capacities
- Monitor orphaned workspaces
- Delete test/POC workspaces after projects end
8. Use DirectLake Mode in Power BI
DirectLake queries OneLake data without importing
- Eliminates duplicate storage
- Reduces semantic model refresh CU consumption
- Faster report load times
Before (Import mode):
- 5 TB data duplicated in semantic models
- Hourly refreshes = high CU usage
After (DirectLake):
- Zero duplication, queries OneLake directly
- Minimal CU for queries (no refresh)
When Microsoft Fabric Pays for Itself
The $50,000 question: When does Fabric's cost deliver positive ROI?
ROI Calculation Framework
Total Cost of Ownership (TCO):
TCO = (Fabric Capacity + OneLake Storage + User Licenses)
+ (Migration Costs + Training)
- (Eliminated Tool Costs + Time Savings Value)
Payback Period:
Payback = (Migration Cost + Training Cost) ÷ (Monthly Savings)
Scenario A: Consolidating Fragmented Azure Services
Before Fabric:
Azure Synapse (DW1000c): $10,950/month
Power BI Premium (P2): $9,990/month
Azure Data Factory: $1,500/month
Databricks (3 clusters): $3,200/month
ADLS Gen2 (20 TB): $460/month
───────────────────────────────────────
TOTAL: $26,100/month
After Fabric (F256):
F256 Capacity: $33,638.40/month
OneLake (20 TB): $460.00/month
───────────────────────────────────────
TOTAL: $34,098.40/month
DELTA: +$7,998.40/month (31% increase)
Wait, that's MORE expensive!
BUT-hidden savings:
- Eliminated 3 FTE managing separate services: 3 × $150K/year = $450K/year = $37,500/month
- Faster development: Unified platform = 30% faster time-to-insight = $15,000/month value
- Reduced errors: Fewer ETL handoffs = fewer data quality issues
Adjusted TCO:
Fabric cost: $34,098.40/month
- FTE savings: -$37,500.00/month
- Faster delivery: -$15,000.00/month
───────────────────────────────────────
NET SAVINGS: $18,401.60/month (70% reduction)
Payback on $100K migration: 100,000 ÷ 18,401.60 = 5.4 months
Conclusion: Fabric pays for itself in under 6 months when you factor in operational efficiency.
Scenario B: Greenfield Analytics Platform
Starting from scratch, 100 users:
Option 1: Build on Separate Azure Services
Azure Synapse: $6,000/month
Azure Data Factory: $1,000/month
Power BI Pro (100 users): $1,000/month
Databricks (2 clusters): $2,000/month
ADLS Gen2 (5 TB): $115/month
Management burden (1 FTE): $12,500/month
───────────────────────────────────────
TOTAL: $22,615/month
Option 2: Microsoft Fabric (F64)
F64 Capacity: $8,409.60/month
OneLake (5 TB): $115.00/month
Management (0.5 FTE): $6,250.00/month
───────────────────────────────────────
TOTAL: $14,774.60/month
SAVINGS: $7,840.40/month (35% less)
```
Conclusion: Greenfield projects on Fabric deliver immediate TCO savings with no migration cost.
Scenario C: Power BI Premium Migration
Power BI Premium P1 (64 VCores):
- Cost: $4,995/month
- Includes: Power BI only
Migrate to Fabric F64:
- Cost: $8,409.60/month
- Includes: Power BI + Data Engineering + Warehousing + Real-Time
ROI drivers:
- Replace separate Data Factory: +$1,000/month savings
- Replace Synapse Serverless: +$500/month savings
- Net increase: $8,409.60 - $4,995 - $1,000 - $500 = $1,914.60/month
For $1,914.60/month more, you get a complete analytics platform.
Breakeven: If Fabric enables one additional revenue-generating analytics use case worth >$2K/month, ROI is immediate.
Key ROI Drivers
Fabric delivers ROI through:
1. License consolidation: Eliminate 3-5 separate Azure services
2. Operational efficiency: Unified platform = fewer handoffs, less management
3. Faster time-to-insight: Integrated tools accelerate development
4. Reduced headcount: Simpler architecture requires fewer specialists
5. Avoid migration debt: Modern platform vs. technical debt accumulation
Hidden Costs to Watch For
Fabric's pricing is transparent, but these hidden costs catch teams off-guard:
1. Data Egress Charges
OneLake data transfer costs:
- Within same region: Free
- Cross-region (within Azure): $0.02/GB
- Outbound to internet: $0.087 - $0.12/GB (first 100 GB/month free)
Example:
- Export 10 TB/month to on-premises: 10,000 GB × $0.087 = $870/month
Avoid: Keep analytics workloads in same Azure region as OneLake.
2. Capacity Throttling Costs
What happens when you exceed CU limits:
- Background jobs queue (delays)
- Power BI refreshes slow down
- Interactive queries may timeout
Hidden cost: User productivity loss, missed SLAs
Solution: Right-size capacity or optimize workloads before throttling occurs.
3. Duplicate Data Costs
Common mistake: Copying data between OneLake and Azure Blob/ADLS:
- OneLake: $0.023/GB/month
- Plus duplicate in ADLS: $0.018/GB/month
- Total: $0.041/GB/month (78% increase)
Solution: Use OneLake Shortcuts to virtualize external data without duplication.
4. Abandoned Workspaces
Shadow IT problem:
- Developers create test workspaces
- Projects end, workspaces remain
- They continue consuming CUs
Hidden cost: 10-20% of capacity wasted on unused resources
Solution: Regular workspace audits, automatic cleanup policies.
5. Inefficient Data Models
Poor semantic model design(need modern data warehouse design):
- Unnecessary columns imported
- No aggregations
- Complex DAX calculations
Result: Refreshes take 10× longer = 10× CU consumption
Solution: Semantic model optimization best practices, use aggregations.
6. Lack of Capacity Governance
Without governance:
- All workspaces share one capacity
- One heavy job can throttle everyone
- No chargeback/showback to departments
7. Training and Adoption Lag
Fabric is powerful, but new:
- Teams trained on Synapse/Data Factory need reskilling
- Learning curve delays projects
Hidden cost: 3-6 months of reduced productivity
Solution: Budget for formal training, allocate time for experimentation.
FAQs
Q: Can I pause and resume Fabric capacity to save money?
A: Yes! You can pause capacity when not in use (nights, weekends) and only pay for active hours. Pausing is instant; resuming takes ~30 seconds.
Q: What happens if I exceed my capacity limits?
A: Fabric uses "capacity smoothing"- short bursts are allowed. Sustained overages trigger throttling (background jobs queue, refreshes slow down). You won't be charged extra, but performance degrades.
Q: Is OneLake storage included in the capacity price?
A: No. OneLake storage is billed separately at $0.023/GB/month (standard tier). Your capacity purchase covers only compute (CUs).
Q: Do I need to buy separate licenses for each Fabric workload?
A: No. One capacity license grants access to all workloads: Data Engineering, Warehouse, Data Science, Real-Time Analytics, Data Factory, and Power BI.
Q: Can I mix Fabric capacities (e.g., F64 for production, F8 for dev)?
A: Yes. Use multiple capacities and assign workspaces appropriately. This enables cost control and isolates dev/test from production workloads.
Q: How does Fabric pricing compare to Snowflake?
A: Snowflake charges separately for compute (credits) and storage. Fabric bundles compute + BI. For pure data warehousing, Snowflake may be cheaper; for unified analytics + BI, Fabric often wins on TCO.
Q: Can I bring my own Azure storage instead of OneLake?
A: Partially. You can use OneLake Shortcuts to query external Azure Data Lake Gen2 data without copying. But Fabric-native features work best with data in OneLake.
Q: Are there free trials for Fabric?
A: Yes. Microsoft offers a 60-day free trial with F64 capacity. Perfect for POCs and hands-on evaluation.
Q: How do I monitor Fabric capacity usage?
A: Use the Capacity Metrics App in the Fabric admin portal. It shows real-time CU consumption, throttling events, and workload breakdown.
Q: Can I get volume discounts for Fabric?
A: Yes, through Reserved Capacity (1 or 3-year commits) offering 20-45% discounts. Enterprise Agreement (EA) customers may negotiate custom pricing with Microsoft.
Need expert help sizing your Fabric deployment? Aptocoiner Analytics specializes in Microsoft Fabric architecture, migration, and cost optimization. [Schedule a free consultation ]
Sources
- Microsoft Fabric pricing: https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/
- Microsoft Fabric licenses and F SKU capacity units: https://learn.microsoft.com/en-us/fabric/enterprise/licenses
- Microsoft Fabric cost optimization guidance: https://learn.microsoft.com/en-us/azure/well-architected/microsoft-fabric/cost-optimization
- Microsoft Fabric Capacity Estimator: https://www.microsoft.com/en-us/microsoft-fabric/capacity-estimator
- Azure Pricing Calculator: https://azure.microsoft.com/en-us/pricing/calculator/
- Microsoft Fabric Capacity Metrics app: https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app
- Azure Synapse pricing: https://azure.microsoft.com/en-us/pricing/details/synapse-analytics/
- Azure Databricks pricing: https://azure.microsoft.com/en-us/pricing/details/databricks/
- Azure Retail Prices API: https://prices.azure.com/api/retail/prices
Comments