Updates & recovery
Use the existing deployment guides for changes to a deployed environment. Choose your infrastructure provider below and follow the linked procedure, including its prerequisites, validation and recovery guidance.
azd init --template Azure/agent-landing-zone . is for a new local project,
not an update or recovery command. For an existing installation, keep its
reviewed source, select the existing environment with
azd env select <environment-name> and preserve provider, inputs and private
deployment records. A clean replacement runner must restore that same
revision and the records required by the linked recovery procedure.
| Task | Bicep | Terraform |
|---|---|---|
| Review infrastructure changes | Review changes | Review or recover |
| Retry a full-stack installation | Retry the same installation | Retry and recover |
| Redeploy applications only | Redeploy applications | Application-only changes |
| Add MCP server or select NL2SQL tools | Select, provision and deploy | Select, provision and deploy |
| Review component outbound access | Read-only review | Provisioning review |
| Review recovery and rollback | Rollback | Update and recover |
| Remove the foundation | Remove the foundation | Remove the foundation |
| Remove a full-stack environment | Remove an environment | Remove the environment |
For failures, use Troubleshooting. For application settings, administration and monitoring, use Agent Application operations.
For outbound-access changes, retain the policy ownership and subnet boundaries. Remove owned rules with the current reconciliation workflow before reverting hooks.
For MCP, server compute and startup toolset selection are separate.
MCP_TOOLSETS=[] registers zero tools; ["nl2sql"] needs its declared
catalog/model dependencies, SQL-owner approvals and active metadata version.
Provision matching dependencies and restart/redeploy after toolset changes.
Deselection stops initialization but does not delete retained catalog data or automatically revoke old grants. Review retirement explicitly; recovery does not run direct SQL inside the orchestrator. Embedding model/dimension changes need reindexing, not just a runtime-setting refresh.
PostgreSQL data protection
Optional PostgreSQL recovery/removal requires the original immutable creation-intent record and independent server CanNotDelete lock outside both provider graphs/state. Same-binding protection recovery is supported; missing/corrupt records are not adoption/deletion permission. Down/disable/replacement stop before either provider teardown. Manual removal needs backup/PITR review, exact inventory, consumer shutdown, data-owner approval and state/discovery reconciliation; preserve shared DNS/RGs. Privileged bypass and the partial-provision window remain risks. SQL bootstrap is manual and restartable across two databases, not cross-database atomic.