Forum Discussion
Copilot Chat Adoption Feedback : Model Selection Governance and Prompt Library Reusability ?
Hello,
As part of several Microsoft Copilot adoption projects that I am currently leading across different organizations, two questions frequently come up from both users and administrators.
The first concerns the ability to lock or enforce a specific model in Copilot Chat for certain use cases.
Several customers would like to guide users toward a particular model when working on specific scenarios (Opus for example) that require a certain level of reasoning, behavior, or response quality. To date, I have not found any official documentation or roadmap information indicating whether this capability is planned.
The second concerns the Prompt Gallery / Prompt Library.
Saved prompts are very useful for starting a conversation, but they do not appear to be reusable directly within an ongoing conversation. In several business scenarios, users would like to chain multiple approved prompts within the same conversation in order to preserve context while applying different working methods, analysis steps, or processes.
Are there any planned developments regarding these two topics?
- The ability to lock or enforce a specific model in Copilot Chat.
- The ability to use prompts from the Prompt Gallery / Prompt Library during an already active conversation.
I have not found any official information on these topics in Microsoft Learn documentation or in the Microsoft 365 roadmap. However, these capabilities seem likely to facilitate user adoption and help standardize usage patterns across organizations.
2 Replies
Have you tried accessing the Prompt Lab (That's what the library/gallery is called in our version of Copilot anyway) through the three dot menu in the top right corner in help and tips?
This works in an existing conversation for me. Based in Australia, milage may vary depending on location.
I don't know why Microsoft has hidden it there, took me a while to find it the first time.
Locking or enforcing a specific model may be possible in your tenant by a system admin depending on setup, for example by enabling the desired one and disabling all others.
It can be handled by a specific agent created and deployed by Copilot Studio too, you can choose the model for the agent, if one is created through that process. If you did lock the model on the admin side that would likely affect all users at all times though, so everyone would have to use only that model in your tenant. This may not be what you intend.I have not seen any information about these topics either, CoralieSimonaire . It'd be worth sharing this in the Champions Community call, relevant upcoming AMA sessions or send through appropriate channels as product feedback.
It is interesting to see these common feedback from multiple organizations. I'd be curious to know what you've recommended to keep them going. And I'd be happy to brainstorm if you are still looking for ways to manage this in the interim :)
