Organizational Prompts: Publish Copilot Prompts to Your Whole Org in Minutes

If you rolled out Microsoft 365 Copilot and then watched most of your people ignore it, this one's for you.

I help organizations deploy Copilot in front of thousands of users, and the pattern is almost always the same. A company buys Copilot, starts the rollout, and then watches it sit there. It's easy to blame the tool. Most of the time we handed everyone a blank box and expected them to figure out what to type.

Your people aren't prompt engineers. They're nurses, knowledge workers, and HR. They open Copilot, see a blank screen, type something like "summarize this email," don't love what comes back, and quietly walk away. Do that across thousands of users and adoption stalls.

There's an admin setting that helps with exactly this. It's called organizational prompts, and if you own Copilot for your org, don't sit on it.

What organizational prompts do

Organizational prompts let you load a library of ready-to-use prompts straight into Copilot for your whole organization. You create and publish them once, and they show up for your users across Copilot Chat, Microsoft Edge, and Teams, suggested automatically as people type. Instead of a blank screen, your users open a menu and pick from prompts you already wrote for them, sorted by department. It gives people a starting point, which is the thing most of them are missing.

One heads-up before you go looking for it. This is rolling out right now, so if you don't see Prompts under Copilot yet, that's likely why, but most are already seeing it in their tenants, so it should be there soon. You'll also need the AI Administrator or Search Editor role to manage them.

How to set it up

Head to the Microsoft 365 admin center. On the left, drop down Copilot and open Prompts. That's where your organizational prompts live.

You've got two ways to add them:

• Create them one at a time with the Create prompt button.
• Import them in bulk. Download the CSV template, fill in one row per prompt, save it as CSV UTF-8, and import the set. You can import up to 100 prompts at a time (5 MB max per file), and publish up to 1,000 in your tenant. If you already have a prompt catalog in a spreadsheet, this is the fast path.

When you create or edit a prompt, you'll set a few fields:

• Title and display prompt. The title is the label on the prompt lab card (35 characters). The display prompt is the short version shown on the pill suggestions and autosuggest (132 characters).
• Prompt. The actual text sent to Copilot when someone picks it. This is required and gives you room to write a real prompt (up to 8,000 characters).
• Supported apps. Pick where the prompt shows up. This one matters. Not everyone has a premium license, but everyone has Copilot Chat on the web, so you can make a prompt available there too.
• Department. Heads up: departments don't map to a security group. They're free-text filters for the end user. Tag prompts with IT, Finance, HR, and so on so people can sort the library by their team.
• Task type. These come from Microsoft (Analyze, Create, Edit, and so on). You can't make your own, but tagging them helps users filter.
• Language. Set the language for the prompt. There's no auto-translation, so if you need a prompt in multiple languages, create a separate one for each.

Hit publish and it's live. Give it about 3 hours to show up in the prompt lab. You can also pin your most important prompts, up to four, and those pinned ones show up as suggested prompts on the Copilot home screen.

Check the analytics

There's an Analytics tab that's worth your time. Once the data populates, you can see active users and submissions per prompt over the last 7, 14, or 28 days. That tells you which prompts people actually use, which ones to fix, and where adoption is landing. It's a straight read on what's working.

Where your users find them

Setup is half the job. Users need to know where these live. They show up in three spots:

• The Suggested button on the Copilot home screen, which opens your pinned prompts.
• The prompt lab, where users search by keyword and filter by department or task type. Picking a prompt drops it into the message box so they can tweak it before sending.
• Autosuggest right in the Copilot input box as someone starts typing.

So someone on IT can search "IT," grab a prompt that rewrites a help desk reply so it doesn't read like "did you try restarting your computer," and send something that sounds a lot nicer. Pre-made prompts, sorted by team, ready to go.

Do these two things after you turn it on

1. Tell people it exists. Send a note to your communication channel. You've got a prompt library, it's sorted by department, here's where to find it. A library nobody knows about doesn't move adoption.
2. Give people a way to submit prompts. Set up a channel where users can send you good prompts to add. When someone finds a prompt that works for Finance or IT, they should have a clear path to say "add this one." That keeps the library growing from the people actually using it.

Organizations have been asking for this because they want to hand users a foundation for getting started with Copilot. Organizational prompts are one of the cleanest ways to do it, and it takes minutes.

If you're an admin, this is a quick win with real impact. Set it up, tell your people, and give them a way to add to it.

For the full field reference and character limits, here's Microsoft's official documentation: Organizational prompts for Microsoft 365 Copilot.

Go push some buttons.