Azure.ResourceManager.Fabric (.NET)
Management plane SDK for provisioning and managing Microsoft Fabric capacity resources via Azure Resource Manager.
Management Plane Only This SDK manages Fabric capacities (compute resources). For working with Fabric workspaces, lakehouses, warehouses, and data items, use the Microsoft Fabric REST API or data plane SDKs.
Installation
Current Version: 1.0.0 (GA - September 2025)
API Version: 2023-11-01
Target Frameworks: .NET 8.0, .NET Standard 2.0
Environment Variables
Authentication
Resource Hierarchy
Core Workflows
1. Create Fabric Capacity
2. Get Fabric Capacity
3. Update Capacity (Scale SKU or Change Admins)
4. Suspend and Resume Capacity
5. Delete Capacity
6. List All Capacities
7. Check Name Availability
8. List Available SKUs
SKU Reference
Key Types Reference
Provisioning and Resource States
Provisioning States (FabricProvisioningState)
Succeeded- Operation completed successfullyFailed- Operation failedCanceled- Operation was canceledDeleting- Capacity is being deletedProvisioning- Initial provisioning in progressUpdating- Update operation in progress
Resource States (FabricResourceState)
Active- Capacity is running and availableProvisioning- Being provisionedFailed- In failed stateUpdating- Being updatedDeleting- Being deletedSuspending- Transitioning to suspendedSuspended- Suspended (not billing for compute)Pausing- Transitioning to pausedPaused- PausedResuming- Resuming from suspended/pausedScaling- Scaling to different SKUPreparing- Preparing resources
Best Practices
- Use
WaitUntil.Completedfor operations that must finish before proceeding - Use
WaitUntil.Startedwhen you want to poll manually or run operations in parallel - Use
DefaultAzureCredential— never hardcode credentials - Handle
RequestFailedExceptionfor ARM API errors - Use
CreateOrUpdateAsyncfor idempotent operations - Suspend when not in use — Fabric capacities bill for compute even when idle
- Check provisioning state before performing operations on a capacity
- Use appropriate SKU — Start small (F2/F4) for dev/test, scale up for production
Error Handling
Common Pitfalls
- Capacity names must be globally unique — Fabric capacity names must be unique across all Azure subscriptions
- Suspend doesn't delete — Suspended capacities still exist but don't bill for compute
- SKU changes may require downtime — Scaling operations can take several minutes
- Admin UPNs must be valid — Capacity administrators must be valid Azure AD users
- Location constraints — Not all SKUs are available in all regions; use
GetSkusFabricCapacitiesAsyncto check - Long provisioning times — Capacity creation can take 5-15 minutes


