Microsoft Outlook Bug Removes Copilot Button for Windows Users

Key Takeaways

• A software defect in classic Outlook for Windows caused Copilot Chat and its associated entry points to disappear for users.
• The issue specifically affected users with Basic-tier Copilot licenses after updating to Outlook build 20026.20182 or higher.
• Users with full M365 paid Copilot (Premium) licenses were unaffected.
• Microsoft deployed a server-side fix on June 29, 2026, resolving the problem without requiring a client-side update.
• While not a security vulnerability, the incident highlights potential complications in feature management within tiered SaaS licensing models.

Microsoft Outlook Bug Removes Copilot Button

A recent software defect within the classic Outlook for Windows application led to the unexpected disappearance of Copilot Chat and all related user interface elements. Microsoft confirmed that the issue was specifically linked to certain Basic-tier Copilot licenses, disrupting workflows for individuals relying on AI-assisted email management features.

The anomaly has since been rectified through a server-side patch, restoring functionality for affected users.

Impacted Users and Specifics of the Flaw

The problem emerged after classic Outlook for Windows updated to build 20026.20182 and subsequent versions. Users possessing a Copilot Chat (Basic) license found themselves unable to access Copilot Chat or any of its entry points within the application. It is noteworthy that users holding the comprehensive M365 paid Copilot (Premium) license remained unaffected, pointing to a specific licensing validation flaw introduced in the problematic build rather than a widespread platform failure.

The bug manifested across multiple user interface elements within classic Outlook, making its absence difficult to overlook:

• The dedicated Copilot button vanished from the top-right section above the ribbon.
• The Copilot icon disappeared from the left application bar and the “More Apps” section.
• Although Copilot appeared in the “Add Apps” list, selecting “Open” produced no response.
• Attempts to add Copilot via ribbon customization showed the command as grayed out and unavailable.

Intriguingly, during the period of the outage, Copilot access remained fully functional through alternative channels, including Outlook on the web and the standalone Microsoft 365 Copilot application or web interface. This selective disruption suggested that the fault was isolated to how the classic Outlook desktop client validated Basic-tier licenses against the new build, rather than indicating a broader server-side Copilot service interruption.

Resolution and Mitigation Steps

The Outlook Team deployed a server-side fix on June 29, 2026, which effectively resolved the licensing-validation issue without necessitating a client-side patch. Users who did not observe the change immediately were advised to restart Outlook to ensure the server-side correction took effect. Community reports have since corroborated that the issue was resolved following this update, with affected users confirming the restoration of Copilot functionality.

For users still operating on outdated builds, Microsoft recommended checking for the latest update by navigating to File > Office Account > Update Options > Update Now, ensuring the fix propagated correctly.

Before the official fix rolled out, Microsoft and community troubleshooting guides provided interim workarounds for administrators requiring immediate Copilot access:

• Switch to the new Outlook experience or Outlook Web Access (OWA), where Copilot remained fully operational.
• Revert the Current Channel to the pre-issue build (16.0.20026.20168) using an administrator Command Prompt with the officec2rclient.exe update command.
• Temporarily disable automatic updates via File > Office Account > Update Options > Disable Updates to prevent reverting to the problematic build.
• Set a reminder to re-enable updates around mid-August or monitor Microsoft’s Known Issues page for confirmation that the fix has stabilized.

Broader troubleshooting resources also highlighted related root causes to investigate in similar Copilot-visibility issues. These included confirming that the Office update channel supports Copilot (the Semi-Annual Enterprise Channel does not), verifying that tenant privacy settings for “Experiences that analyze your content” and “All connected experiences” are enabled, and ensuring that Shared Computer Activation environments, which block Copilot entirely, are not in use.

While this specific incident was a licensing-display bug rather than a security vulnerability, it underscores the potential fragility of feature-gating logic tied to tiered Software-as-a-Service (SaaS) licensing in widely deployed productivity suites.

What You Should Do

• Ensure Updates are Enabled: Verify that your Microsoft Office applications, particularly Outlook, are configured for automatic updates to receive critical fixes promptly.
• Restart Outlook: If you experienced the issue, restart your Outlook application to ensure the server-side fix has been applied.
• Check for Latest Build: Navigate to File > Office Account > Update Options > Update Now to manually check for and install the latest updates if you are on an older build.
• Monitor Microsoft’s Known Issues: For any unexpected feature disappearances, regularly consult Microsoft’s official Known Issues page before assuming a misconfiguration or other problem.
• Review Licensing: Understand the differences between Basic and Premium Copilot licenses to anticipate feature availability and potential discrepancies.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.