Wardn HubTrusted MCP server directory.

Registry

  • MCP Servers
  • Skills
  • Categories

Resources

  • API docs
  • Score method

Contribute

  • Submit server
  • Advertise
© 2026 Wardn Hub
Wardn Hub
MCP ServersSkillsCategoriesAPI docsSubmit server
Submit server
skills/sickn33/agentic-awesome-skills/azure-mgmt-fabric-dotnet

azure-mgmt-fabric-dotnet

1
sickn33/agentic-awesome-skills·Audit passed·Snapshot 0cd0870550ba

Summary

This source did not publish a separate summary. Review SKILL.md before using the skill.

SKILL.md

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

dotnet add package Azure.ResourceManager.Fabric
dotnet add package Azure.Identity

Current Version: 1.0.0 (GA - September 2025)
API Version: 2023-11-01
Target Frameworks: .NET 8.0, .NET Standard 2.0

Environment Variables

AZURE_SUBSCRIPTION_ID=<your-subscription-id>
# For service principal auth (optional)
AZURE_TENANT_ID=<tenant-id>
AZURE_CLIENT_ID=<client-id>
AZURE_CLIENT_SECRET=<client-secret>

Authentication

using Azure.Identity;
using Azure.ResourceManager;
using Azure.ResourceManager.Fabric;

// Always use DefaultAzureCredential
var credential = new DefaultAzureCredential();
var armClient = new ArmClient(credential);

// Get subscription
var subscription = await armClient.GetDefaultSubscriptionAsync();

Resource Hierarchy

ArmClient
└── SubscriptionResource
    └── ResourceGroupResource
        └── FabricCapacityResource

Core Workflows

1. Create Fabric Capacity

using Azure.ResourceManager.Fabric;
using Azure.ResourceManager.Fabric.Models;
using Azure.Core;

// Get resource group
var resourceGroup = await subscription.GetResourceGroupAsync("my-resource-group");

// Define capacity configuration
var administration = new FabricCapacityAdministration(
    new[] { "[email protected]" }  // Capacity administrators (UPNs or object IDs)
);

var properties = new FabricCapacityProperties(administration);

var sku = new FabricSku("F64", FabricSkuTier.Fabric);

var capacityData = new FabricCapacityData(
    AzureLocation.WestUS2,
    properties,
    sku)
{
    Tags = { ["Environment"] = "Production" }
};

// Create capacity (long-running operation)
var capacityCollection = resourceGroup.Value.GetFabricCapacities();
var operation = await capacityCollection.CreateOrUpdateAsync(
    WaitUntil.Completed,
    "my-fabric-capacity",
    capacityData);

FabricCapacityResource capacity = operation.Value;
Console.WriteLine($"Created capacity: {capacity.Data.Name}");
Console.WriteLine($"State: {capacity.Data.Properties.State}");

2. Get Fabric Capacity

// Get existing capacity
var capacity = await resourceGroup.Value
    .GetFabricCapacityAsync("my-fabric-capacity");

Console.WriteLine($"Name: {capacity.Value.Data.Name}");
Console.WriteLine($"Location: {capacity.Value.Data.Location}");
Console.WriteLine($"SKU: {capacity.Value.Data.Sku.Name}");
Console.WriteLine($"State: {capacity.Value.Data.Properties.State}");
Console.WriteLine($"Provisioning State: {capacity.Value.Data.Properties.ProvisioningState}");

3. Update Capacity (Scale SKU or Change Admins)

var capacity = await resourceGroup.Value
    .GetFabricCapacityAsync("my-fabric-capacity");

var patch = new FabricCapacityPatch
{
    Sku = new FabricSku("F128", FabricSkuTier.Fabric),  // Scale up
    Properties = new FabricCapacityUpdateProperties
    {
        Administration = new FabricCapacityAdministration(
            new[] { "[email protected]", "[email protected]" }
        )
    }
};

var updateOperation = await capacity.Value.UpdateAsync(
    WaitUntil.Completed,
    patch);

Console.WriteLine($"Updated SKU: {updateOperation.Value.Data.Sku.Name}");

4. Suspend and Resume Capacity

// Suspend capacity (stop billing for compute)
await capacity.Value.SuspendAsync(WaitUntil.Completed);
Console.WriteLine("Capacity suspended");

// Resume capacity
var resumeOperation = await capacity.Value.ResumeAsync(WaitUntil.Completed);
Console.WriteLine($"Capacity resumed. State: {resumeOperation.Value.Data.Properties.State}");

5. Delete Capacity

await capacity.Value.DeleteAsync(WaitUntil.Completed);
Console.WriteLine("Capacity deleted");

6. List All Capacities

// In a resource group
await foreach (var cap in resourceGroup.Value.GetFabricCapacities())
{
    Console.WriteLine($"- {cap.Data.Name} ({cap.Data.Sku.Name})");
}

// In a subscription
await foreach (var cap in subscription.GetFabricCapacitiesAsync())
{
    Console.WriteLine($"- {cap.Data.Name} in {cap.Data.Location}");
}

7. Check Name Availability

var checkContent = new FabricNameAvailabilityContent
{
    Name = "my-new-capacity",
    ResourceType = "Microsoft.Fabric/capacities"
};

var result = await subscription.CheckFabricCapacityNameAvailabilityAsync(
    AzureLocation.WestUS2,
    checkContent);

