Skip to content

Scope azd deployment job to a GitHub Environment - #90

Closed
Arun Sekhar (achandmsft) wants to merge 1 commit into
mainfrom
chore/scope-deploy-job-environment
Closed

Scope azd deployment job to a GitHub Environment#90
Arun Sekhar (achandmsft) wants to merge 1 commit into
mainfrom
chore/scope-deploy-job-environment

Conversation

@achandmsft

Copy link
Copy Markdown
Collaborator

Binds the azd deployment job in azure-dev.yaml to a GitHub production Environment.

Scoping the deploy job to an Environment lets deployment configuration be managed through environment protection rules (required reviewers, branch/tag restrictions, wait timers) and keeps deployment-time configuration grouped per environment. This aligns with the recommended azd CI/CD pipeline setup.

No workflow logic changes - only adds environment: production to the build job.

Note: a production environment may need to be created in repo settings (Settings -> Environments) for the job to run; reviewers can confirm during review.

@achandmsft

Copy link
Copy Markdown
Collaborator Author

Closing in favor of #91, which removes the unused AZURE_CREDENTIALS reference at the root instead of scoping the job to an environment.

@achandmsft
Arun Sekhar (achandmsft) deleted the chore/scope-deploy-job-environment branch June 16, 2026 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant