Copilot Prompt Gallery: Moving Your Team's Saved Prompts
How to collect the prompts your team uses in ChatGPT, Claude or Gemini, rewrite them for Microsoft Copilot and share them through Copilot Prompt Gallery.
Every team that has used AI for a while has a set of prompts that work. The proposal prompt sales copies from a shared doc. The prompt finance uses to check an invoice against a contract. The one HR uses to turn interview notes into a summary. When a company moves to Microsoft Copilot, those prompts are some of the most valuable things to bring along, and the easiest to lose, because they live everywhere.
Copilot Prompt Gallery is where they land. It lets people save prompts and share them with a link, by email, or with a Teams team. It needs a Microsoft Copilot license.
Step 1: Find the prompts
Prompts rarely live in one place. Look in:
- Shared documents and wikis, where teams keep "prompts that work".
- Chat and email threads, where someone shared a prompt that got passed around.
- Custom GPTs, Claude Projects and Gems. Their conversation starters are prompts, and their instructions often contain several.
- People's own notes. Ask each team lead for the five prompts their team uses most.
Ask for the prompt and one example of a good result. The example tells you whether the rewritten prompt still works.
Step 2: Sort them
Most prompt collections shrink by half once someone looks at them together. For each prompt, decide:
- Keep. It's used often and works.
- Merge. Three versions of the same meeting-summary prompt become one.
- Make it an agent. If a prompt needs a long setup, a set of reference files, or a fixed format every time, it's really a small assistant. Rebuild it as a Copilot agent instead, with the files as its knowledge. See how to rebuild a custom GPT in Agent Builder.
- Retire. Nobody has used it in months.
Step 3: Rewrite them for Copilot
Prompts written for ChatGPT, Claude or Gemini usually work in Copilot with small changes:
- Point to company content, not uploads. A prompt that started with "I'll paste our rate card" can refer to the rate card where it lives in SharePoint. Copilot can only use content the person already has permission to see, so the prompt works the same for everyone who has access.
- Remove tool-specific instructions. Lines about a specific model, plugin or feature of the old tool should describe the task instead.
- Keep personal preferences out. "Write in British English" or "keep it short" belong in each person's Copilot custom instructions, not in a shared prompt.
- Test with the original example. Run the rewritten prompt on the same input and compare it with the result you collected in step 1.
Step 4: Save and share them
Save each prompt in Prompt Gallery with a clear name that says what it does ("Proposal first draft from discovery notes", not "Sales prompt 3"). Share team prompts with the team's Teams team, so new people find them without asking around. Prompts for one-off use can go out with a link or by email.
Give the library an owner in each team. Someone has to remove prompts that stop working and add the new ones people discover.
Step 5: Show people where they are
A prompt library nobody opens doesn't change anything. Include Prompt Gallery in the Copilot training: show each team its shared prompts, run one together, and show how to save their own. That small habit is what turns "we bought Copilot" into "we use Copilot".
Part of a bigger move
Prompts are one piece of moving a team's AI work. The others are the custom assistants, the knowledge files behind them, chat history and each person's preferences. Our ChatGPT, Claude and Gemini pages show what moves where, and the AI Migration Assessment inventories all of it, prompts included, before anything changes.