Fabric Capacity Manager for .NET
Manage Microsoft Fabric capacities programmatically through Azure Resource Manager.
The document discourages hardcoded credentials and clearly states the management-plane scope, authentication variables, and administrator identities. However, creation, scaling, suspension, and deletion affect external resources and billing without stepwise user confirmation, least-privilege RBAC guidance, sensitive-data flow disclosure, or verifiable rollback, so points are deducted.
Installation, authentication, resource hierarchy, CRUD, long-running operations, states, and common errors are documented and the examples are broadly consistent. However, there are no skill-specific tests, compilation evidence, API compatibility proof, or recovery procedures; static review therefore supports only a modest score.
Triggers, the .NET management-plane purpose, and the boundary from Fabric data-plane work are clear, covering capacity creation, retrieval, update, suspend, resume, delete, listing, and SKU discovery. Non-fit cases, permission prerequisites, input/output contracts, Chinese support, and mainland-China reachability are not specified.
The skill includes installation, environment variables, authentication, workflows, type references, states, best practices, error handling, pitfalls, related SDKs, version metadata, and an MIT license. It lacks a changelog, explicit maintenance owner/update path, and in-file stability guidance for external references.
The document covers the main Fabric capacity-management tasks and provides directly adaptable C# examples, an SKU table, and error handling. Yet the examples are not statically proven to compile or run, and cost, approval, idempotency boundaries, and pre-delete confirmation require user-side review and adaptation.
The skill supplies package, version, API-version, and reference metadata, while the repository context shows generic CI and test infrastructure. No skill-specific tests, test results, or third-party execution evidence are provided, so key API claims and runnable-example status cannot be independently reproduced from the supplied files.
- Before create, scale, suspend, resume, or delete operations, confirm the subscription, resource group, region, SKU, RBAC permissions, and expected cost; deletion needs explicit confirmation and a recovery or rebuild plan.
- Do not commit AZURE_CLIENT_SECRET or other credentials to code, logs, or prompts; key rotation, log redaction, and least-privilege guidance are not documented.
- The stated package/API versions, type names, and calls are not backed by skill-specific compilation or integration tests; validate them in the target .NET and SDK environment.
- The skill does not address mainland-China reachability for Azure, NuGet, Microsoft documentation, or related services.
What it does & when to use it
This skill helps .NET developers manage Microsoft Fabric capacity resources with the Azure Resource Manager SDK. It covers the management-plane lifecycle: create, read, update, delete, scale, suspend, and resume capacities, plus name-availability and SKU queries. It does not cover Fabric workspaces, lakehouses, warehouses, or data items. The guidance includes authentication, resource hierarchy, resource states, error handling, and operational pitfalls.
It shows how to install Azure.ResourceManager.Fabric and Azure.Identity, authenticate with DefaultAzureCredential or a specific credential, create an ArmClient, and navigate subscriptions and resource groups to FabricCapacityResource objects. Examples cover creating capacities with administrators, locations, SKUs, and tags; reading properties and states; changing SKUs or administrators; suspending and resuming; deleting; listing capacities; checking names; and listing subscription or capacity SKUs.
- A .NET Azure developer needs to provision a Microsoft Fabric capacity in a resource group through code.
- A platform engineer needs to scale a Fabric SKU or change capacity administrators as workload requirements change.
- An operations team needs to suspend capacities outside working hours and resume them later.
- An Azure deployment workflow needs to validate capacity names, regional availability, or eligible SKUs before provisioning.
Pros & cons
- Covers the core management-plane lifecycle for Fabric capacities.
- Provides directly reusable asynchronous C# Azure SDK patterns.
- Includes authentication, SKU selection, resource states, error handling, and pitfalls.
- MIT-licensed and installable through the Agent Skills collection.
- It does not manage Fabric workspaces, lakehouses, warehouses, or data items.
- Provisioning and scaling are long-running operations; creation may take 5–15 minutes.
- Permissions, quotas, regional SKU availability, and Azure billing depend on the target environment.
- The supplied material does not document independent test coverage for this individual skill or a platform compatibility matrix.
How to install
Run npx skills add microsoft/skills and select the skill in the installation wizard. The collection installs into the chosen agent directory, such as .github/skills/ for GitHub Copilot. In the .NET project, run dotnet add package Azure.ResourceManager.Fabric and dotnet add package Azure.Identity.
How to use
Ask the coding agent for a task such as “Create an F64 Microsoft Fabric capacity in this resource group with Azure.ResourceManager.Fabric” or “Suspend and resume the existing Fabric capacity.” Configure AZURE_SUBSCRIPTION_ID and the required identity variables, then use the C# patterns to create an ArmClient, obtain the subscription and resource group, and call the relevant asynchronous ARM methods. The lifecycle examples use WaitUntil.Completed for long-running operations.
Compared to similar skills
Use the Microsoft Fabric REST API or data-plane SDKs for workspaces, lakehouses, warehouses, and data items. Azure.ResourceManager is the core ARM SDK, while Azure.Identity supplies authentication; this skill focuses specifically on Azure.ResourceManager.Fabric.