Codex skills for Microsoft Azure
These Azure skills cover App Service, Azure Functions, Bicep, Microsoft Entra ID and the ASP.NET Core apps that run on them. Codex deploys through a staging slot that must pass its health check before a swap, previews every Bicep change with what-if, moves Functions to the current programming model, and gives workloads managed identities or federated credentials instead of client secrets.
Start with these 3
- Azure Functions Triggers, bindings and durable workflows done right Codex identifies which Azure Functions programming model a project uses, moves it to the current one, and picks a hosting plan from real timeout and networking needs. Bindings connect through managed identity with data-plane roles, Durable Functions orchestrators stay deterministic, and everything runs under Core Tools and Azurite before a confirmed publish.
- Azure App Service Ship through the staging slot, never around it Codex deploys App Service web apps to a staging slot, checks the health route, and swaps with preview so production settings are applied before traffic moves. Secrets become Key Vault references read by a managed identity, environment-specific values are sticky, and startup command, port and runtime are set explicitly so boot failures are diagnosable.
- Azure Bicep Typed templates, a what-if before every deploy Codex writes Bicep with typed, validated parameters, per-environment .bicepparam files and symbolic references instead of string-built resource IDs. It checks Azure Verified Modules before hand-rolling one, keeps secrets out of outputs, uses deterministic guid() names for role assignments, and shows a what-if before any deployment runs.
2 more Microsoft Azure skills
General skills with Microsoft Azure guidance
Not built around Microsoft Azure, but they include steps or tools for it. Not part of the install-all command.
-
Godot 4 C#
Godot with .NET, minus the generator surprises -
OAuth 2.1 and OIDC
SSO logins that validate every hop -
GitHub Actions Security
Read-only tokens, SHA pins, no injected titles -
OpenTelemetry
One connected trace per request, vendor-neutral -
Regex Crafting
Regexes with test tables and no catastrophic backtracking -
Problem Details Errors
One error shape clients can branch on -
Modern C#
Nullable on, boilerplate off, analyzers enforcing it -
PowerShell Scripting
pwsh scripts that stop on errors and honour -WhatIf -
Document AI and OCR
Route each page, keep confidences, review the doubtful -
Text to Speech
Natural narration with names pronounced right -
Secrets Management
No plaintext keys, rotation you have rehearsed -
Container Registries
Immutable tags, digest deploys, safe cleanup
Every Microsoft Azure skill in one command
Installs these 5 into ~/.agents/skills/. Add --project after -- to install into the current repository instead.
The installer is a 104-line POSIX shell script. It fetches the skills you name from codexskills.dev and unpacks each into its own folder in your skills directory. No sudo, no telemetry, and every skill page shows the full SKILL.md first. Read install.sh
curl -fsSL codexskills.dev/install.sh | sh -s -- azure-functions azure-app-service azure-bicep azure-entra-id aspnet-core Microsoft Azure FAQ
Is there a Codex skill for migrating Azure Functions to the current programming model?
Azure Functions first identifies which model a project uses, such as Node.js v3 with function.json versus v4 with app.http, or .NET in-process versus the isolated worker, and moves it to the current one. It picks Flex Consumption or Premium from real timeout and networking needs, runs everything under Core Tools and Azurite locally, and asks before func azure functionapp publish. Durable Functions orchestrators are kept deterministic, with no Date.now() or I/O inside them.
Can Codex write Azure Bicep instead of ARM templates?
Azure Bicep writes main.bicep with typed, validated parameters and per-environment .bicepparam files, checks Azure Verified Modules before hand-rolling one, and shows a what-if preview before any deployment runs. It never puts secrets such as a listKeys() result in outputs, because outputs land in deployment history, and names role assignments with deterministic guid() values. Converting ARM JSON or portal-created resources to Bicep is in scope.
How should my API validate Microsoft Entra ID tokens?
Microsoft Entra ID registers APIs with v2 tokens, scopes and app roles, and validates issuer, audience, tenant and scope or role on every request. It rejects ID tokens and Graph access tokens at your API and keys users on tid plus oid rather than email. Tenant-wide actions such as admin consent or credential resets wait for your confirmation.
How do I install all 5 Microsoft Azure skills at once?
Pass every name to the installer in one command: curl -fsSL https://codexskills.dev/install.sh | sh -s -- azure-functions azure-app-service azure-bicep azure-entra-id aspnet-core. Add --project right after -- to put them in the current repository's .agents/skills/ so your team gets them too.
Which Microsoft Azure skill should I try first?
Azure Functions is the closest fit for most Microsoft Azure work. Mention it with $azure-functions in a prompt to load it on purpose; after that, Codex picks it up on its own whenever a task matches.