Update JSON structure in management group API documentation#128623
Update JSON structure in management group API documentation#128623meghanagupta95 wants to merge 2 commits into
Conversation
The PUT MG's request body was missing the "details" field. This would have led to the MG being created under the root MG by default. Placing the "parent" JSON under the "details" key ensures the provided parent id is respected.
|
@meghanagupta95 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
Bot
added
azure/svc
Change sent to author
azure-governance/subsvc
labels
|
@meghanagupta95 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit ccc7aee: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Management Group PUT request body example to correctly nest parent under properties.details, preventing unintended creation under the root management group.
Changes:
- Add
properties.detailswrapper to the request body JSON example - Ensure the JSON example is structurally complete (adds the missing closing brace)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
|
Learn Build status updates of commit 9990b05: ✅ Validation status: passed
For more details, please refer to the build report. |
The PUT MG's request body was missing the "details" field. This would have led to the MG being created under the root MG by default. Placing the "parent" JSON under the "details" key ensures the provided parent id is respected.