The cancellation came in an update to Microsoft 365 Message Center advisory MC1477999. Microsoft did not post a new notice. The update is dated October 8, 2026, and reads: "After additional consideration we have decided not to proceed with this change. You can safely disregard this message. We apologize for any inconvenience this may have caused." The rollout schedule entry now reads "Copilot chat list entry point removal (Worldwide, GCC): Cancelled".
What Microsoft had planned
The original advisory, MC1477999, was published Sep 23, 2026. It covered Microsoft Teams and Microsoft 365 Copilot Chat. It started from a simple point: users can access Copilot either from the Teams chat list or from the Copilot app in the Teams app bar. Microsoft wanted to close the smaller of those two doors. It argued that the Copilot app provides access to the full set of Copilot capabilities, while the chat list entry point provides a more limited experience.
The superseded plan included these details:
- Timeline: Removal in Worldwide and GCC tenants was to begin mid-October 2026 and expected to complete by late-October 2026.
- Transition aid: Prior to the mid-October removal, users who access Copilot from the chat list will see a coachmark directing them to the Copilot app.
- Scope: Desktop and web only. The advisory said mobile users are not affected.
- No opt-out: Neowin reported at the time that this change is being enforced from the server-side by Microsoft, and there is no admin or user control to modify behavior.
- No data loss: Microsoft said existing Copilot conversations, notifications, supported deep links, and session continuity will continue to work. No user conversations, prompts, chat history, or Copilot data will be removed.
This was always a navigation change, not a plan to retire Copilot. The proposal would have removed one shortcut and kept the full Copilot app in the app bar. It was still the kind of interface change that generates support tickets. The advisory carried Major change, User impact, Admin impact and Retirement tags for that reason.
Section summary: Microsoft planned to remove the chat-list Copilot shortcut on Teams desktop and web in mid-to-late October 2026 and send users to the app-bar Copilot app. That plan is now cancelled.
Why did Microsoft change its mind?
Microsoft hasn't said. Neowin noted that Microsoft hasn't gone into details about what factors in its "additional consideration" led it to backpedal on its original announcement. The same outlet pointed out the contrast with the first advisory, in which Microsoft painstakingly described how it was streamlining the Copilot interaction experience and would guide people to the sole method of invoking Copilot.
It's tempting to credit user feedback, telemetry or internal politics over how prominent Copilot should be. Nothing published supports any of those explanations, so treat them as guesses. One reading of the evidence does hold up. Microsoft's original case rested on interface consistency and less clutter. Some users clearly use the chat-list shortcut, though, and removing a familiar entry point always costs something. Microsoft has decided, for now, that the cost isn't worth paying.
Neowin also added an editorial jab. Its writer said they were surprised by Microsoft's move a few days ago, especially considering how the tech giant has been rather intent on shoving AI down our throats these past couple of years. In that sense the reversal fits Microsoft's broader pattern of keeping Copilot in as many places as possible.
Section summary: Microsoft has given no reason for the reversal. Any explanation beyond "additional consideration" is speculation.
What this means for Teams admins
The practical result is simple: don't prepare for this change. Modern Workspace Pro, which tracks Message Center posts, summarized it this way: impact is limited to awareness and possible communication that the prior update is cancelled, with no configuration or user disruption expected.
Some IT teams moved quickly after the September 23 notice. The original advisory recommended that admins update training materials, alert help desks and review app pinning. If you did any of that, here is a sensible cleanup list:
- Pull back user communications. If you told users Copilot would leave the chat list in October, send a short correction so they don't go looking for a change that isn't coming.
- Restore training and support content. If you removed the chat-list route from screenshots, adoption guides or knowledge base articles, put it back. Both entry points are still live on desktop and web.
- Update help desk scripts. Agents should know that both routes to Copilot in Teams remain available.
- Leave app pinning alone if it's useful. The original advisory suggested reviewing Teams app setup policies and pinning the Copilot app. Pinning it is still a reasonable choice if you want users to find the full Copilot experience, but nothing requires it now.
- Keep the record. Save the updated MC1477999 text for your change log. If a similar change returns later, you'll want the history.
That last step matters because Message Center shows only the current version of a post. The community-run Message Center archive tracks revisions. It records two versions of MC1477999: the original from September 23 and an update logged early on October 9 UTC. The update changed the body, tags, category, major-change flag and end date. Admins who rely on Message Center alone could miss how much a post has changed since they last read it.
Section summary: No admin action is required. Undo any preparation you did for the removal and keep the cancellation notice on file.
Is the change gone for good?
Nobody outside Microsoft knows. The update cancels this rollout under this advisory. It does not promise to keep both Copilot entry points forever, set a new date, or describe a replacement design.
Microsoft's original reasoning hasn't disappeared either. The company still describes the chat-list entry as the more limited of the two experiences. A more cautious version of the consolidation could come back later, perhaps with an admin toggle or a longer transition. That is analysis, not reporting. Watch the Message Center for any new advisory that mentions Copilot entry points in Teams.
The bottom line
Microsoft reversed course on MC1477999 before the rollout began. The Copilot shortcut stays in the Teams chat list on desktop and web, and the full Copilot app stays in the app bar. Nothing changes on mobile, and user data was never at risk. Microsoft hasn't explained the decision. Admins who prepared for the removal should undo those changes and wait for any future notice before acting again.