Copilot Scheduled Prompts just moved house inside Microsoft 365, and if you manage Copilot governance policies, this is the kind of change that is easy to miss until an audit or an internal question forces you to look. Starting mid-August 2026, it will no longer be governed by the Optional Connected Experiences policy. Instead, it moves under the main Microsoft 365 Connected Experiences framework. Nothing changes for the person scheduling a recurring Copilot summary. Everything changes for the admin who documented how that feature is controlled.
If your organisation has been tightening its Copilot governance since rollout, this is exactly the kind of quiet policy shuffle worth a five minute check. For a structured way to keep that kind of review from slipping through the cracks, our free Microsoft 365 Copilot rollout checklist walks through the admin controls worth revisiting on a regular basis.
What Is Changing for Copilot Scheduled Prompts
Copilot Scheduled Prompts is the feature that lets users automate recurring Copilot requests, daily summaries, weekly reports, standing reminders, without retyping the same prompt every time. Until now, whether your users could see and manage the feature was decided by the Optional Connected Experiences setting, a policy that also governs a long list of unrelated Office features like Bing-powered map charts and online picture search.
That is the part Microsoft is fixing. By late August 2026, the feature will be governed by the Microsoft 365 Connected Experiences policy framework instead. According to Microsoft, existing scheduled prompts keep running without interruption during the move, and users keep the same ability to create, edit, and manage their prompts. What changes is purely which policy toggle an admin uses to control the feature, and which compliance documentation now describes it correctly.
How Copilot Scheduled Prompts Governance Works Now
Reviewing Your Copilot Scheduled Prompts Policy Step by Step
If your organisation actively restricts features through Connected Experiences policies, here is the review Microsoft recommends before the change completes:
- Open your Microsoft 365 Connected Experiences policy settings in the admin center.
- Check whether you currently restrict Copilot Scheduled Prompts through the Optional Connected Experiences setting.
- Confirm how the Microsoft 365 Connected Experiences policy is configured for the same group of users.
- Update any internal documentation that references the old Optional Connected Experiences path for this feature.
- Notify whoever owns Copilot governance and policy management in your organisation about the change, so audit trails stay accurate.
For most organisations, no action is required. This step only matters if you deliberately used the Optional Connected Experiences setting to lock down this feature for compliance reasons.
Why Microsoft Moved Copilot Scheduled Prompts to Connected Experiences
Optional Connected Experiences was never designed as a Copilot governance tool. It is a broad, decade-old privacy policy setting built for Office features like online image search and 3D Maps in Excel, long before Copilot existed. Folding Copilot Scheduled Prompts into that setting meant admins had to reason about an AI automation feature using a policy meant for stock photo lookups.
Moving Copilot Scheduled Prompts to the Microsoft 365 Connected Experiences framework aligns the feature with how Microsoft governs the rest of Copilot. It is a cleanup move, not a new capability, but cleanup moves like this one matter more than they look. Governance documentation that is technically accurate but conceptually confusing is documentation nobody trusts, and undocumented drift is exactly what compliance reviews are supposed to catch.
Rollout Timeline
| Phase | Start | End |
|---|---|---|
| General Availability (Worldwide) | Mid-August 2026 | Late August 2026 |
According to Microsoft, this should be rolling out from mid-August 2026 and complete by late August 2026. There is no separate Preview phase listed for this change, it moves straight through to General Availability.
Who Is Affected by This Copilot Scheduled Prompts Change
Two groups need to pay attention here. Microsoft 365 Copilot customers with access to Scheduled Prompts are affected in the sense that the feature keeps working exactly as before, so no end-user communication is strictly necessary. Microsoft 365 administrators who use Connected Experiences policies to govern feature availability are the group that actually needs to act, and only if they currently lean on the Optional Connected Experiences setting specifically to control Copilot Scheduled Prompts.
If your organisation has never touched the Optional Connected Experiences policy, or manages Copilot access some other way, this change passes by without any practical impact. Copilot Scheduled Prompts keeps running, keeps being editable, and keeps showing up exactly where users expect it.
Admin Tips for Copilot Scheduled Prompts
Treat this the way you would treat any policy framework migration, even a small one. Start by pulling up your current Connected Experiences configuration and confirming which setting currently controls this feature for your tenant. Screenshot it, or export the setting, so you have a before-and-after record for your own audit trail.
Update internal documentation and administrative guidance before the rollout completes in late August 2026, not after. If your organisation runs periodic compliance reviews, flag this change to whoever owns that process now, so it does not surface as a surprise finding three months from now. Our Copilot Cost Management article covers a similar pattern, where a small admin-facing change in how Copilot is governed had a bigger downstream effect on reporting accuracy than the headline suggested.
It is also worth using this as a trigger to check your broader Connected Experiences configuration, not just this one policy. Policy frameworks that govern AI features tend to get revisited by Microsoft more often than legacy Office privacy settings, and each revision is a chance for documentation to quietly go stale. Our article on restricted content discovery for Copilot and Microsoft 365 search is another example of governance surfaces shifting underneath admins with limited fanfare.
License Requirements for Copilot Scheduled Prompts
Copilot Scheduled Prompts requires an active Microsoft 365 Copilot license, the same license already required to use the feature today. This governance change does not add a new license requirement, does not remove one, and does not change which SKU unlocks the feature.
For the exact requirements around Copilot licensing more broadly, see License options for Microsoft 365 Copilot on Microsoft Learn. If the feature stops appearing for a user after this rollout, the license is still the first thing to check, this change does not alter that troubleshooting order.
The Paul-Take
I like this one for a reason that has nothing to do with what it actually does. Copilot Scheduled Prompts does not change for a single end user. Nobody in your organisation will notice a thing. But it is at least the third or fourth time this year Microsoft has quietly moved a Copilot feature between governance frameworks, and each time the pattern is the same: no fanfare, a short Message Center post, and an assumption that admins are watching closely enough to catch it.
Most are not. Most admins set a Connected Experiences policy once, document it, and move on to the next fire. That is completely reasonable given everything else on an M365 admin’s plate. But it means Scheduled Prompts, and features like it, drift quietly out of sync with the documentation that is supposed to describe them. Six months from now, an auditor asks how Scheduled Prompts is governed, and the answer on file is wrong.
My advice is not complicated. Build a short, recurring habit, fifteen minutes a month, where you specifically check whether any Copilot governance policy has moved. Not features. Not licensing. Policy plumbing. That is the layer Microsoft keeps reorganising, and it is the layer that never shows up in a release notes headline.
According to Microsoft, this should be rolling out from mid-August 2026 and complete by late August 2026.
MVP Reference List
| Item | Detail |
|---|---|
| MC Number | MC1447683 |
| Roadmap ID | Not applicable, this is a governance policy change rather than a tracked Roadmap feature |
| Microsoft Learn: Manage scheduled prompts | learn.microsoft.com/microsoft-365/copilot/scheduled-prompts |
| Microsoft Learn: Connected experiences policy settings | learn.microsoft.com/microsoft-365-apps/privacy/manage-privacy-controls |
| Microsoft Learn: Optional connected experiences admin controls | learn.microsoft.com/microsoft-365-apps/privacy/optional-connected-experiences |