# Manage Microsoft Fabric Capacity with .NET

Managing Microsoft Fabric capacity through Azure Resource Manager requires precise SDK workflows. This skill provides .NET guidance for authentication, provisioning, scaling, suspension, deletion, and status checks.

## Install

```bash
npx skillstore add sickn33/azure-mgmt-fabric-dotnet
```

## Metadata

- Status: approved
- Slug: sickn33-azure-mgmt-fabric-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: b2302532abc8aa221d1bd21e8a100ca1fe0d5cf2567463c95b34a98361e8f2d0
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-mgmt-fabric-dotnet
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-mgmt-fabric-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-mgmt-fabric-dotnet/manifest

## Capabilities

- Provide installation guidance for the Azure Resource Manager Fabric SDK and Azure Identity packages.
- Authenticate ARM clients with DefaultAzureCredential and retrieve the active Azure subscription.
- Create, retrieve, update, suspend, resume, list, and delete Fabric capacities.
- Check capacity name availability and list supported SKUs by subscription or capacity.
- Handle long-running operations, provisioning states, and common ARM request failures.
- Explain management-plane scope, resource hierarchy, SDK types, and regional constraints.

## Use Cases

- Provision Fabric capacity: Generate a .NET workflow that authenticates, validates inputs, creates a Fabric capacity, and waits for provisioning to finish.
- Automate capacity lifecycle: Build repeatable routines for listing, scaling, suspending, resuming, and deleting capacities with state checks.
- Review SDK integration: Check a C\# implementation for correct ARM types, asynchronous operations, error handling, and management-plane boundaries.

## Prompt Templates

### Set up Fabric management

```
Show me how to set up a .NET application for Microsoft Fabric capacity management using DefaultAzureCredential and my Azure subscription.
```

### Provision a capacity

```
Create a C# workflow for capacity [name] in [resource group], using [region], [SKU], and [administrator UPNs].
```

### Manage the capacity lifecycle

```
Design a workflow that lists capacities, scales [capacity] to [SKU], suspends it when idle, and resumes it after state validation.
```

### Review resilient automation

```
Review my Fabric automation for idempotency, least privilege, long-running operations, retries, quota failures, and guarded deletion. Explain every recommended change.
```

## Limitations

- Covers Fabric capacity management only, not workspaces, lakehouses, warehouses, or data items.
- Requires valid Azure authentication, permissions, subscription access, regional availability, and quota.
- Package versions, API behavior, SKU availability, and pricing can change after publication.
- Examples can modify or delete billable cloud resources and require environment-specific testing.

## Best Practices

- Use DefaultAzureCredential with least-privilege Azure roles and avoid hardcoded secrets.
- Confirm subscription, resource group, capacity name, region, SKU, administrators, and cost before mutations.
- Wait for long-running operations when required, handle ARM errors, and verify the final provisioning state.

## Anti Patterns

- Do not use this SDK for Fabric workspaces, lakehouses, warehouses, or data-plane items.
- Do not delete, suspend, resume, scale, or reassign administrators without explicit target confirmation.
- Do not assume that a SKU, quota, package version, or API behavior is identical across regions and subscriptions.

## Security Audit

- Audited at: 2026-07-23T21:26:18.428\+00:00
- Summary: All 79 static findings are false positives caused by Markdown formatting, placeholder credential names, official links, and benign prose. No prompt injection or exfiltration intent was found. The skill still presents privileged Azure operations that can affect cost, access, and service availability.

## Stats

- Views: 80
- Downloads: 7
- Favorites: 0
- Popularity score: 0