nav: relabel Builder track to Microsoft Scout (tool + description) - #8
Open
dahans-msft2 wants to merge 1 commit into
Open
nav: relabel Builder track to Microsoft Scout (tool + description)#8dahans-msft2 wants to merge 1 commit into
dahans-msft2 wants to merge 1 commit into
Conversation
dahans-msft2
force-pushed
the
scenario-2-nav-scout
branch
from
August 6, 2026 04:24
8dab791 to
beb1c3c
Compare
dahans-msft2
force-pushed
the
scenario-2-nav-scout
branch
from
August 6, 2026 04:28
beb1c3c to
6a5ac86
Compare
dahans-msft2
force-pushed
the
scenario-2-nav-scout
branch
from
August 6, 2026 04:33
6a5ac86 to
2c61426
Compare
dahans-msft2
force-pushed
the
scenario-2-nav-scout
branch
from
August 6, 2026 04:35
2c61426 to
08caf84
Compare
Collaborator
Author
|
@maquinl - updating the tool description for builder level. Take a look and merge if good? |
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.
The Builder track in
paths.tsstill described a Copilot Studio picture — the tool read"Copilot Studio / Scout"and the blurb was about wiring up agents that hand off and firing a Teams alert. Scenario 2's Builder path is Microsoft Scout, whose flow is "an agent builds you a live dashboard, grounded on your files, that a teammate can run."Change (2 lines, same single-
tool-string mechanism the Base/Advanced tracks use):tool:"Copilot Studio / Scout"→"Microsoft Scout"desc: rewritten to match Scout — "Have Microsoft Scout build it for you — a live dashboard grounded on your real files that a teammate can run in one step."Flows through the Start Building dropdown and every
<BuildMatrix>automatically. Aligns with moving off Copilot Studio.Not in this PR (flagging for a follow-up): the Builder
guidesLinkanchor (#copilot-studio) and its sevenstudio-*guide pages are still Copilot Studio content.