if (result.Value.IsNameAvailable == true)
{
    Console.WriteLine("Name is available!");
}
else
{
    Console.WriteLine($"Name unavailable: {result.Value.Reason} - {result.Value.Message}");
}

8. List Available SKUs

// List all SKUs available in subscription
await foreach (var skuDetails in subscription.GetSkusFabricCapacitiesAsync())
{
    Console.WriteLine($"SKU: {skuDetails.Name}");
    Console.WriteLine($"  Resource Type: {skuDetails.ResourceType}");
    foreach (var location in skuDetails.Locations)
    {
        Console.WriteLine($"  Location: {location}");
    }
}

// List SKUs available for an existing capacity (for scaling)
await foreach (var skuDetails in capacity.Value.GetSkusForCapacityAsync())
{
    Console.WriteLine($"Can scale to: {skuDetails.Sku.Name}");
}

SKU Reference

SKU NameCapacity Units (CU)Power BI Equivalent
F22-
F44-
F88EM1/A1
F1616EM2/A2
F3232EM3/A3
F6464P1/A4
F128128P2/A5
F256256P3/A6
F512512P4/A7
F10241024P5/A8
F20482048-

Key Types Reference

TypePurpose
ArmClientEntry point for all ARM operations
FabricCapacityResourceRepresents a Fabric capacity instance
FabricCapacityCollectionCollection for capacity CRUD operations
FabricCapacityDataCapacity creation/read data model
FabricCapacityPatchCapacity update payload
FabricCapacityPropertiesCapacity properties (administration, state)
FabricCapacityAdministrationAdmin members configuration
FabricSkuSKU configuration (name and tier)
FabricSkuTierPricing tier (currently only "Fabric")
FabricProvisioningStateProvisioning states (Succeeded, Failed, etc.)
FabricResourceStateResource states (Active, Suspended, etc.)
FabricNameAvailabilityContentName availability check request
FabricNameAvailabilityResultName availability check response

Provisioning and Resource States

Provisioning States (FabricProvisioningState)

  • Succeeded - Operation completed successfully
  • Failed - Operation failed
  • Canceled - Operation was canceled
  • Deleting - Capacity is being deleted
  • Provisioning - Initial provisioning in progress
  • Updating - Update operation in progress

Resource States (FabricResourceState)

  • Active - Capacity is running and available
  • Provisioning - Being provisioned
  • Failed - In failed state
  • Updating - Being updated
  • Deleting - Being deleted
  • Suspending - Transitioning to suspended
  • Suspended - Suspended (not billing for compute)
  • Pausing - Transitioning to paused
  • Paused - Paused
  • Resuming - Resuming from suspended/paused
  • Scaling - Scaling to different SKU
  • Preparing - Preparing resources

Best Practices

  1. Use WaitUntil.Completed for operations that must finish before proceeding
  2. Use WaitUntil.Started when you want to poll manually or run operations in parallel
  3. Always use DefaultAzureCredential — never hardcode credentials
  4. Handle RequestFailedException for ARM API errors
  5. Use CreateOrUpdateAsync for idempotent operations
  6. Suspend when not in use — Fabric capacities bill for compute even when idle
  7. Check provisioning state before performing operations on a capacity
  8. Use appropriate SKU — Start small (F2/F4) for dev/test, scale up for production

Error Handling

using Azure;

try
{
    var operation = await capacityCollection.CreateOrUpdateAsync(
        WaitUntil.Completed, capacityName, capacityData);
}
catch (RequestFailedException ex) when (ex.Status == 409)
{
    Console.WriteLine("Capacity already exists or conflict");
}
catch (RequestFailedException ex) when (ex.Status == 400)
{
    Console.WriteLine($"Invalid configuration: {ex.Message}");
}
catch (RequestFailedException ex) when (ex.Status == 403)
{
    Console.WriteLine("Insufficient permissions or quota exceeded");
}
catch (RequestFailedException ex)
{
    Console.WriteLine($"ARM Error: {ex.Status} - {ex.ErrorCode}: {ex.Message}");
}

Common Pitfalls

  1. Capacity names must be globally unique — Fabric capacity names must be unique across all Azure subscriptions
  2. Suspend doesn't delete — Suspended capacities still exist but don't bill for compute
  3. SKU changes may require downtime — Scaling operations can take several minutes
  4. Admin UPNs must be valid — Capacity administrators must be valid Azure AD users
  5. Location constraints — Not all SKUs are available in all regions; use GetSkusFabricCapacitiesAsync to check
  6. Long provisioning times — Capacity creation can take 5-15 minutes

Related SDKs

SDKPurposeInstall
Azure.ResourceManager.FabricManagement plane (this SDK)dotnet add package Azure.ResourceManager.Fabric
Microsoft.Fabric.ApiData plane operations (beta)dotnet add package Microsoft.Fabric.Api --prerelease
Azure.ResourceManagerCore ARM SDKdotnet add package Azure.ResourceManager
Azure.IdentityAuthenticationdotnet add package Azure.Identity

References

  • Azure.ResourceManager.Fabric NuGet
  • GitHub Source
  • Microsoft Fabric Documentation
  • Fabric Capacity Management

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Related skills

amazon-alexakubernetes-architectpostgresql-optimizationgit-workflow-and-versioningnextjs-app-router-patterns