If you've opened Word, Excel, or PowerPoint recently and felt like the Copilot button had wandered off, you weren't imagining things. Microsoft is rolling out a redesigned entry point for Copilot Chat that lives on the document canvas rather than tucked into the ribbon — and it brings a few changes that are more interesting than a button move usually deserves.
The headline shift is discoverability. But underneath, there's a story about contextual suggestions and accessibility that's worth paying attention to, especially if you manage rollouts or care about how AI features actually get used rather than just licensed.
Out of the ribbon, onto the page
The old pattern was simple: Copilot sat in the ribbon, alongside everything else. Easy to ignore. According to Microsoft's message centre notice (MC1189000), the new entry point — officially the Copilot Dynamic Action Button, or DAB — appears at the bottom-right of the canvas as an always-available primary entry point. You can right-click it and choose Dock, or drag it to the side of the content when you want to focus; clicking the smaller docked icon brings it back to the canvas.
The rollout began in early December 2025 and, per the latest message centre update on 11 May 2026, is expected to complete by end of May 2026 (Microsoft revised this from an earlier "late March" estimate). It covers Word, Excel, and PowerPoint on web, desktop, and mobile, and is starting with users who have a Microsoft 365 Copilot licence and pinning enabled before progressing further.
For admins, there's no required action, but the existing "Pin Microsoft 365 Copilot Chat" setting still controls whether the entry point appears. If you've set it to "Do not pin" and you want users without a Copilot licence to access Copilot Chat in-app, you'll need to flip that back — assuming your tenant is still in scope for that experience, given Microsoft's recent changes for larger tenants.
Suggestions that actually read the room
The more interesting change is what shows up around the button. Hovering on the DAB surfaces Suggested User Actions (SUAs) — curated prompts tied to the current document or selection. And when you select text or take an action on the canvas, a separate contextual entry point appears right there too.
In practice, that means the suggestions you see in a half-finished pitch deck are different from the ones you see in a budget spreadsheet, and different again when you've selected a paragraph in a long report. It's a modest version of the proactive Copilot Microsoft has been talking about for the past year — one that nudges based on what's in front of you, rather than waiting for you to type "help."
This pairs naturally with the broader agentic capabilities Microsoft announced as generally available on 22 April 2026, where Copilot can take multi-step actions directly on the canvas rather than just suggesting them. The new entry point is, in a sense, the front door to that work: a faster path from "I have a document open" to "Copilot is doing the thing."
Keyboard-first, finally
The part that's easy to overlook: the new design is built with keyboard and screen-reader users in mind, and Microsoft is unifying its shortcuts across the suite. The old combo of Alt+H, F, X to open the Copilot pane is being replaced with a simpler, consistent set:
- Windows (desktop and web):
Alt+C— sets focus on the Copilot button in the canvas; if the chat pane is already open, focus jumps to the chat box so you can start typing. - Mac (desktop and web):
Cmd+Ctrl+I— sets focus on the Copilot button. - All platforms:
F6— moves focus to the Copilot button. From there, the up arrow walks through the suggested prompts.
Microsoft says the updated shortcuts are already live in Outlook and Word on Windows and Mac, with the other apps following. The broader goal is consistency: one shortcut pattern across Microsoft 365 that supports both keyboard-first users and anyone using a screen reader.
For anyone who's tried to drive Copilot purely with a keyboard, you'll know this matters. AI features have a habit of being designed mouse-first and retrofitted later. Building keyboard parity into the entry point itself — rather than as a follow-up patch — sets a better baseline, and it makes Copilot meaningfully more usable for power users who'd rather not lift their hands off the keys, even without any accessibility need.
What this means for rollouts
If you're running Microsoft 365 at scale, three things are worth flagging to your team. First, your end users will see the Copilot icon move — expect a small wave of "where did Copilot go?" tickets, and consider a short comms note before it lands in your tenant. Second, the contextual SUAs may change what people actually try with Copilot, which can subtly shift training material and adoption metrics. Third, if accessibility compliance is on your radar — and in the EU, with the European Accessibility Act in force since 28 June 2025, it increasingly should be — the improved keyboard and screen-reader support is a meaningful addition to your story.
The quiet pattern
Step back and the move makes sense as part of a longer arc. Microsoft has been steadily pulling Copilot out of "feature you go to" mode and into "thing that's just there." Putting the entry point on the canvas, tailoring its prompts to context, and respecting the keyboard are all variations on the same theme: AI surfaces that meet you where you're working, instead of asking you to detour.
It's the kind of unglamorous interface work that decides whether a billion-dollar AI strategy gets used or ignored. And it's exactly the sort of detail that comes up over coffee at ECS, where people who actually run these rollouts across European tenants compare notes on what changes adoption — and what just changes the icon. The button moved. Whether the behaviour around it moves too is the more interesting question.