SkillAgentSearch skills...

azure-mgmt-fabric-dotnet

Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager.

Install / Use

npx skills add microsoft/skills --skill azure-mgmt-fabric-dotnet

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Our assessment of azure-mgmt-fabric-dotnet

azure-mgmt-fabric-dotnet scores 93/100 on our quality scale, 549th of 3,481 Development & Engineering skills we index (top 16%).

Its SKILL.md is 11 KB long, well organised into 24 sections with 13 code examples: a thorough specification that gives an agent plenty to work with.

With 3,051 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 5 days ago, so azure-mgmt-fabric-dotnet is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

azure-mgmt-fabric-dotnet compared with similar skills

All 4 of these similar skills score higher than azure-mgmt-fabric-dotnet; compare them before choosing.

SkillScoreStarsUpdatedFormat
azure-mgmt-fabric-dotnet (this skill)by microsoft933.1k5d agoSKILL.md
ai-job-searchby MadsLorentzen10044.4ktodayCLAUDE.md
claude-howtoby luongnv8910041.7k2d agoCLAUDE.md
algorithmic-artby anthropics100177.9k6d agoSKILL.md
pptxby anthropics100177.9k6d agoSKILL.md

Frequently asked questions

How do I install azure-mgmt-fabric-dotnet?
Run npx skills add microsoft/skills --skill azure-mgmt-fabric-dotnet. The install tabs above show the steps for each supported agent.
Which AI agents does azure-mgmt-fabric-dotnet work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is azure-mgmt-fabric-dotnet safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is azure-mgmt-fabric-dotnet still maintained?
The repository was last updated 5 days ago, so azure-mgmt-fabric-dotnet is actively maintained.

name: azure-mgmt-fabric-dotnet description: | Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity", "Fabric SKU", "provision Fabric", "ARM Fabric", "FabricCapacityResource". license: MIT metadata: author: Microsoft version: "1.0.0" package: Azure.ResourceManager.Fabric

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> # Required: Azure subscription ID
AZURE_TOKEN_CREDENTIALS=prod  # Required only if DefaultAzureCredential is used in production
AZURE_TENANT_ID=<tenant-id> # For service principal auth (optional)
AZURE_CLIENT_ID=<client-id> # For service principal auth (optional)
AZURE_CLIENT_SECRET=<client-secret> # For service principal auth (optional)

Authentication

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

// Local dev: DefaultAzureCredential. Production: set AZURE_TOKEN_CREDENTIALS=prod or AZURE_TOKEN_CREDENTIALS=<specific_credential>
var credential = new DefaultAzureCredential(
    DefaultAzureCredential.DefaultEnvironmentVariableName
);
// Or use a specific credential directly in production:
// See https://learn.microsoft.com/dotnet/api/overview/azure/identity-readme?view=azure-dotnet#credential-classes
// var credential = new ManagedIdentityCredential();
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[] { "admin@contoso.com" }  // 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[] { "admin@contoso.com", "newadmin@contoso.com" }
        )
    }
};

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 Name | Capacity Units (CU) | Power BI Equivalent | |----------|---------------------|---------------------| | F2 | 2 | - | | F4 | 4 | - | | F8 | 8 | EM1/A1 | | F16 | 16 | EM2/A2 | | F32 | 32 | EM3/A3 | | F64 | 64 | P1/A4 | | F128 | 128 | P2/A5 | | F256 | 256 | P3/A6 | | F512 | 512 | P4/A7 | | F1024 | 1024 | P5/A8 | | F2048 | 2048 | - |

Key Types Reference

| Type | Purpose | |------|---------| | ArmClient | Entry point for all ARM operations | | FabricCapacityResource | Represents a Fabric capacity instance | | FabricCapacityCollection | Collection for capacity CRUD operations | | FabricCapacityData | Capacity creation/read data model | | FabricCapacityPatch | Capacity update payload | | FabricCapacityProperties | Capacity properties (administration, state) | | FabricCapacityAdministration | Admin members configuration | | FabricSku | SKU configuration (name and tier) | | FabricSkuTier | Pricing tier (currently only "Fabric") | | FabricProvisioningState | Provisioning states (Succeeded, Failed, etc.) | | FabricResourceState | Resource states (Active, Suspended, etc.) | | FabricNameAvailabilityContent | Name availability check request | | FabricNameAvailabilityResult | Name 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. 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

| SDK | Purpose | Install | |-----|---------|---------| | Azure.ResourceManager.Fabric | Management plane (this SDK) | dotnet add package Azure.ResourceManager.Fabric | | Microsoft.Fabric.Api | Data plane operations (beta) | dotnet add package Microsoft.Fabric.Api --prerelease | | Azure.ResourceManager | Core ARM SDK | dotnet add package Azure.ResourceManager | | Azure.Identity | Authentication | dotnet add package Azure.Identity |

References

Related Skills

View on GitHub
GitHub Stars3.1k
CategoryDevelopment
Updated5d ago
Forks349

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions