Python Appservice Deploy — Agent Skill by Microsoft

From the author

Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux. WHEN: "Flask App Service", "Django App Service", "FastAPI App Service", "deploy Python to App Service". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform/Bicep/IaC, full infra — use azure-prepare.

— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured, idempotent workflow for deploying Python applications (Flask, Django, FastAPI) to Azure App Service on Linux. It handles the creation of necessary Azure resources—including Resource Groups, App Service Plans (P0v3), and Web Apps—while enforcing best practices like server-side builds and proper startup configuration. The process includes automated normalization of shell scripts to ensure compatibility and provides a reliable path for both standard CLI-based deployments and those utilizing Azure Developer CLI (azd) configurations.

What it does

Automatically creates or validates Azure Resource Groups, App Service Plans, and Web Apps.
Configures server-side builds via SCM_DO_BUILD_DURING_DEPLOYMENT.
Normalizes Linux shell scripts to prevent line-ending issues during deployment.
Sets appropriate startup commands for FastAPI applications.
Packages the application code into a clean ZIP archive, excluding unnecessary files.
Supports both standard Azure CLI and azd-based deployment workflows.

When to use it

When you need to deploy a Python Flask, Django, or FastAPI application to Azure App Service Linux.
When you want to automate the provisioning of the required Azure infrastructure alongside the code deployment.
When you need a repeatable, error-checked deployment process for Python web apps.
When you are working with a standard Python project structure and require a reliable deployment pipeline.

Advantages

Reduces manual configuration by deriving sensible defaults for resource names and regions.
Ensures cross-platform compatibility by normalizing line endings in scripts.
Prevents common deployment failures through pre-packaging validation.
Provides a consistent, idempotent approach to resource creation.
Integrates seamlessly with existing Azure CLI and azd workflows.

Usage examples

“Deploy my Flask app to Azure App Service.”: The agent will prompt for an app name, then automatically create the necessary Resource Group, P0v3 Linux App Service Plan, and Web App, finally deploying the code.
“Deploy my FastAPI project to Azure.”: The agent will configure the Web App with the required uvicorn startup command and deploy the code to an Azure App Service Linux instance.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/python-appservice-deploy/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip python-appservice-deploy.zip -d .agents/skills

Documentation by Microsoft

Python on Azure App Service — Code Deploy

Deploys Python (Flask, Django, FastAPI, generic) code to Azure App Service Linux (P0v3, Python 3.14). Creates RG + Plan + Web App if missing. Hand off to azure-prepare for VNet, Key Vault, databases, or IaC.

MCP tools used: mcp_azure_mcp_subscription_list, mcp_azure_mcp_group_list, mcp_azure_mcp_appservice, mcp_azure_mcp_azd (when azure.yaml is present).

Workflow

Prerequisite: Verify the latest stable Azure CLI; update with approval and recheck if needed.

Resolve context — smart defaults, minimal prompts. Only the app name is interactive; RG (<app>-rg), Plan (<app>-plan), region (current az default or eastus2), subscription are derived. create-app.md §1.
Detect framework (advisory, never blocks). detect.md.
Choose path — azure.yaml host: appservice → deploy-azd.md; else deploy-azcli.md.
Ensure RG → Plan (P0v3 --is-linux) → Web App (--runtime "PYTHON:3.14") exist. Before creating a plan, invoke azure-quotas to check quota availability. On transient ARM errors, follow transient-retry.md. create-app.md.
Set startup — Flask/Django: none (Oryx auto-detects). FastAPI: always python -m uvicorn main:app --host 0.0.0.0. Other: warn. startup-commands.md.
Set SCM_DO_BUILD_DURING_DEPLOYMENT=true.
Deploy — azd deploy or az webapp deploy --type zip --track-status false --enriched-errors true.
STOP. Print the post-deploy message (post-deploy-message.md) and end the turn.

Hard rules

LINUX SCRIPTS — normalize selected shell/startup files to LF, then verify no CR bytes remain. Stop on normalization, validation or packaging failure; deploy only a fresh package.
DJANGO REMOTE BUILDS — require STATIC_ROOT and successful system/collectstatic checks before packaging.
⛔ NO POST-DEPLOY VERIFICATION — after deploy returns, do not run az webapp log tail, curl, Invoke-WebRequest, or any health probe. App Service needs 2–3 min to warm; a quiet log or early 5xx is not failure.
⛔ SHELL SAFETY — for --runtime always use "PYTHON:3.14" (colon). Never "PYTHON|3.14" (pipe is a shell operator).
⛔ NEVER az webapp up — deprecated. Use Step 7 commands.
✅ URL FORMAT — present endpoints as https://... URLs.

Error Handling

See errors.md for the full symptom → cause → fix matrix. Quick triage: missing plan/app → re-run Step 4; container ping timeout on 8000 → fix startup (Step 5); ModuleNotFoundError after deploy → ensure Step 6 ran, redeploy.

Files

