Who should publish organisational Copilot prompts — and can we delegate?

You’re right to want a governed prompt catalogue. Seat spray without approved starting points is how shadow prompt libraries and “clever” risky wording end up in every team chat.

Here’s what’s going on. In Microsoft 365 admin centre, Copilot → Prompts lets AI Administrators (or Search Editor / equivalent) create, edit, delete, import, export, and pin organisational prompts — curated prompts that appear for users in Microsoft Copilot Chat, Edge, and Teams as Suggested / Prompt Lab cards and as autosuggest while they type. Tenants can publish up to 1,000 prompts; changes typically take about three hours to show in Prompt Lab. You can pin up to four priority prompts, bulk-import up to 100 per CSV (5 MB), and review per-prompt analytics (active users and submissions over 7/14/28 days). Roles matter: this is an admin-centre job today for most tenants. Microsoft’s roadmap item 569425 (delegated prompt publishing) adds the ability for admins to delegate create/edit/delete of organisation prompts to users, Entra security groups, and distribution groups via Prompt Lab without giving them the Microsoft 365 admin centre — with admins retaining oversight in the current admin experience. Treat that as in development (GA timing on the roadmap; verify current status for your cloud) until it lands in your tenant.

Steady before scale puts Pane 05 GRC and Pane 07 Adoption together: prompts are organisational content, not throwaway chat tips. Schofield’s Third Law (historically attributed) still applies — the easier a prompt is for everyone to discover, the easier a poorly worded one amplifies bad practice at scale.

Options that actually work:

1. AI Admin–owned catalogue first. Publish a short Wave 0 set (pinned four + a department-tagged lab), export a CSV backup, and review analytics weekly. Best Steady default while delegation is rolling out.
2. Prepare a delegated publishing model for named content owners. When 569425 reaches your tenant, delegate to Entra groups (e.g. Copilot Champions, L&D), keep AI Admin oversight in Copilot → Prompts, and require a review date on every prompt description. Good once the feature is live.
3. Hand Global Admin to every department “so they can publish faster.” Unnecessary privilege; use AI Admin / Search Editor today, and delegated Prompt Lab later — not broader admin roles.
4. Skip organisational prompts and rely on Word docs of “good prompts.” Those go stale, aren’t autosuggested, and never show submission analytics.

12 Panes action / comms: Tell Adoption: Pinned prompts are a governed channel — treat the four pins like homepage real estate. Tell GRC: Export before bulk delete; deletion is permanent. Users: Promoted by your organisation means approved wording — still check sensitivity before you paste confidential data into the prompt.

Benefits / risks: Curated prompts shorten time-to-value and reduce freestyle risk; localisation needs separate prompts per language (no auto-translate); the 1,000 limit and three-hour lag frustrate last-minute campaigns. Delegation without an owner register recreates prompt sprawl with nicer UI. Product surfaces and GA dates move — verify Learn and Message Centre for your tenant.

I’d suggest this week: stand up ten organisational prompts (four pinned), export the CSV to your AI register, name future delegate groups, and watch analytics before you widen. You’ll have Steady Adoption without waiting for every maker to invent the same prompt badly.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer