The fix also has a history. This is the second time Microsoft has called this problem resolved, which partly explains why help desks may treat the news with some suspicion.
What broke in classic Outlook
Microsoft's support page says the issue began after classic Outlook for Windows updated to build 20026.20182 or later. Affected users lost the Copilot Chat or Copilot entry points in Outlook. It hit people with a Copilot Chat (Basic) license and people with a paid Microsoft 365 Copilot (Premium) account.
According to Microsoft and BleepingComputer's reporting, affected users saw one or more of these symptoms:
- The Copilot button missing from the top-right area above the ribbon.
- The Copilot icon missing from the left app bar or More Apps area in classic Outlook.
- In Add Apps, Copilot may appear as an available app, but selecting Open does nothing.
- Adding Copilot through ribbon customization may show the command as unavailable or grayed out.
Copilot itself kept working. Copilot remains available from other entry points, such as Outlook on the web or the Microsoft Copilot standalone app or web experience. The bug removed the entry points in Outlook, not the service. That explains why users found it so frustrating: Copilot worked in a browser tab but not in the desktop app they use all day.
Section summary: Builds 20026.20182 and later of classic Outlook could hide every Copilot entry point for both Basic and Premium license holders. Copilot kept working through the web and the standalone app.
The root cause: Outlook couldn't read the user's profile
Microsoft blames the problem on how classic Outlook reads profile data. BleepingComputer reports that Microsoft traced it to a bug that prevented Outlook from retrieving some account information from the user's Outlook profile. Microsoft's own wording is that it fixed an issue in classic Outlook that could cause the Copilot entry point to be missing from the navigation pane when required account information could not be retrieved from the user's Outlook profile.
Microsoft's fix note doesn't name the profile field involved. While the issue was still under investigation, News4Hackers reported that the root cause [was] linked to MAPI property. That fits with the fix description, but Microsoft's final note gives no details, so treat it as reported context rather than confirmed engineering detail.
The support page also doesn't say how the fix is delivered. It doesn't say whether it needs a client update or comes from the service side, and it gives no rollout date. Don't assume every affected PC has already recovered.
Fixed in June, back in September
This is not the first time Microsoft has marked this issue fixed. BleepingComputer notes that Microsoft first announced in June that it had fixed the bug with a service change, but last month it said it had started investigating again after recent updates caused it to resurface.
Windows Report covered the first fix at the time. It reported that Microsoft marked the issue as fixed and said the Outlook Team resolved it through a service change on June 29, 2026. Back then, the reported scope was narrower. Microsoft described Classic Outlook for Windows users who only had the Copilot Chat (Basic) license. The issue appeared after Outlook updated to build 20026.20182 or later, while users with a paid Microsoft 365 Copilot license were not affected.
The current support page lists paying Premium customers as affected as well. That wider scope is worth noting. A bug that first hit only Basic users came back and also affected the paid tier. Admins who closed tickets in July on the strength of the June fix may want to reopen a few.
Section summary: The June 29 service change didn't hold. The issue came back after later updates and grew to cover Premium licenses, and Microsoft now traces it to profile data that Outlook couldn't read.
"Fixed" doesn't mean every missing button is fixed
Microsoft is careful on this point. Its note says the Copilot button might be missing for several different reasons, including licensing, Microsoft 365 app configuration, update channel, privacy settings, or other environmental factors. It tells users to work through its Copilot troubleshooters and its general guide to missing Copilot buttons.
So a user who still has no Copilot button may not be hitting this bug at all. Several unrelated problems produce the same symptom.
Troubleshooting checklist for classic Outlook
Here is Microsoft's guidance, in a practical order.
1. Check the "Show Apps in Outlook" setting
Microsoft says this setting can hide Copilot from the classic Outlook app bar. It also says the setting is separate from the bug it fixed. BleepingComputer describes it as a temporary workaround, but Microsoft lists it under additional troubleshooting. It's a sensible first check, not the cure for the profile bug.
- In classic Outlook, select File, then Options.
- Select Advanced.
- Under Outlook panes, check Show Apps in Outlook.
If the Copilot icon then appears in the app bar, the cause was this setting, not the bug.
2. Use Microsoft's official workarounds
Microsoft's workaround list for this known issue is short:
- Use new Outlook.
- Use Outlook Web Access (OWA).
- Create a new Outlook profile in classic Outlook.
Since the defect involved data Outlook couldn't read from the profile, a fresh profile makes sense. It isn't guaranteed to work, though. Users with large cached mailboxes, shared mailboxes or delegate setups should keep in mind that a new profile means rebuilding those settings and re-syncing mail.
3. Run the Copilot license troubleshooter
Microsoft's Get Help app includes a Copilot license troubleshooter for users who think they have a license but can't see the Copilot icon in eligible Microsoft 365 apps:
- Open the Get Help app.
- Search for Copilot License Troubleshooter.
- Follow the steps provided.
Get Help also has a separate Copilot connectivity troubleshooter. It checks for firewall rules and other connection blockers, so it covers network problems, not the Outlook profile bug.
4. Refresh the license and check the build
Microsoft's general guide to missing Copilot buttons recommends installing the latest build first. Then refresh the license: go to File > Account, select Update License, and restart all open Microsoft 365 apps.
5. Business users: check the update channel
This one catches a lot of enterprise users. Microsoft says Copilot features are not available in Microsoft 365 apps on the Semi-Annual Enterprise Channel. Licensed users need Current Channel or Monthly Enterprise Channel. To check, go to File > Account and look under Product Information. If it says Semi-Annual Enterprise Channel, the user needs the help desk to move the device to another channel. Microsoft notes that the web versions of the apps work in the meantime.
6. Check privacy settings
On Windows, go to File > Account > Account Privacy > Manage Settings. Make sure Experiences that analyze your content and All connected experiences are both turned on. If the organization manages these settings, only an admin can change them.
Section summary: Start with Show Apps in Outlook. Then work through license, build, update channel and privacy settings, and use a new profile, new Outlook or OWA as fallbacks.
Analysis: a small button with a bigger lesson
Calling this a cosmetic bug would undersell it. Microsoft has put Copilot at the center of Microsoft 365. In an app where it's being promoted that heavily, a missing button looks like a feature has been taken away, not like a display glitch. That's worse when the company is charging for the Premium tier. It's fair to ask whether a $30-a-seat feature should depend on a profile property that Outlook occasionally fails to read.
Microsoft does deserve some credit. Its support note doesn't claim to fix every missing button. It says plainly that several causes look identical from the user's side. Accurate documentation like that is more useful to a help desk than a hopeful "resolved" label.
Even so, the history argues for caution. A June service fix was followed by a regression in later updates, and the October fix comes with no stated delivery mechanism or date. Our view, based on general IT practice rather than anything Microsoft has said: admins should confirm the fix on a sample of affected machines before closing tickets in bulk, and should record build numbers and update channels in those tickets in case the problem comes back a third time.
This also fits a broader pattern of classic Outlook problems. BleepingComputer notes that this year Microsoft has also fixed classic Outlook issues that prevented some classic Outlook users from sending emails via Outlook.com and rendered the classic Outlook client unusable when enabling the Microsoft Teams Meeting Add-in. As Microsoft moves its attention to new Outlook, classic Outlook keeps picking up known-issue entries. Organizations still running the classic client should keep checking Microsoft's list of recent classic Outlook issues.
Bottom line
- What happened: On builds 20026.20182 and later, classic Outlook for Windows hid Copilot buttons for Basic and Premium users because it couldn't read required account information from the Outlook profile.
- Status: Microsoft marks the issue fixed as of its October 15 support update. This follows a June 29 fix that didn't hold.
- If the button is still missing: Check Show Apps in Outlook, run the Copilot license troubleshooter, confirm the build, update channel and privacy settings, and use new Outlook, OWA or a new profile if needed.
- Copilot still works on the web and in the standalone app while you troubleshoot.