Skills

Chapter 37 of 37

Python Appservice Deploy

Deploy Python (Flask/Django/FastAPI) code to Azure App Service Linux.

1 minute · 215 words · 4 sections

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

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 (opens in a new tab) §1.
Detect framework (advisory, never blocks). detect.md (opens in a new tab).
Choose path — azure.yaml host: appservice → deploy-azd.md (opens in a new tab); else deploy-azcli.md (opens in a new tab).
Ensure RG → Plan (P0v3 --is-linux) → Web App (--runtime "PYTHON:3.14") exist. On transient ARM errors, follow transient-retry.md (opens in a new tab). create-app.md (opens in a new tab).
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 (opens in a new tab).
Set SCM_DO_BUILD_DURING_DEPLOYMENT=true.
Deploy — azd deploy or az webapp deploy --type zip --track-status false.
STOP. Print the post-deploy message (post-deploy-message.md (opens in a new tab)) and end the turn.

Hard rules

⛔ 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 (opens in a new tab) 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.

Install this repository

$ npx skills add microsoft/azure-skills

» /plugin marketplace add microsoft/azure-skills

Skills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.

About this skill

Trigger

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 verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Licence: MIT
Also published for: GitHub — collapsed into this chapter because the copies are the same skill.
Source: skills/python-appservice-deploy/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/microsoft/azure-skills, branch main, last pushed 7 August 2026.

Licence

MIT — the text of every chapter is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

37 chapters found by walking the repository tree for SKILL.md, not by matching a directory convention. 6 distinct layouts observed: skills/*/SKILL.md, skills/azure-app-onboard/*/SKILL.md, skills/azure-kubernetes/*/SKILL.md, skills/microsoft-foundry/*/SKILL.md, skills/microsoft-foundry/models/deploy-model/*/SKILL.md, skills/microsoft-foundry/models/*/SKILL.md.

Duplicates collapsed

37 mirror copies folded into their canonical chapter — republished for GitHub. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 251°, chroma 0.167. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this chapter so the document has one h1 and no skipped levels:

Shifted “4 headings” from h1 to h2 so the chapter title is the only h1.

Spec compliance

6 editorial notes across 3 of 37 chapters. They are printed in the margin of each chapter rather than as errors here.

Deploy — 2 notes
Prepare — 2 notes
Scaffold — 2 notes

Images

Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Microsoft, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /microsoft/azure-skills.md, and each chapter at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Python on Azure App Service — Code Deploy

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

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 (opens in a new tab) §1.
Detect framework (advisory, never blocks). detect.md (opens in a new tab).
Choose path — azure.yaml host: appservice → deploy-azd.md (opens in a new tab); else deploy-azcli.md (opens in a new tab).
Ensure RG → Plan (P0v3 --is-linux) → Web App (--runtime "PYTHON:3.14") exist. On transient ARM errors, follow transient-retry.md (opens in a new tab). create-app.md (opens in a new tab).
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 (opens in a new tab).
Set SCM_DO_BUILD_DURING_DEPLOYMENT=true.
Deploy — azd deploy or az webapp deploy --type zip --track-status false.
STOP. Print the post-deploy message (post-deploy-message.md (opens in a new tab)) and end the turn.

Hard rules

⛔ 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.

Python Appservice Deploy

Python on Azure App Service — Code Deploy

Workflow

Hard rules

Error Handling

About this skill

Trigger

Colophon

Python Appservice Deploy

Python on Azure App Service — Code Deploy

Workflow

Hard rules

Error Handling

Appendix 37.1–37.12

ReferencesMarkdown · 8 files

Scripts4 files

About this skill

Trigger

Colophon

Appendix 37.1–37.12

ReferencesMarkdown · 8 files

Scripts4 files