Microsoft is adding a Copilot on/off toggle directly into classic Outlook for Windows, a change that removes one of the last remaining reasons for organizations to push users toward the new Outlook client. The rollout, detailed in Microsoft 365 Message Center post MC1358831 and scheduled to begin in early July 2026, adds an in-app preference that had been conspicuously absent from the traditional desktop application—without altering who actually qualifies to use Copilot.

The setting arrives not as a new license grant or forced activation, but as a simple control tucked under the File menu. Its main practical effect: administrators who have held off migrating users to new Outlook solely to provide that toggle can now check that item off their list.

The Copilot Toggle Finally Lands: What’s Actually Changing

On June 4, 2026, Microsoft published MC1358831 with a clear timeline: a public preview that began in early June and wrapped up by mid-June, followed by a worldwide general availability rollout starting in early July and finishing by the end of that month. Once the update reaches a classic Outlook installation, users will find a new Copilot settings page at File > Copilot settings, with simple On and Off options.

The change is a settings rollout only. It does not create a new Copilot entitlement, expand licensing, or bypass your organization’s existing administrative controls. As Microsoft stated in the message center announcement, tenant-level restrictions and administrator-override policies remain unaffected. Think of it as adding a light switch to a room: flipping it won’t make the lamp work if the bulb is missing or the circuit breaker is off.

For users still on classic Outlook—whether because of legacy add-in dependencies, offline workflow requirements, or simple familiarity—this update closes a notable feature gap. The absence of an in-app Copilot toggle had often been cited as a reason to move to the newer client, even when other migration blockers existed. Now that reason loses its bite.

Importantly, this is not the same as the separate, ongoing issue in which some users have seen their Copilot Chat buttons disappear after updating classic Outlook to build 20026.20182 or later. That problem, discussed in Microsoft’s known issues and Q&A forums, stems from a connectivity and authentication glitch and remains under investigation. MC1358831 is a deliberate, phased addition of a settings page, not a fix for those missing buttons. Don’t confuse the two.

What This Means for You

The impact depends on how you use Outlook.

For everyday users

If you open classic Outlook and suddenly spot a new Copilot section under the File menu, don’t panic. The setting’s presence does not mean Copilot is suddenly active or snooping on your emails. It simply means your organization has received the update. Whether Copilot actually works for you still depends on two things: your Microsoft 365 license must include Copilot, and your organization’s policies must allow its use. If either is missing, toggling the switch to On won’t magically enable the assistant.

In other words, a new settings page is not an AI takeover. If you don’t have Copilot access today, this update changes nothing for you.

For IT administrators and help desks

The real relief is operational. For months, teams managing classic Outlook deployments have faced a blunt choice: either migrate users to new Outlook just to give them a Copilot off switch, or field endless tickets when Copilot began appearing with no easy way to disable it. MC1358831 hands administrators that control without a client migration.

When the update lands, you can expect the following:
- The setting appears inside classic Outlook’s File menu—no policy change required.
- It does not override existing tenant-wide Copilot settings (such as those in the Microsoft 365 admin center or cloud policy service).
- A user who is ineligible for Copilot because of licensing or org restrictions won’t gain access by flipping the switch.

Your immediate job is to update support documentation and remind help-desk staff that a missing toggle during the early weeks of July is likely a rollout timing issue, not a configuration error. A concise checklist will save hours:
1. Verify the user is running classic Outlook for Windows.
2. Confirm whether the MC1358831 rollout should have reached your tenant (Microsoft’s typical phased release may delay it by a few weeks).
3. Look for the published path—File > Copilot settings > On/Off—and don’t hunt for it elsewhere.
4. Separately verify the user’s Copilot eligibility via license assignment and admin center reports.
5. If the toggle is visible but Copilot still doesn’t function, check the account’s eligibility, not the setting.
6. Escalate only after ruling out rollout timing, license status, and existing administrative blocks.

For developers and power users

