generated: '2026-09-06'
method: generated
source: >-
  Generated from the eight first-party contracts under openapi/ plus
  conventions/azure-cloud-conventions.yml, errors/azure-cloud-problem-types.yml and
  data-model/azure-cloud-data-model.yml. Every operationId cited in a skill was verified present in the
  named contract before the skill was written; none was invented.
provider: Microsoft Azure Cloud
providerId: azure-cloud
note: >-
  Azure publishes no Agent Skills and no AGENTS.md of its own — searched
  https://azure.microsoft.com/llms.txt , https://github.com/Azure and the Learn developer index on
  2026-09-06 and found none. These four are ours, grounded in the harvested contracts.
skills:
  - id: azure-cloud-authenticate-and-call-arm
    file: skills/azure-cloud-authenticate-and-call-arm.md
    title: Authenticate and make a first Azure Resource Manager call
    api: azure-cloud
    contract: openapi/azure-cloud-resource-manager-api-openapi.json
    operations:
      - ResourceGroups_List
      - Resources_List
      - ResourceGroups_CheckExistence
    covers:
      - Entra ID token acquisition and the management.azure.com/.default scope
      - The mandatory api-version parameter and the MissingApiVersionParameter failure
      - nextLink pagination
      - The OData error envelope and the codes worth branching on
      - Rate-limit budget and the x-ms-ratelimit-remaining-* headers
  - id: azure-cloud-manage-virtual-machine-lifecycle
    file: skills/azure-cloud-manage-virtual-machine-lifecycle.md
    title: Manage an Azure virtual machine
    api: azure-cloud
    contract: openapi/azure-cloud-compute-api-openapi.json
    operations:
      - VirtualMachines_ListAll
      - VirtualMachines_Get
      - VirtualMachines_InstanceView
      - VirtualMachines_CreateOrUpdate
      - VirtualMachines_Start
      - VirtualMachines_PowerOff
      - VirtualMachines_Deallocate
      - VirtualMachines_Delete
    covers:
      - The PowerOff vs Deallocate billing and hardware-lease distinction
      - Declarative PUT semantics and If-Match optimistic concurrency
      - Azure-AsyncOperation polling, including the 200-with-status-Failed trap
      - Absence of replay protection on POST actions
  - id: azure-cloud-provision-and-tear-down-a-resource-group
    file: skills/azure-cloud-provision-and-tear-down-a-resource-group.md
    title: Provision and tear down an Azure resource group
    api: azure-cloud
    contract: openapi/azure-cloud-resource-manager-api-openapi.json
    operations:
      - ResourceGroups_CreateOrUpdate
      - ResourceGroups_Get
      - ResourceGroups_CheckExistence
      - ResourceGroups_ExportTemplate
      - Resources_ListByResourceGroup
      - Resources_ValidateMoveResources
      - Resources_MoveResources
      - ResourceGroups_Delete
    covers:
      - Export-before-destroy as the only resource-group snapshot Azure offers
      - Validate-then-move as one of three rehearsal affordances on ARM
      - The irreversibility of ResourceGroups_Delete and what survives it
  - id: azure-cloud-recover-a-soft-deleted-key-vault
    file: skills/azure-cloud-recover-a-soft-deleted-key-vault.md
    title: Recover a soft-deleted Azure Key Vault
    api: azure-cloud
    contract: openapi/azure-cloud-key-vault-api-openapi.json
    operations:
      - Vaults_ListDeleted
      - Vaults_GetDeleted
      - Vaults_CreateOrUpdate
      - Vaults_PurgeDeleted
      - Vaults_Delete
      - Vaults_Get
    covers:
      - The documented 7-90 day soft-delete window and the name-reuse lock
      - Recovery via createMode recover rather than a dedicated operation
      - What recovery does NOT restore (RBAC assignments, Event Grid subscriptions)
      - Why an agent must never call Vaults_PurgeDeleted