Configuring Approved Models for Agent Responses in Copilot Studio
A company uses an agent in Copilot Studio that produces structured responses using a reusable instruction template. The responses follow the required tone and format. During a compliance review, the team discovers that the responses were generated using a model that is not on the approved list. The company requires that the reusable instruction template continues to be used and the model used for prompt-driven responses meets governance requirements. The solution must ensure that prompt-driven responses are generated using an approved model. You need to configure the solution that meets the requirements. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Insight
This question tests the separation of model selection and prompt engineering; the common trap is attempting to restrict model usage via prompt instructions rather than administrative configuration.
Learn how to enforce governance requirements by selecting an approved model from the Microsoft Foundry catalog while maintaining existing reusable instruction templates in Copilot Studio agents.
Candidates often choose option F, believing that adding a constraint to the instruction template will force the agent to use a specific model. This is incorrect because prompts cannot override the underlying model configuration set in the agent settings.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct actions are A and C. To meet governance requirements, you must explicitly select an approved model from the Microsoft Foundry model catalog (Option A). This ensures the underlying LLM used for prompt-driven responses is compliant. Since the requirement states the reusable instruction template must continue to be used, ensuring it is applied to the agent (Option C) satisfies the business continuity aspect without violating governance.Why the Other Options Are Wrong
Option B is incorrect because Azure AI Search is a grounding source for data retrieval, not for enforcing model selection or governance policies on the base model. Option D is irrelevant; publishing the agent does not automatically update or validate the model against an approved list. Option E addresses transparency but does not solve the core issue of using an unapproved model. Option F is the most common distractor; prompts cannot control which backend model is invoked—model selection is a configuration setting, not a text instruction.Community Comment Notes
Community consensus strongly supports rejecting Option F. As user Rami7 noted, 'Prompts cannot control which underlying model is selected,' highlighting that model governance is an administrative task. Another commenter confirmed that 'F - Prompts can't enforce which model is actually used.' The community correctly identifies that model selection is a configuration setting distinct from prompt logic.Exam Strategy
Always distinguish between what a prompt can do (guide tone, format, logic) and what agent settings control (model choice, tools, grounding). Governance questions typically require administrative configuration changes rather than prompt engineering tweaks.
Frequently Asked Questions
Can I restrict models using the instruction template?
No. Prompts cannot control the underlying model selection. You must configure the approved model in the agent's settings via the Foundry catalog.
Does Azure AI Search enforce model governance?
No. Azure AI Search is used for grounding responses with enterprise data, not for controlling which LLM model processes the prompt.