fix: merging dev to main - #610
Merged
Merged
Conversation
Priyanka-Microsoft
requested review from
Avijit-Microsoft,
Dongbumlee,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
dgp10801,
nchandhi and
toherman-msft
as code owners
April 17, 2026 05:29
Avijit-Microsoft
temporarily deployed
to
production
April 17, 2026 12:15 — with
GitHub Actions
Inactive
Avijit-Microsoft
had a problem deploying
to
production
April 17, 2026 12:19 — with
GitHub Actions
Failure
Avijit-Microsoft
had a problem deploying
to
production
April 17, 2026 12:45 — with
GitHub Actions
Failure
Avijit-Microsoft
temporarily deployed
to
production
April 17, 2026 12:51 — with
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
April 20, 2026 07:04 — with
GitHub Actions
Inactive
Avijit-Microsoft
had a problem deploying
to
production
April 20, 2026 07:08 — with
GitHub Actions
Failure
Avijit-Microsoft
had a problem deploying
to
production
April 20, 2026 07:33 — with
GitHub Actions
Failure
Avijit-Microsoft
temporarily deployed
to
production
April 20, 2026 07:38 — with
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
April 20, 2026 09:09 — with
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
April 20, 2026 09:12 — with
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
April 20, 2026 10:12 — with
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
April 20, 2026 10:19 — with
GitHub Actions
Inactive
Roopan-Microsoft
approved these changes
Apr 20, 2026
|
🎉 This PR is included in version 1.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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
This pull request significantly updates the
LocalDevelopmentSetup.mddocumentation to clarify and streamline the local development process for the solution accelerator. The changes provide more robust instructions for setting up the required Azure resources, configuring environment files, running backend services, and troubleshooting common issues. The documentation now better supports both Visual Studio and dotnet CLI workflows, emphasizes the importance of correct Azure deployment, and helps prevent common configuration errors.Azure Deployment and Prerequisites:
Azure Authentication and Permissions:
Backend Services Setup and Execution:
appsettings.Development.jsonfiles, including warnings about stale or incorrect App Configuration URLs and the need to use the full template files.Frontend Setup:
http://localhost:5000), clarified.envconfiguration, and improved documentation for environment variables and dependency installation. [1] [2]Troubleshooting and Common Issues:
These updates make the local development guide more robust, user-friendly, and resilient to common pitfalls, especially for new contributors or those unfamiliar with Azure-based development workflows.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information