docs: Update deployment script and azure.yaml to run script in proper sequence - #650
Merged
Roopan-Microsoft merged 1 commit intoJul 9, 2026
Merged
Roopan-Microsoft merged 1 commit into
Roopan-Microsoft merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
chaudhariniraj
requested review from
Avijit-Microsoft,
Prajwal1-Microsoft,
Roopan-Microsoft,
VinaySh-Microsoft,
Anish Arora (aniaroramsft),
dgp10801,
nchandhi and
Todd Herman (toherman-msft)
as code owners
July 9, 2026 09:24
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the deployment guidance and azd configuration so post-deployment tasks run in the intended order (ACR build/push first, then post-deployment configuration).
Changes:
- Updates the deployment guide to explicitly run the ACR build/push script before the post-deployment script.
- Disables the automatic postprovision hook in azure.yaml (no longer runs the post-deployment script automatically).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/DeploymentGuide.md | Adds/clarifies the manual post-deployment script sequence (ACR build/push → post-deployment). |
| azure.yaml | Removes the default postprovision hook behavior by replacing it with an empty hook map. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
Comment thread
docs/DeploymentGuide.md
Comment thread
docs/DeploymentGuide.md
Comment thread
azure.yaml
Roopan-Microsoft
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Removed the postprovision hook from the default azure.yaml, so azd up no longer automatically runs post-deployment scripts.
What changed
Impact
Default deployment now stops after infrastructure provisioning.
Post-deployment steps must be executed manually.
Breaking change note
This is a behavior change for users relying on the previous azd up flow, so the PR should clearly state that automatic post-deployment execution has been removed.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information