ATTRIBUTION.mdAdded by AutoGineer1004 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md3.2 KiB
references/create-app.md6.2 KiB
references/deploy-azcli.md6.8 KiB
references/deploy-azd.md3.4 KiB
references/detect.md3.6 KiB
references/errors.md3.8 KiB
references/post-deploy-message.md4.4 KiB
references/startup-commands.md4.3 KiB
references/transient-retry.md2.3 KiB
scripts/generate-app-name.ps1Script1.7 KiB
scripts/generate-app-name.shScript1.8 KiB
scripts/retry-az-create.ps1Script2.1 KiB
scripts/retry-az-create.shScript1.9 KiB

references/deploy-azd.md

Deploy via `azd`

Use this path when the workspace already has an azure.yaml whose service host is appservice.

When to use

Condition	Use azd?
`azure.yaml` exists AND `services.<name>.host: appservice`	✅ Yes
`azure.yaml` exists but targets Container Apps / Functions / etc.	❌ Hand off to `azure-prepare`
No `azure.yaml`	❌ Use deploy-azcli.md

Confirm host target

# Look for `host: appservice` under services in azure.yaml
grep -E "host:\s*appservice" azure.yaml

# Look for `host: appservice` under services in azure.yaml
Select-String -Path azure.yaml -Pattern 'host:\s*appservice'

If no match → use the az CLI path.

Verify the latest stable Azure CLI before deployment. Django remote builds require STATIC_ROOT and successful python manage.py check and python manage.py collectstatic --noinput.

Before every azd up/azd deploy, run the shared LF normalization and validation example on the service's actual package inputs, including generated startup scripts. Use its shell-specific exit guard. Package only after normalization/validation succeeds; any normalization, validation or packaging failure stops deployment. Require a fresh package, never a cached artifact from a failed attempt.

Authenticate

azd auth login --check-status || azd auth login

azd auth login --check-status
if ($LASTEXITCODE -ne 0) { azd auth login }

Provision (first time only)

If no azd environment exists in this folder:

Before creating a plan, invoke azure-quotas to check quota and regional availability. Ask before changing a user-specified region; stop if quota is unavailable or unverifiable rather than switching SKU.

azd env new <env-name>
azd env set AZURE_LOCATION <region>
# Optional: override default SKU via the template's parameters
azd env set APP_SERVICE_SKU P0v3

Then provision + deploy in one call:

azd up || exit 1

azd up
if (-not $? -or $LASTEXITCODE -ne 0) { throw "azd provisioning/packaging/deployment failed" }

Deploy code only (subsequent deploys)

azd deploy || exit 1

azd deploy
if (-not $? -or $LASTEXITCODE -ne 0) { throw "azd packaging/deployment failed" }

After azd deploy returns, stop. Do not run azd monitor, az webapp log tail, or any HTTP probe.

Report endpoint to the user

⛔ Do NOT probe the endpoint (no curl, no Invoke-WebRequest) and do NOT tail logs as a verification step. App Service can take 2–3 minutes after deploy before the site responds.

Read the endpoint from azd without hitting the site:

# bash
azd env get-values | grep -E '^SERVICE_.*_URI='

# PowerShell
azd env get-values | Select-String "SERVICE_.*_URI"

Present the URL with the https:// prefix and the post-deploy message from post-deploy-message.md, then end the turn.

Notes

⛔ Do not run azd init -t <template> in an existing workspace — it can destroy user code. Only azd init (no template) is safe inside an existing project.
If azd up provisions infra that doesn't match P0v3 Linux, the underlying template owns that decision — don't fight it. Note this to the user.
If azd deploy fails because no environment exists, fall back to azd env new then re-run.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

What our scanner noticed· Low risk

Instructions that use the network
Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Shipping And Launch
Addy Osmani· Community
A comprehensive framework for managing safe, observable, and reversible production software deployments.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Quantized Export
Seth Hobson· Community
Export a promoted fine-tuned model in the right deployment format — merged safetensors, LoRA-only, GGUF with imatrix, or FP8. Use after a checkpoint passes promotion, when choosing a quantization format for a target device, or when an exported model fails its smoke test.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository42.3k
Deployment Pipeline Design
Seth Hobson· Community
Design robust, secure, and automated CI/CD pipelines with multi-stage promotion, approval gates, and progressive delivery strategies.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository42.3k
Gitops Workflow
Seth Hobson· Community
A guide to implementing GitOps workflows for Kubernetes using ArgoCD and Flux.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Spark Environment Setup
Seth Hobson· Community
Set up and troubleshoot ML training and inference environments on NVIDIA DGX Spark hardware.
Cloud and DevOpsClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository42.3k
Cloud Infrastructure Deployment Engineer
Seth Hobson· Community
An expert deployment engineer agent specializing in CI/CD pipelines, GitOps workflows, and advanced containerized deployment automation.
Cloud and DevOpsClaude Code
MITGitHub stars of the source repository42.3k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download python-appservice-deploy.zip