On July 2, 2026, Microsoft quietly retired the Release Planner as the go-to source for Copilot Studio updates, shifting all future feature announcements for the platform—and its sibling agents for Sales, Finance, and Service—to the Microsoft 365 Roadmap. The move ends years of fragmented planning but demands immediate changes in how organizations track and evaluate upcoming agent capabilities.
What Actually Changed
For years, Copilot Studio's release plans lived on a dedicated Power Platform Release Planner site, separate from the broader Microsoft 365 Roadmap. That changed in early July when, as announced in a Microsoft Tech Community post, Microsoft began publishing all forward-looking Copilot Studio features on the standard Microsoft 365 Roadmap—the same place where IT admins track updates for Teams, SharePoint, and other core services. The Release Planner will no longer receive new entries for Copilot Studio, Sales Agent, Finance Agent, or Service Agent.
The immediate impact: the roadmap now includes specific, time-bound previews and general availability targets. A notable entry introduces SharePoint lists as a supported knowledge source for Copilot Studio agents, with public preview listed for July 2026 and general availability set for September 2026. Other upcoming features include a "production-ready preview" of the new agent creation experience—Microsoft's term for a feature stable enough for testing in production-like environments but not yet fully released—and a workflow overhaul that remains in standard public preview. These labels signal readiness levels, but they do not replace an organization's own validation processes.
What It Means for You: Different Roles, Different Responses
The roadmap consolidation affects stakeholders differently. Here's a breakdown by role:
For IT admins and governance teams: The Microsoft 365 Roadmap becomes a critical early-warning system. New Copilot Studio features might alter how agents access organizational data, invoke actions, or share with users. A service update that seems minor—like a new connector or an expanded knowledge source—could have compliance or security implications if adopted without review. Admins should treat each relevant roadmap entry as a trigger for an internal impact assessment, not a green light for automatic enablement.
For makers and developers: Earlier visibility into upcoming capabilities is a boon. Knowing that SharePoint lists will soon be a knowledge source allows teams to start planning agent designs and data cleanup well before the feature lands. But the roadmap's timing is aspirational; delays happen. Build flexibility into project timelines, and never base a critical business process on a feature marked as "preview" without rigorous testing.
For business owners: The roadmap aligns business initiatives with technology delivery, but temptation to rush adoption must be tempered. A feature might be interesting on paper but unsuitable for your use case, data sensitivity, or user base. Treat roadmap items as conversation starters for your IT and compliance partners, not as purchase orders.
Understanding Microsoft's Preview Labels
Microsoft uses a variety of labels that can confuse even experienced planners. Here's a quick cheat sheet:
| Label | What it means | Should you use it in production? |
|---|---|---|
| Public preview | Feature is available for testing but may change or break. Not covered by support SLAs. | Only in isolated test environments. |
| Production-ready preview | Microsoft considers the feature stable enough for limited production use, but it's still not GA. Requires careful internal validation. | Possibly, after rigorous testing and with a rollback plan. |
| General availability (GA) | Fully released, supported, and ready for production. | Yes, after your standard change management process. |
Always treat preview features according to your own organization's risk policies, regardless of Microsoft's labels.
How We Got Here: From Release Planner to Unified Roadmap
The migration didn't happen in a vacuum. Since 2023, Microsoft has been gradually unifying its various release planning surfaces into the central Microsoft 365 Roadmap. Power Platform and Dynamics 365 had long maintained their own Release Planner, but as Copilot Studio gained enterprise traction and blurred the lines between "platform" and "productivity suite," a split roadmap became untenable. Organizations found themselves cross-referencing two sites to piece together a complete picture of what was coming.
The shift also reflects Copilot Studio's evolution from a bot-builder into a strategic component of the Microsoft 365 Copilot ecosystem. With agents that can ground in Microsoft 365 data and orchestrate across productivity apps, its roadmap belongs alongside the services it integrates with. The July 2 date marks the culmination of that alignment.
What to Do Now: A Practical 5-Step Checklist
The immediate task isn't just bookmarking a new URL. It's about folding the Microsoft 365 Roadmap into your existing change governance without drowning in noise. Here's a simple, repeatable workflow:
-
Bookmark and filter: Go to the Microsoft 365 Roadmap, filter by product "Microsoft Copilot Studio" (and its sibling agents, if relevant), and save the filtered view. Consider using the RSS feed or email alerts if available.
-
Inventory your agents: List all agents currently in production, pilot, or active development. Note their knowledge sources, actions, sharing scope, and business criticality. This inventory will be your map for impact analysis.
-
Assign a reviewer: Designate a person or small team—often a combination of a power platform admin and a business analyst—to scan new roadmap entries on a defined cadence (weekly is usually sufficient). They need not be deeply technical; they just need to flag items that touch your inventory.
-
Quick-triage each entry: When a new feature appears, ask three questions: Does it introduce a new knowledge source? Does it enable new actions or API connectors? Does it change sharing or security boundaries? If the answer to any is yes, route it to a formal review that includes your security, compliance, and business owner representatives. Otherwise, log it as "monitor."
-
Archive the old: Remove links to the Release Planner from your internal wikis and onboarding documents. If you have past Release Planner snapshots that informed active projects, save them with a date stamp and a note that they're now superseded by the Microsoft 365 Roadmap.
This lightweight process converts a passive information stream into an accountable governance practice without bogging down your teams.
Outlook: Expect More Frequent and Impactful Updates
The roadmap consolidation signals that Copilot Studio is entering a phase of rapid, enterprise-focused iteration. As the platform deeply integrates with Microsoft 365 services, the volume and significance of roadmap entries will likely increase. Watch for more nuanced governance controls—Microsoft is already teasing granular data access policies in the admin center—and for features that demand cross-team collaboration (like new AI models or compliance-related audit logs).
Start building your review muscle now, while the stakes are still moderate. When the roadmap signals that autonomous agents can soon initiate cross-application workflows, having a practiced change-management routine will be the difference between proactive confidence and reactive scrambling.