Instruction file imported from ivegamsft/work-tracker (.github/instructions/azure.instructions.md). Copyright stays with the author.

Azure Standards

Name: azure
Author: ivegamsft

Use this instruction when changes touch Azure-hosted applications, SDK usage, infrastructure, or operational configuration.

Expectations

Prefer managed identity for Azure-hosted workloads over connection strings and access keys.
Never hardcode credentials. Use Key Vault or secure environment configuration.
Use least privilege for both management-plane and data-plane access.
Add retries, timeouts, and logging for transient cloud operations.
Prefer current Azure services and current SDK versions over legacy service patterns when starting new work.
Keep regional, quota, and cost implications visible when proposing Azure resources.

Review Lens

Is authentication appropriate for where the code will run?
Are secrets and certificates kept out of source control?
Are Azure-specific failure modes handled clearly?
Does the change require infrastructure, RBAC, or deployment documentation updates?

{ "ocm": "1", "id": "ivegamsft-work-tracker-azure-instructions", "kind": "skill", "name": "azure", "description": "Use when working on Azure services, Azure SDK integrations, Azure deployment configuration, or cloud architecture for Azure. Covers secure Azure defaults, authentication, and service usage patterns.", "publisher": "ivegamsft", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when working on Azure services, Azure SDK integrations, Azure deployment configuration, or cloud architecture for Azure. Covers secure Azure defaults, authentication, and service usage patterns." ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/ivegamsft/work-tracker", "path": ".github/instructions/azure.instructions.md", "ref": "b14bfd52ad94e81a902561d9302c777557a8906d", "url": "https://github.com/ivegamsft/work-tracker/blob/b14bfd52ad94e81a902561d9302c777557a8906d/.github/instructions/azure.instructions.md", "key": "ivegamsft/work-tracker/.github/instructions/azure.instructions.md" }, "applies_to": "**/*.{bicep,bicepparam,tf,tfvars,ps1,sh,md,json,yml,yaml,ts,js,py,cs}" }, "instructions": "# Azure Standards\n\nUse this instruction when changes touch Azure-hosted applications, SDK usage, infrastructure, or operational configuration.\n\n## Expectations\n\n- Prefer managed identity for Azure-hosted workloads over connection strings and access keys.\n- Never hardcode credentials. Use Key Vault or secure environment configuration.\n- Use least privilege for both management-plane and data-plane access.\n- Add retries, timeouts, and logging for transient cloud operations.\n- Prefer current Azure services and current SDK versions over legacy service patterns when starting new work.\n- Keep regiona", "cost": { "context_tokens": 236 } }

azure

About

Azure Standards

Expectations

Review Lens

Use it

Manifest

Reviews