Copilot leaves the Power Automate designer on November 30. Sort every flow into keep, move or retire before then
Somebody on your team built a flow by typing what they wanted into the Copilot pane. On November 30 that pane goes away. The flow keeps running, and so does the question of who understands it.

Microsoft retires Copilot in the Power Automate designer for cloud flows and agent flows on November 30, 2026. Existing flows are not deleted or changed, and makers can still build and edit them by hand, from templates and with the flow checker and run history. Natural-language building moves to the Power Automate plugin in an approved AI assistant. Before then, list every flow, find the ones built by chat, and decide who owns each.
What Microsoft is retiring
On November 5, Microsoft told admins in a Message Center post that it's retiring Copilot in the designer for cloud flows and agent flows on November 30, 2026. Its documentation describes the feature plainly. It's the Copilot pane in the flow designer, where makers could build and edit flows by chatting, ask questions about a flow, get help writing expressions and troubleshoot errors.
After November 30, makers can no longer open or use it. Nothing else is touched. The documentation is explicit that the retirement doesn't delete, move or change existing flows, including the ones that were created or edited with Copilot. Makers can still create, edit, test and run flows in the designer, start from templates, write expressions in the editor, and use the flow checker and run history.
If your people want to keep building in plain language, Microsoft points them to the Power Automate plugin inside a supported AI assistant that your organization approves, GitHub Copilot being its example. Its Message Center post also mentions connecting to Copilot Studio over MCP.
Why this is bigger than a missing button
It's tempting to read this as a small tooling change. Nothing breaks. But think about what a Copilot-built flow is. Somebody described a job in a sentence, an assistant wired up the steps, and the flow went live. The person may have read every step. They may have only checked that it ran once.
When the tool that wrote and explained the flow disappears, what's left is the flow, and whoever's name is on it. If they can't say what each step does, and why it's there, then nobody owns it in any useful sense. Scripts and spreadsheets have always worked this way: the automation outlives the person's memory of it.
The assistant leaves on November 30. The flows it helped build stay. So the useful work before November 30 isn't about the Copilot pane at all. It's an inventory. A gentle one, on a Sunday afternoon.
Decision guide
What changes on November 30, and what doesn't
| Consideration | Goes away | Stays |
|---|---|---|
| Describing a flow in words | In the designer's Copilot pane | In the plugin of an approved AI assistant |
| Existing flows | Not affected: not deleted, moved or changed | Keep running as they do today |
| Editing | Chat-based edits in the designer | Editing in the designer, templates and the expression editor |
| Troubleshooting | Asking Copilot about an error | Flow checker and run history |
The assistant leaves on November 30. The flows it helped build stay.
Keep, move or retire
Start by listing every flow. Name, owner, which systems it touches, when it last ran. Your admin tools may show much of that, so start there. Then ask the makers which flows were built or changed by chatting, because Microsoft's notice doesn't say how to tell, and the answer is probably in someone's memory.
Then read each one aloud with its owner. Can they say what every step does? What happens if a connection expires, or an app renames a field? What does it do with an unexpected value? A flow that nobody can explain is a flow to treat carefully.
Sort the flows three ways.
Keep. The owner can explain it, it runs reliably and it does one clear job. Leave it alone. Write the owner's name and a two-line description where the team can find them.
Move. It does an important job, but it's tangled, or nobody quite understands it, or it's grown into several jobs. Plan to rebuild it more simply, by hand, or with an approved assistant's plugin, with a person who'll own the result.
Retire. It was a trial, the job disappeared, or it runs and nobody reads what it produces. Turn it off and watch for a week before deleting. If somebody notices, you've found a real dependency. If not, you've removed a risk.
A few questions help with the reading. What data does the flow touch: customer records, invoices, anything with personal details? Who gets an email from it, and would they notice if it stopped? Does it use a personal account's connection that would break if the person left? Flows tied to one person's sign-in are a quiet risk on their own, and a review like this is the natural time to find them.
Don't try to be perfect. The aim is a short list of the flows that matter, each with an owner who can explain it, and a plain decision on the rest. Two hours with a spreadsheet will get you most of the way. The rest can be a date on a calendar.
One more habit is worth building: when you retire a flow, record why and when. A line in a shared note, such as "turned off November 20, nobody read the report, no one has asked since," saves the next person from wondering whether the missing flow is a mistake. It also gives you something to check if a customer or a colleague later says that something stopped arriving.
How the work moves
A Sunday-afternoon sort
- List every flow
Name, owner, what it touches, when it last ran.
- Mark the chat-built ones
Ask the makers; the notice doesn't say how to tell.
- Read each one aloud
Can the owner say what every step does and why?
- Sort
Keep as is, move to a better home, or retire.
- Write the owner down
One name per flow, plus where the notes live.
Don't tie the process to one assistant
The same lesson applies to whichever tool replaces Copilot in the designer. The Digital Phoenix write-up of the notice says it neatly: don't tie a process to one assistant. If your team builds flows by chatting with one tool, decide how the result gets documented so another tool, or a person, can pick it up.
A practical habit helps. When a flow is built or changed in conversation, save the plain-language request, what the flow does, and what to check when it fails, in a note beside the flow. Five minutes. It costs almost nothing on the day the flow is born, and it's hard to reconstruct later.
The tool also needs an approval step for new assistants. Microsoft's guidance talks about a supported assistant that your organization approves. That's a policy for your IT person or manager to write down, with a name next to it.
If someone on your team enjoys building flows by chatting, don't take that away from them. The chat was never the risk. The risk was a flow that works and nobody understands. A maker who writes the request down, reads the result and tells one other person what it does is doing the job properly, with or without Microsoft's assistant.
What to do this week
Share the notice with the people who build flows. Update any internal guide or training that recommends the Copilot pane. Run the sort on the ten flows that matter most to the business, not all two hundred. Put a date on the rest.
If your automations have grown across Power Automate, scripts and spreadsheets, and nobody has a complete picture, we can help map what runs, who owns it and what happens when it breaks. That's the start of our business automation work. Talk to us.
Related work: Spin:Market
We build alongside the people doing the work.
Bring us the problem you’re thinking about.