Copilot Workspaces agentic chat: what MC1550540 means for Researcher, Analyst and Designer

In short

Copilot Workspaces agentic chat is coming. Microsoft announced in Message Center post MC1550540 (published 12 November 2026) that Copilot Workspaces, previously called Copilot Notebooks, will no longer let users pick Researcher, Analyst or Designer as separate agents. Instead, Workspaces gets an agentic chat. The user describes the task, and Copilot applies the right skills based on the request.

The separate agents do not disappear. They stay available in the M365 Copilot app. Only the experience inside Workspaces changes.

When does this happen?

  • Frontier preview: rollout is planned to start in December 2026. Microsoft has not given a completion date yet.
  • General availability: dates are still being finalized.
  • Platform: web.
  • Roadmap ID: 516041.

So for most organizations this is not something for next week. But if you run a Frontier pilot group, they will see it soon.

What Copilot Workspaces agentic chat changes for users

Today, a user in Copilot Notebooks or Workspaces has to decide which agent to use. Researcher for deep, multi source research. Analyst for working with data. Designer for visuals.

With Copilot Workspaces agentic chat, that choice is gone. The user just writes what they need, for example “Compare the three supplier proposals in this workspace and make a short summary table”, and Copilot decides which capabilities to use.

Researcher, Analyst and Designer as separate options in Workspaces disappear. Their capabilities stay available in Workspaces through chat.

What admins need to do

According to MC1550540, no admin action is required. The change applies automatically when it reaches your tenant.

That does not mean you can ignore Copilot Workspaces agentic chat. I would look at three things:

  1. Training material. Search your quick reference cards, intranet pages and Copilot training decks for instructions like “select Researcher” or “choose the Analyst agent” in Notebooks or Workspaces. Those steps will be wrong.
  2. Communication to pilot users. Tell your Frontier users before it lands. A short message in your Copilot champions channel saves your helpdesk a lot of “where did Researcher go?” tickets.
  3. Your existing agent controls. Researcher and Analyst have their own settings in the Microsoft 365 admin center. Admins can block them, and Researcher with Computer Use has its own access and website settings. Check what you configured today, and test in your Frontier group how those settings behave inside Copilot Workspaces agentic chat. Microsoft Learn explains the current controls in Manage agents in the Microsoft 365 admin center and Researcher with Computer Use admin configuration.

My opinion: good for users, but show what happens

I think Copilot Workspaces agentic chat is the right direction. In almost every Copilot session I give, people ask me the same question: “Which agent should I use for this?” Most users don’t care whether it is Researcher or Analyst. They care about the result. Letting Copilot route the request removes one decision that never should have been the user’s problem.

There is a catch though. When Copilot picks the skill for you, it also becomes less visible what it is doing. Researcher can run for minutes, search the web and pull from many sources. Users should be able to see that this happened, so they know how to judge the answer. I hope Microsoft makes it clear in the chat which skill was used.

This also fits a bigger trend. With Copilot Cowork Microsoft already moved towards “describe the outcome, let Copilot do the steps”. Workspaces now follows the same idea. For admins this means governance shifts from “which agent may a user open” to “what may Copilot do on the user’s behalf”. If you want to see how that works for apps, read my article on Copilot Cowork connectors in the admin center.

What this means for your adoption approach

If your Copilot adoption program still teaches people to pick tools, now is a good moment to change that. Teach prompts that describe the outcome, the context and the format you want. That skill works in Workspaces, in Copilot Chat and in Cowork. It also works when Microsoft renames or merges the next feature, which, let’s be honest, will happen again.

For more on making Copilot easy to reach for end users, see Copilot in Teams: new entry point for easier access.

Checklist

  • Note MC1550540 in your change calendar for December 2026 (Frontier) and watch for the GA date.
  • Update training material that tells users to pick Researcher, Analyst or Designer in Notebooks or Workspaces.
  • Inform your Frontier pilot users and Copilot champions.
  • Review your Researcher and Analyst settings in the Microsoft 365 admin center.
  • Test in your Frontier group whether those settings apply inside Copilot Workspaces agentic chat.
  • Shift your adoption training from “pick the tool” to “describe the outcome”.

Need help?

Want to know what this and other Message Center changes mean for your organization? KbWorks helps Dutch organizations prepare their Microsoft 365 and M365 Copilot environment, from governance to adoption. Get in touch.

Source: Microsoft 365 Message Center MC1550540, published 12 November 2026.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

Get The Paul Take

My no-fluff read on Microsoft 365, Teams, SharePoint and Copilot. Real lessons from real rollouts, and what I would actually do. Once every two weeks.

No spam. Unsubscribe anytime.