Copilot Prompt Gallery: Building a Team Prompt Library

Prompt Gallery in Microsoft Copilot Chat is one of the most underused features in the Microsoft 365 stack for organizations rolling out Copilot at scale. In my experience, few use them all, and those that do treat them as a personal convenience, where users can park commands they want to reuse. That’s great and a great place to start. However, for enterprise adoption and command sharing among colleagues, you can go a step further and use it as a team, department, or even company command library. You need to combine it with a suitable Microsoft Teams Team to get the full benefits. When you do, Prompt Gallery becomes a storage and distribution layer for rapid libraries across the organization, the missing piece in most Copilot adoption programs that struggle to move from individual experimentation to repeatable team practices. You can use this in the AI ​​tools that most of the organizations I contact on a daily basis will use. That said, it’s also not perfect and we call that out as well

This article discusses three things: the role of Prompt Gallery as a personal library, a mechanism for sharing saved commands into Microsoft Teams Teams, and configuring Teams to act as a searchable organization-wide library of commands. This concludes with a governance pattern that makes everything maintainable for the CIO.

Prompt Gallery as a personal prompt library

The Prompt Gallery resides within Microsoft 365 Copilot Chat and stores commands that users have created or saved. By default, saved commands are only visible to the user unless explicitly shared within a Team. The gallery presents three views: suggested commands that Microsoft curates, your commands (those created and saved by users), and Team commands (commands shared with Teams that users are members of). If you have actually shared the prompt to the Team

You can access commands via Microsoft 365 Copilot Chat, Copilot in Microsoft Teams. The stand-alone Copilot Prompt Gallery app was discontinued in July 2025, with the experience merged into the Prompt Gallery surface within Copilot Chat.

The saving workflow is very easy:

1. Run commands in Copilot Chat.
2. When the response comes back, hover over the command itself and select the Save command icon.
3. The command appears in the Your Commands tab in the Prompt Gallery, available for reuse in Copilot Chat, Teams, and Outlook.

This is absolutely useful on an individual level, but the commercial value only emerges when you treat saved commands as reusable assets and not personal shortcuts. A consultant who has created a working CARE-framed financial summary should not be the only person in his practice who can execute it.

Share saved commands to Microsoft Teams Teams

The sharing mechanism is a bridge between personal use and team practice. From the Your Commands tab in the Prompt Gallery:

1. Hover over the command you want to share and select Share command.
2. Select Share to team.
3. Select the target Microsoft Teams team from the list.

Once shared, the command is visible to every member of that Team under the Team commands tab in the Prompt Gallery and the Commands app. There is no separate approval step, no notifications, and no automatic appearance in the channel itself. Members must know it to see Teams prompts, or install the Prompt app somewhere visible.

An alternative path is to share the command as a link, generated from the Share command menu, which can be sent via Teams chat, email, or pasted into a SharePoint page. Link sharing is useful for cross-team distribution but lacks the central list that Team sharing provides.

One thing to note in the latest Microsoft Copilot Chat experience, the traditional ellipsis (three dots) menu in conversations that was present in most cases has been removed (at least that was the case for me), and with it direct access to features like Prompt Gallery. Currently, the only available ellipsis menu consistently appears on the new chat screen, meaning quick discovery is limited to starting a new conversation. You may find this frustrating – I know I have.

Configuring Microsoft Teams as an organization-wide quick library?

This is where most organizations stop. The default behavior leaves shared commands buried beneath the surface of the Prompt Gallery for individual users, where it’s no problem for people who already know them to look there. By sharing it with a team that people can access, you make it available for them to reuse

Choose your Team carefully

The receiving team can choose whatever best represents the people you want to share with. You may decide to create a dedicated rapid library team, or you may share it with existing project teams or departments. A custom prompt library gives you control over who can access. Explicit naming conventions, such as AI Command Library.

Channel structure

Channels on a library team should reflect how users search for guidance, not an organizational chart. A workable structure based on the work to be done:

• Summary for meeting notes, document summaries, and executive summaries.
• Drafting for emails, proposals and customer communications.
• Analysis for data interpretation, Excel-based instructions, and report critique.
• Translation and rewriting for tone changes, language conversion, and accessibility.
• Functional channels for HR, Finance, Legal and any specific role pattern that needs its own space.

Tagging and naming conventions

The search in the Prompts application is basically based on keywords against the title and description of the prompt. Therefore, tagging conventions are more important than a properly indexed system. Apply a naming pattern like [Function] [Audience] [Framework]For example Executive Summary, Board, CARE. The description field should include the model, framework used, and expected output format.

Governance

A fast library without governance will quickly become a quagmire. Grave stale, contradictory, or unsafe orders within a few months. A governance pattern requires four components:

• Library holdings. One named owner, typically Copilot’s adoption lead or AI center of excellence lead, is responsible for Team membership, channel structure, and content quality.
• Curation group. A small group of contributors with write access, drawn from the functions the library serves. Everyone has read access and can request additions.
• Review the beat. Quarterly review of any published requests against current model behavior, current product naming, and current organizational policies. Commands that no longer work, or refer to products that are no longer used, will be retired or rewritten.
• Version control. When a prompt is revised, note the previous version in the description column with the date of change and reason. Without this, you can’t audit why an output changes when someone challenges it.

And it’s perhaps in this area that the fast gallery falls a little short – especially around version control. But it’s a start and better than nothing

Where this fits into Copilot’s broader adoption strategy

Treating Prompt Gallery and a dedicated fast library that provides a storage and distribution layer for an organization-wide fast library is part of a broader pattern: moving Copilot adoption from individual productivity to operational discipline. This is combined with rapid frameworks (RTF, CARE, CO-STAR, and others) for consistent structure, rapid evaluation rubrics for measurable quality, and maturity models that benchmark where a function is on the journey from ad hoc push to systematic use. Libraries are artifacts that make these things visible and reusable throughout the organization.

Useful Links

AI Empowerment Program | Microsoft Copilot & AI Consulting

Why Your Copilot Program Needs a Fast Library, Not Another Pilot

Copilot Notebook: The Most Underused Workspace in M365