Azure API Management for .NET
Provision and govern Azure API Management resources from .NET.
The document distinguishes management-plane from data-plane use and recommends DefaultAzureCredential instead of hardcoded keys. However, examples can create, modify, and delete APIM resources, perform restore operations, print subscription secrets, and use a plaintext password example, without least-privilege guidance, user confirmation, impact disclosure, sensitive-data handling, or verifiable rollback, so points are deducted.
It covers major service, API, product, subscription, policy, and error-handling paths and includes some exception handling. However, version claims, API signatures, and snippet completeness are not verified within the skill; long-running operations, resource-state assumptions, input validation, and abnormal-input feedback are thin. Under static calibration, the score does not exceed 10.
The name, audience, management-plane scope, and trigger phrases are clear, and the skill states that it does not perform gateway data-plane calls. Non-fit cases, permission prerequisites, regional constraints, and Chinese-language boundaries are not sufficiently defined, and Azure/.NET requirements limit use outside that environment.
The skill has front matter, MIT licensing, author and version metadata, layered sections for installation, authentication, workflows, and references, plus multiple examples. It lacks a changelog, explicit maintenance ownership and update path, pinned dependency guidance, troubleshooting, and known-limitations disclosure.
It provides directly reusable .NET patterns for common APIM management tasks and offers meaningful value over writing them manually. However, the snippets are not shown to have been tested for this skill; some depend on surrounding context or may require API-version adjustments, while security-sensitive and destructive operations require substantial human review. Under static calibration, the score does not exceed 7.
The skill supplies auditable code, package names, official documentation references, and repository-level CI/test material. The supplied CI and tests do not establish coverage of this selected skill's key paths, and there are no skill-specific acceptance criteria, execution results, or independently reproducible evidence. Under static calibration, the score does not exceed 5.
- Add explicit user confirmation, permission scoping, impact assessment, and recovery procedures before create, update, delete, or restore operations.
- Do not print subscription keys or use the plaintext password shown in the example; use secure secret storage and rotation.
- Verify the stated v1.3.0 version, API signatures, and SDK type usage by compiling and integration-testing in the target project.
- The core function depends on Azure ARM, Azure.Identity, and the .NET SDK; verify service reachability, tenant permissions, and mainland-China network compatibility.
What does this skill do, and when should you use it?
This Agent Skill targets the Azure API Management management plane through Azure.ResourceManager.ApiManagement. It helps developers work with APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends. The material covers package installation, DefaultAzureCredential authentication, ARM resource navigation, asynchronous CRUD operations, backup and restore, and ARM error handling. It does not cover direct API calls through an APIM gateway, which belong to the data plane.
It explains how to install Azure.ResourceManager.ApiManagement and Azure.Identity, configure Azure subscription and credential environment variables, and navigate subscriptions, resource groups, and APIM services with ArmClient. It provides C# examples for creating or updating APIM services, APIs, products, and subscriptions; retrieving subscription keys; applying XML API policies; backing up and restoring services; and handling RequestFailedException.
- A .NET platform engineer needs to provision or update an Azure API Management service programmatically.
- An API platform team needs to manage APIs, products, subscriptions, and access policies.
- A developer needs ARM SDK guidance for APIM users, groups, backends, or self-hosted gateways.
- An operations team needs to automate APIM service backup and restore.
- A team wants Azure management code built around DefaultAzureCredential and idempotent CreateOrUpdateAsync operations.
What are this skill's strengths and limitations?
- Shows the resource hierarchy from ArmClient through APIM child resources.
- Covers common management tasks including services, APIs, products, subscriptions, policies, backup, restore, and error handling.
- Clearly separates management-plane SDK operations from data-plane gateway calls.
- Includes guidance for DefaultAzureCredential, idempotent updates, and long-running operations.
- MIT-licensed and maintained as part of Microsoft's actively developed Agent Skills collection.
- Limited to Azure API Management management-plane operations; it does not teach gateway data-plane calls.
- Service creation may take more than 30 minutes, and the Developer SKU example is intended for development/testing with no SLA.
- The source does not document independent test scenarios or platform-validation results for this specific skill.
- It requires an Azure subscription, suitable permissions, and a .NET project; exact RBAC roles are not specified.
How do you install this skill?
Run:
npx skills add microsoft/skills
Choose this skill in the installation wizard. The README states that skills are installed into the selected agent's directory, such as .github/skills/ for GitHub Copilot, and can be symlinked across agent configurations. For manual copying, use .github/plugins/azure-sdk-dotnet/skills/azure-mgmt-apimanagement-dotnet/.
How do you use this skill?
After installing the skill, give the coding agent a management-plane request such as: "Using Azure.ResourceManager.ApiManagement and DefaultAzureCredential, create a Developer SKU APIM service, then create an API, product, and subscription." You can also request API policy configuration, backup and restore, or ARM error handling. Direct calls to an APIM gateway are outside this skill's scope.
How does this skill compare with similar options?
Compared with APIM data-plane usage, this skill focuses on Azure Resource Manager operations for provisioning and managing services, APIs, products, subscriptions, and policies. It does not guide business API requests sent directly to an APIM gateway endpoint.