Notă
Accesul la această pagină necesită autorizare. Puteți încerca să vă conectați sau să modificați directoarele.
Accesul la această pagină necesită autorizare. Puteți încerca să modificați directoarele.
Start from a template from Microsoft, your organization, or the developer community when it provides a useful architecture for your project. After initialization, the template becomes a local set of standard azd files that you can review and edit for your requirements.
If you didn't select a template, browse the Azure Developer CLI template galleries. Review the template's source, documentation, license, security configuration, and deployment costs before you use it.
Initialize a template
Run azd init with the template repository name, path, or URL:
azd init --template <template>
For example, the following command initializes the hello-azd template:
azd init --template hello-azd
By default, azd creates a project directory for the template. To initialize it in the current empty directory, add . after the template argument:
azd init --template hello-azd .
Review the starting template
After initialization, inspect the local files and identify which parts you plan to retain, replace, or remove. Review:
- The services, source paths, languages, and hosts in
azure.yaml. - The resources and role assignments in the Bicep or Terraform files.
- The parameters and environment values required during provisioning.
- The application code, container definitions, hooks, and pipeline files.
- Any assumptions about subscriptions, regions, service tiers, networking, or external dependencies.
At this point, the existing template is your project's starting template. Continue to Explore and edit template files to review how the files work together, make changes, and test the result.
Related content
- Template development overview
- Azure Developer CLI templates
- Explore and edit template files
- Extend a template
- Azure Developer CLI template galleries
Request help
For information on how to file a bug, request help, or propose a new feature for the Azure Developer CLI, please visit the troubleshooting and support page.