Fix Foundry IQ tool approval instructions in Lab 04 and B1 - #242
Merged
Conversation
Point students at the kb-knowledgebase<id> tool added by the Foundry IQ connection instead of the standalone Azure AI Search tool, which the agent never invokes, so MCP approval requests actually fire. Fixes #235 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Fixes #235
Lab 04 and consolidated lab B1 told students to set Ask for approval for all tools on the Azure AI Search tool, but Foundry IQ attaches a
kb-knowledgebase<unique-id>tool that the agent actually invokes — so approval never fired andagent_client.pygot nomcp_approval_request.Updated both labs to target the
kb-knowledgebase...tool and clarified the note about the other tools that may appear. Docs-only change.