Add troubleshooting guidance for Azure DevOps pipeline "azd init" errors #3853
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.
This PR addresses a common issue where users encounter "ERROR: no project exists; to create a new project, run azd init" when deploying .NET Aspire projects via Azure DevOps pipelines.
Problem
Users following the Azure DevOps deployment documentation experience pipeline failures during the provisioning step because
azd init
generates files (azure.yaml
and.azure
folder) that are typically not committed to repositories. When pipelines run in clean environments, these files don't exist, causingazd
commands to fail.Solution
Added comprehensive troubleshooting documentation that provides:
azd init
in the pipeline with proper flags:Changes Made
aca-deployment-github-actions.md
--from-code
flag usage.azure
folder contentsAll changes follow the Microsoft Writing Style Guide and pass markdown linting.
Fixes #983.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Internal previews