No APIs, add-in behaviors, or automation workflows are altered by this rollout. The setting is purely a user-facing preference within the classic Outlook interface. If you’ve built solutions that interact with Copilot, they remain governed by the same licensing and service controls. The only difference is that users can now manage their own on/off preference without leaving the classic client.

How We Got Here: A Long-Simmering Feature Gap

Classic Outlook’s relationship with Copilot has been awkward from the start. When Microsoft launched its AI assistant across Microsoft 365, the new Outlook for Windows got Copilot integration—including the ability to summarize threads, suggest replies, and generate meeting notes—alongside an obvious on/off toggle. Classic Outlook, still used by millions of organizations thanks to its extensive add-in support and offline capabilities, was left out.

For a while, the gap could be ignored. Then Microsoft began pushing Copilot more aggressively, and the disparity became a practical problem. IT managers who wanted to give users the flexibility to disable Copilot without blocking it entirely found themselves with no in-app lever. The only path was to migrate to new Outlook, which often wasn’t feasible because of missing features in the newer client.

Throughout 2024 and 2025, WindowsForum users and other community members voiced their frustrations. Reports of Copilot buttons appearing and disappearing without explanation, confusion over licensing, and the growing pressure to adopt new Outlook created a noisy support landscape. The July 2026 rollout is essentially Microsoft’s answer: you can keep classic Outlook and still give users that on/off switch.

It’s worth noting what this doesn’t resolve. Classic Outlook still lacks many of the Copilot experiences found in the web and new desktop clients, such as real-time coaching and advanced meeting insights. Feature parity is not on the table with MC1358831. The update is strictly about adding a settings page, not about bringing the full Copilot suite to the classic client.

Your July Action Plan: What to Do Now

Even if you’re not a migration decision-maker, there are steps to take.

If you’re a user: When you see the toggle, don’t immediately toggle it to On and expect magic. First, check with your IT team to confirm that your account has Copilot access. If they say yes, go ahead and experiment. If they say no, leave the switch Off and move on. The setting won’t break anything.

If you’re an administrator:
- Audit your classic Outlook population. How many users still rely on it, and why? The Copilot toggle removal argument is gone, but other migration drivers may still apply.
- Test the setting in a ring. Once the rollout hits your tenant, have a small group verify that the toggle appears and that it respects your licensing and policy boundaries.
- Update your support scripts. Help-desk staff should ask: “Is the setting visible? If yes, does Copilot actually work when turned on? If not, is the account licensed?”
- Communicate clearly. Avoid overpromising. The right message: “Classic Outlook now has a Copilot on/off option. It doesn’t mean everyone gets Copilot, and it doesn’t disable all Microsoft 365 AI features.”

If you’re still evaluating a client migration: Take the Copilot toggle off your comparison spreadsheet. Then refocus on the features that genuinely affect your business: add-in compatibility, offline access, automation, and form handling. MC1358831 only addresses one narrow gap; your broader decision must rest on a full inventory of user needs.

Beyond the Toggle: What’s Still Missing

Closing the settings gap is a pragmatic step, but it doesn’t quiet the larger conversation around classic Outlook’s future. Microsoft has been signaling for years that new Outlook represents the long-term direction, and the classic client remains on extended life support. No timeline has been announced for feature parity, and it’s likely that experience differences will continue to widen.

For organizations deeply invested in the classic ecosystem—particularly those running custom COM add-ins or complex VBA automation—the Copilot toggle may offer only temporary breathing room. The fundamental migration question remains, now without the convenient excuse of a missing AI switch.

Meanwhile, keep an eye on the separate blotter item where Copilot buttons momentarily vanished from classic Outlook after a recent build update. Microsoft says it’s investigating, and a fix may come in a service-side configuration change. As always, verify any sudden disappearance of Copilot controls against your rollout status and the latest known issues before opening a ticket.

In the near term, the July rollout represents a small but meaningful improvement for the many organizations still running classic Outlook. The toggle itself is a simple UI element, but its arrival signals that Microsoft is willing to throw a bone to holdouts even as it nudges everyone toward the new experience.