Deployment Reference

Bicep Deployment

Use this page when you need to inspect or modify the Bicep templates that sit underneath the repo's primary deployment workflow.

Repo IaC layer Best used with AZD orchestration Container runtime underneath
AZD deployment Enterprise networking

The Bicep templates are the infrastructure backbone behind the repo’s recommended deployment flow. Most teams should still apply them through AZD, but this page is where you orient yourself when you need to inspect or customize the infrastructure directly.

Understand the IaC baseline

Use this path when you need to know what the repo is actually provisioning rather than treating AZD as a black box.

Customize safely

Review or modify the files in deployers/bicep/ when your organization needs network, SKU, or resource-layout changes.

Preview before applying

Keep azd provision --preview in the flow so you can inspect infrastructure impact before applying it to a shared environment.

Remember the runtime model

The supported Bicep path still lands on container-based App Service, so startup behavior follows the container entrypoint rather than native Python app settings.

Use Bicep as the infrastructure layer, not a separate platform story

In this repo, Bicep is best understood as the IaC layer beneath AZD rather than a competing deployment experience. Start from the AZD guide unless your goal is specifically to inspect or change the infrastructure modules themselves.

When to choose this path

  • You want to inspect or customize the Bicep templates in deployers/bicep/
  • You want to understand the infrastructure used by the azd deployment flow
  • You are troubleshooting infrastructure behavior or preparing Bicep module changes
  1. Start with the Azure Developer CLI deployment guide.
  2. Review or modify the Bicep files under deployers/bicep/.
  3. Use azd provision --preview or azd up to apply those changes through the supported workflow.

References