Deployment Reference
Choose the right Simple Chat deployment path and understand when each deployment model is the right operational fit.
This section is the deployment decision map. Use it after you already understand the basics and need the path-specific guidance for the rollout model your team actually uses.
Azure Developer CLI
The most current and best-supported path. Use it when you want provisioning, configuration, and deployment handled in one repo-aligned workflow.
Azure CLI with PowerShell
Use this when you want a script-driven deployment flow with more control over sequencing and recovery than the default AZD experience.
Bicep and Terraform
Use these when infrastructure-as-code ownership is the main concern and your team needs more direct control over templates or state.
Manual native Python notes
Use the manual notes only when you are intentionally operating a native Python App Service deployment rather than the repo's container deployers.
Pick the runtime model first
The most important split is not AZD versus Terraform. It is container-based App Service versus native Python App Service. The repo's main deployment paths are container-based, and that changes startup-command handling, upgrade flow, and rollback expectations.