Most Copilot rollouts I see have a strange shape. The licences are bought. The admin centre is half-configured. And nobody is using it.
Six months in, a few power users are saving an hour a week. Everyone else opens Copilot, stares at a blank box, and closes the tab.
That’s not a Copilot problem. That’s a prompting problem.
And the worst part? Microsoft has already shipped the fix. Most tenants haven’t turned it on.
What is a tenant prompt library, really?
A prompt library is a list of known-good prompts pinned inside the Copilot experience itself. Your users see them when they open Copilot — in chat, in Word, in Excel, in Outlook, wherever you’ve published them.
Two layers matter for SMBs and MSPs.
The first is the Microsoft Copilot Prompt Gallery — the public set Microsoft maintains. Useful. Generic.
The second is promoted prompts — your own prompts, pushed to your own users from the Microsoft 365 admin centre. This is the layer almost nobody uses, and it’s the one that actually changes behaviour.
Think of it as the difference between handing someone a generic cookbook and putting a Post-it on their fridge that says “this is how we make pasta”.
Step-by-Step: publishing a tenant prompt library
Portal walkthrough, no PowerShell.
Open the admin centre
Sign in to the Microsoft 365 admin centre as a Global or Copilot admin. Expand Copilot in the left nav, then Settings, then Promoted prompts.
Write the prompt your users actually need
Don’t reach for a clever one. Reach for the boring one your help desk keeps explaining. “Summarise this week’s emails from my customers and group by client.” “Draft a weekly status update for my manager based on my meetings and Teams chats.” Plain English, written the way a non-technical user would actually type it.
Pin it to the right app
You can target the prompt to Microsoft 365 Copilot chat, Word, Excel, PowerPoint, Outlook, Teams, or OneNote. Pin one prompt per app where it’s actually useful. Five great prompts beats fifty mediocre ones.
Set the audience
Use a group, not “everyone”. Roll it to a pilot. Sales gets the sales prompts. Finance gets the finance prompts. The prompt is the training material.
Publish and watch adoption move
Promoted prompts surface at the top of the Copilot prompt UI for the assigned users within a few hours. Microsoft’s Copilot Prompt Gallery documents the surfaces they show up on.
Title: Weekly client summary
App: Microsoft 365 Copilot chat
Prompt:
Summarise emails and Teams messages from
my customers this week. Group by client.
Highlight any unanswered questions.Notice what’s missing? No mention of how Copilot does the work. No file picker. No talk of Work IQ. The user just asks once and gets the outcome. That’s the brief.
Why this actually changes behaviour
Most adoption programmes hand out PDFs nobody reads. Promoted prompts put the training inside the product, at the moment of use.
“I don’t know what to ask Copilot for.”
That sentence kills more rollouts than any licensing or governance issue. A prompt library answers it.
Three things shift the day you publish one:
- New users see a starting point on day one instead of a blinking cursor.
- Power users stop reinventing the same prompt twelve different ways.
- You finally have a measurable, governable surface to iterate on.
That last one matters for MSPs. You can review the prompt library quarterly with your client, the same way you review a security baseline. Copilot doesn’t get tired. Use that.
For the deeper guidance on what makes a prompt land, Microsoft’s own write effective prompts page is worth lifting language from when you draft yours.
One closing thought
If you’re rolling out Copilot to a client and you haven’t published a single promoted prompt, you’re charging them for a tool and shipping them a blank page.
Promoted prompts aren’t there to teach people how to use Copilot. They’re there to remove the moment of not knowing what to ask completely.
CIAOPS 