Should makers clear Agent Readiness before we let them publish?

You’re right to want the fight with policy before the go-live theatre. Last-minute “why is Teams grayed out?” tickets are usually a design-time failure, not a maker skill gap.

Here’s what’s going on. Agent Readiness (Microsoft 365 Roadmap 568762, status Rolling out, GA timing September CY2026 on the roadmap — verify for your cloud) puts a real-time health check in the Copilot Studio build experience. A single Review / Agent status summary on the Overview page groups issues by severity — Blocking, Warning, and Info — and shows whether they affect draft, published, or both. Tools and channels blocked by data policies or Advanced Connector Policies appear grayed out with a clear reason, so makers don’t spend a day wiring something that was never going to publish. For agents on the standard harness, Learn documents the Agent status summary under Copilot details; the GitHub Copilot harness path has a similar always-visible Review entry point. Important honesty from Microsoft: this does not replace admin-level governance or compliance reporting — it’s maker-facing hygiene, not your audit pack. Admins can also set a custom guidance message (preview on Learn) in Power Platform admin centre → Copilot → Settings → Maker guidance: plain text up to 400 characters, optional HTTPS link and contact email, scoped by environment or environment group (group overrides environment). That message replaces the generic “Contact your admin” when makers hit blocked capabilities — useful for pointing at your request form or zone rules.

Steady before scale: Pane 05 GRC owns the policy truth; Pane 07 Adoption owns the maker experience of that truth. Schofield’s Third Law (historically attributed) still applies — the easier it is to click a blocked connector “just to try,” the easier someone else inherits the same overreach when the block isn’t there.

Options that actually work:

1. Treat Blocking readiness as a soft publish gate in your ALM checklist. No production channel until Agent status is green (or only Info). Pair with Maker guidance that links to your agent intake form. Best Steady default while 568762 finishes rolling out.
2. Zone the message. Different Maker guidance for sandbox vs production environment groups — sandbox explains “experiment here,” production explains “raise a change, don’t lobby Security in chat.”
3. Ignore readiness and keep escalating at publish time. You’ll keep paying in tickets what you refused to pay in design-time clarity.
4. Assume green readiness equals compliance sign-off. It doesn’t — Learn is explicit that Agent status isn’t admin governance reporting.

12 Panes action / comms: Tell makers: Review before you book the demo — gray means policy, not a bug. Tell PPAC admins: Set Maker guidance this week; 400 characters of plain English beats another Slack argument. GRC: Keep DLP/ACP as the source of truth; readiness only surfaces it earlier.

Benefits / risks: Fewer failed publishes and clearer policy feedback; preview docs and rolling features can still move; custom messages aren’t localised; readiness won’t catch every runtime or identity risk. Verify Learn and Message Centre for what your tenant shows today.

I’d suggest this week: enable Maker guidance on your agent production environment group, add “Agent status has no Blocking issues” to the publish checklist, and walk one maker through Review on a known blocked connector so the story sticks. You’ll get Steady publish hygiene without inventing another admin dashboard.

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