Reorder config sections in DAB MCP documentation to follow repository convention #3033
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.
Why make this change?
Addresses feedback on #2971 requesting the example configuration structure follow the repository convention of placing
runtimebeforeentities.What is this change?
Reordered the JSON sections in the example
dab-config.jsonstructure indocs/Testing/ai-foundry-integration.md:{ "data-source": { ... }, "runtime": { ... }, // Moved before entities "entities": { ... } }This matches the standard ordering used throughout the codebase (e.g.,
samples/basic-empty-dab-config.json, test configurations).How was this tested?
Documentation-only change; no functional testing required.
Sample Request(s)
N/A - Documentation update only.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.