Skip to content

add new course on Foundry Toolkit#10027

Draft
softchris wants to merge 6 commits into
microsoft:mainfrom
softchris:patch-5
Draft

add new course on Foundry Toolkit#10027
softchris wants to merge 6 commits into
microsoft:mainfrom
softchris:patch-5

Conversation

@softchris

Copy link
Copy Markdown
Contributor

No description provided.

@softchris softchris marked this pull request as draft July 8, 2026 13:09
@rremi6061-glitch

Copy link
Copy Markdown

Bonjou

@carlotta94c carlotta94c left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First chapter review


This is where most implementation work happens. You will use it to move from model exploration to agent development and then into validation. As your project grows, this section becomes a practical day-to-day control center.

For example, a common loop is: open Model Catalog, test a prompt in Playground, then inspect behavior in Agent Inspector without leaving the same extension area.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the suggested path actually makes sense, as you don't usually move from playground to agent inspector. Agent inspector is more for pro-code agent debugging. Can we just skip this sentence?

- **Build**: Agent creation, Agent Inspector, hosted agent management, and playground workflows.
- **Monitor**: Tracing, evaluations against expected behavior, and model profiling.

After building and monitoring, you still need support and feedback channels to keep improving.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest rephrasing this as follows: "As you build and test your soultion, you might need support..."

Once you've installed Foundry Toolkit, you should know the layout and where to find the tools you need. The extension is organized into three main sections: My Resources, Developer Tools, and Feedback.

Once Foundry Toolkit is installed, the UI is organized into sections that mirror how teams actually build. Learning this layout early saves discovery time and helps new teammates get oriented much faster.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think those 2 sentences might be merged into one, to avoid redundancy.


1. Open Foundry Toolkit and click into My Resources.
2. Expand one available section, even if it is currently sparse.
3. Say out loud what you can see now that you could not see five minutes ago.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what you mean here - you see more stuffs under my resources just if you create models/agents or connect to an existing Foundry project. Since they are in the set up phase, they shouldn't be able to see much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants