Microsoft is adding a dedicated Copilot button above the ribbon in Classic Outlook, bringing the legacy email client into visual alignment with Word, Excel, and PowerPoint. The rollout begins in late August 2026 and will be on by default for users holding Microsoft 365 Copilot licenses.
The company announced the change through its administration portal, calling the redesigned entry point "more visually appealing and consistent." IT admins should expect some user confusion. Anyone who has not seen the button in the rest of the Office suite will want to know why there is suddenly a new element sitting above their familiar toolbar.
What the new entry point does
Classic Outlook Gets Copilot AI | New Meeting Preparation Feature 2026
The Copilot button surfaces AI-powered actions based on context. In Outlook, that means summarizing long email threads or drafting replies. The existing Copilot side pane stays put. The button is just a faster way to open it.
Microsoft frames the move as part of a broader strategy. Its roadmap entry says the redesign "anchors Copilot as one connected system across Microsoft 365, surfacing relevant actions that help you stay in flow." Translation: every app in the suite now opens Copilot from the same spot.
No floating button this time
Unlike the Word, Excel, and PowerPoint rollout earlier this year, the Classic Outlook button will not float over content. That distinction matters. Microsoft had to backpedal on the floating button in those apps after users complained it obscured their work. The company eventually allowed users to banish it to the ribbon area.
Classic Outlook users get the permanent above-ribbon placement from day one. Whether that counts as Microsoft learning from its earlier misstep or simply respecting the density of an inbox view is open to interpretation.
Microsoft's decision to ship Copilot on by default echoes a decades-old playbook around defaults and user behavior.
What admins need to prepare for
The update arrives late August and is enabled by default. Microsoft has not announced a toggle to disable the button enterprise-wide before it lands. That leaves IT teams in the familiar position of writing internal comms before the rollout rather than waiting for support tickets to stack up.
Organizations still running Classic Outlook have until at least 2029 for support, and the mandatory opt-out phase for migrating to new Outlook has been pushed to 2027. In practice, this means Classic Outlook will keep receiving feature updates, not just security patches.
Logicity's Take
Microsoft is betting that visibility drives adoption. The more places users see Copilot, the more likely they are to click it, and the easier it is for IT to justify the M365 Copilot license cost ($30/user/month). For CIOs, the real question is whether the productivity gains materialize before users tune out another interface element. If your org has not run a Copilot pilot yet, this rollout is a natural trigger.
The pattern across Office
Classic Outlook was the last major Office app without a top-level Copilot entry point. Word, Excel, and PowerPoint have had the above-ribbon button since earlier in 2026. Microsoft clearly wants every app to look and behave the same way when it comes to AI features.
The consistency argument cuts both ways. Uniform placement helps users who move between apps. It also means there is no escaping Copilot prompts unless admins disable the feature entirely for unlicensed users.
For enterprises still weighing the Classic-to-new-Outlook migration, the Copilot button rollout is a reminder that Microsoft is still investing in Classic Outlook's feature set. The migration deadline is 2027 for opt-out, but organizations can stay on Classic Outlook with full support until at least 2029.
Need Help Implementing This?
Logicity's consulting partners can help you plan your Microsoft 365 Copilot rollout, manage change communications, and measure adoption. Reach out through our advisory network.
Source: www.theregister.com
Manaal Khan
Tech & Innovation Writer
Produced with AI assistance and reviewed by the Logicity editorial team. Learn more in our Editorial Policy.
