Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request updates the Agent 365 guided setup documentation to restore Resource Group and Location field requirements for self-hosted (non-Azure deployment) scenarios. These fields were previously removed but are actually needed by the CLI for blueprint creation and potential resource group operations, even when not deploying to Azure Web Apps.
Changes:
- Added Resource Group and Location fields to the self-hosted deployment configuration table in the guided setup instructions
skg-marimuthu
approved these changes
Feb 13, 2026
tmlsousa
approved these changes
Feb 13, 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
3 participants
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.
Adding resource group and location values back for non-azure deployment scenario as these are still needed for blueprint and endpoint creation.