On July 2, 2026, Microsoft quietly shifted how businesses track upcoming features for its expanding Copilot agent family. Starting immediately, all feature updates for Microsoft Copilot Studio, Sales Agent, Finance Agent, and Service Agent will appear exclusively on the public Microsoft 365 Roadmap. The dedicated Release Planner—a tool many IT teams relied on to preview and brace for changes—stopped receiving new entries for these products on the same day.

The move marks a significant pivot in how Microsoft communicates product evolution, trading a gated, admin-focused planning tool for a broadly accessible, real-time list of features in development, rolling out, and already launched. It’s the latest signal that Copilot agents are no longer fringe experiments but core, trackable ingredients of the Microsoft 365 suite.

What Actually Changed

Until July 1, 2026, administrators could open the Release Planner inside the Microsoft 365 admin center and see a curated, timeline-driven view of upcoming features for Copilot agents, complete with rollout waves, tenant-specific target dates, and change management notes. The Release Planner was part of Microsoft’s set of structured deployment tools, designed to help large organizations stagger updates, train users, and avoid disruptive surprises.

Now, that curated experience is gone for Copilot Studio, Sales Agent, Finance Agent, and Service Agent. Instead, those feature records have been ported to the Microsoft 365 Roadmap (roadmap.microsoft.com), the public-facing website that aggregates all announced features across the 365 ecosystem. Each feature gets an ID, a brief description, a status tag (In Development, Rolling Out, Launched), and broad platform availability. What the Roadmap doesn’t offer is the tenant-level rollout precision that Release Planner did—no per-tenant dates, no indication of whether a feature is being rolled out to your specific organization just yet.

Microsoft has not removed the Release Planner entirely. Other Microsoft 365 services continue to publish their features there. But for these four Copilot surfaces, the Roadmap is now the single source of truth.

What It Means for You

For IT Administrators and Change Managers

The elimination of Release Planner entries is both a transparency win and a planning loss. On the upside, the Roadmap is public, searchable, and updated more frequently than the old planner. You can embed Roadmap widgets into dashboards, build Power Automate workflows off RSS feeds, and share feature previews with stakeholders who don’t have admin center access. The Roadmap also shows features much earlier in the development cycle—sometimes months before they hit a ring.

The downside is the loss of granular roll-out information. Without Release Planner, admins must now rely on Message Center posts, which only appear when a feature is starting to roll out to your tenant, or wait for the feature to actually appear. That compressed notice period could strain training and communication plans, especially for features that change user workflows inside Copilot Studio or automated agents.

For regulated industries that demand documented change control, this shift means rebuilding processes around Roadmap restlessness: you’ll need to monitor Roadmap IDs, correlate them with Message Center notifications, and perhaps stand up your own change tracking using the Roadmap’s API.

For Copilot Developers and Power Users

If you’re building custom copilots in Copilot Studio, the Roadmap now serves as your public backlog of platform improvements. Want to know when a new adaptive card feature or connector arrives? Follow the relevant Roadmap item. The change also makes it easier to align internal development sprints with Microsoft’s publishing cadence, since the Roadmap typically outlines features weeks or months ahead of general availability.

For business users of Sales, Finance, or Service Agents, the shift is mostly invisible. They never saw the Release Planner. But the Roadmap’s public nature means that enterprise customers and partners can now hold Microsoft accountable to delivery timelines more explicitly than before.

For Business Decision Makers

If you’re evaluating Copilot agents, the Roadmap offers a straightforward marketecture view of what’s coming. It’s now easier to compare Microsoft’s trajectory with third-party AI agent platforms, because you can literally see the feature pipeline. However, remember that the Roadmap’s dates are aspirational; features listed as “In Development” can slip, and some never materialize.

How We Got Here

The Microsoft 365 Roadmap launched in 2014 as a way to share what’s next across the suite. Over the years, it’s grown from a spreadsheet-like list into a filterable database with statuses, tags, and cloud instance filters. By 2024, Microsoft had already moved many features from the old “targeted release” notifications into the Roadmap. The Release Planner, introduced around 2020, was meant to complement Message Center by giving a longer planning horizon for bigger changes.

Copilot agents, however, have been in an awkward spot. They’re part of Microsoft 365, but they straddle Power Platform, Dynamics 365, and standalone experiences. Their feature updates often skipped the Release Planner entirely, or appeared inconsistently. By unifying everything on the Roadmap, Microsoft is treating these agents as first-class M365 citizens, worthy of the same transparency as Teams, SharePoint, and Exchange.

The timing aligns with an upcoming wave of agent capabilities Microsoft has teased for late 2026—autonomous cross-app agents, enhanced memory, and deeper enterprise controls. Placing these on the Roadmap allows Microsoft to publicly build anticipation and gather feedback before features lock.

What to Do Now

  1. Start watching the Roadmap. Bookmark https://roadmap.microsoft.com and create a custom view filtering for “Microsoft Copilot Studio,” “Sales Agent,” “Finance Agent,” and “Service Agent” under the product list. Subscribe to RSS feeds for those views so you receive updates as soon as statuses change.
  2. Revisit change management processes. If your organization’s IT change advisory board relied on Release Planner lead times, update your standard operating procedure. You now have less advanced notice for Copilot agent changes, so factor in a shorter review window and plan training sessions more flexibly.
  3. Leverage the Roadmap API. For larger shops, use the Microsoft 365 Roadmap API to pull feature data into your own governance tools. This can partially restore the timeline oversight you lost by automating the correlation between Roadmap IDs and Message Center alerts.
  4. Check Message Center daily. The reduction in Release Planner coverage means that the first concrete sign of a Copilot agent update hitting your tenant will be a Message Center post. Configure email alerts and designate someone to triage them—especially for features that could change how Sales or Service Agents interact with customers.
  5. Provide feedback to Microsoft. If the loss of tenant-specific timelines hurts your operations, use the “Feedback” button inside the admin center or the Roadmap itself to request a more granular planning view for Copilot agents. Microsoft has historically adjusted roadmap features based on enterprise feedback.

Outlook

Don’t be surprised if more Microsoft 365 services follow this pattern. The Roadmap’s ubiquity and API-first design make it an easy target for centralizing all feature communication. For now, Release Planner remains relevant for core workloads like Exchange and SharePoint, but its role is shrinking. Watch for the Copilot Suite—which now encompasses Studio, Sales, Finance, Service, and possibly upcoming generic enterprise agents—to become the testing ground for a full phase-out of Release Planner in favor of a single, dynamic feed.

For now, the message is clear: if you manage Copilot agents, make the Microsoft 365 Roadmap your new morning coffee read.