docs: Update Copilot Studio setup instructions & Testing Guide - #88
Merged
Roopan-Microsoft merged 3 commits intoAug 26, 2026
Merged
Conversation
Updated agent names and added important naming instructions in the deployment guide.
Updated supplier name in the Testing Guide to reflect the correct company experiencing production delays.
Contributor
Author
|
Seth Steenken (@sethsteenken), as discussed |
Copilot started reviewing on behalf of
Jordan Bean (jordanbean-msft)
August 19, 2026 18:12
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Copilot Studio deployment and testing documentation to reduce configuration mismatches between the Copilot Studio connected-agent names and the system prompt, and to align a sample testing scenario with available sample data.
Changes:
- DeploymentGuide: Require exact Copilot Studio connected-agent names
Foundry Chat AgentandFabric Data Agent(matching system prompt references). - TestingGuide: Update the sample test email supplier/account name to
Worldwide Importersto match sample data.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/copilot/DeploymentGuide.md | Clarifies required external-agent connection names (Foundry/Fabric) for correct sub-agent invocation in Copilot Studio. |
| docs/copilot/TestingGuide.md | Updates a test scenario email to use an entity that exists in the provided sample data. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Roopan-Microsoft
approved these changes
Aug 26, 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
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 updates the deployment and testing documentation for Copilot Studio to clarify agent naming conventions and improve test scenario accuracy.
Deployment documentation improvements:
DeploymentGuide.mdto require that the Foundry agent be named exactlyFoundry Chat Agentand the Fabric agent be named exactlyFabric Data Agent, with explicit notes that these names must match the system prompt references. The agents not being named exactly the same as the system prompt names was causing Copilot Studio to not call the sub agents.Testing documentation update:
TestingGuide.mdfrom "Mountain Peak Manufacturing" to "Worldwide Importers" since "Mountain Peak Manufacturing" doesn't exist in the sample data.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Check that Copilot Studio is able to call the Foundry Chat Agent & the Fabric Data Agent correctly and that the Fabric Data Agent is able to retrieve inventory data for an account that exists in the sample data (Worldwide Importers)
Other Information