Copilot Appears in Ribbon but Is Disabled in Outlook Classic – No Licensing or Policy Errors

Question

Hello, We are experiencing an issue where Microsoft 365 Copilot is functioning correctly in Outlook Web (OWA) but remains greyed out in Outlook Classic (Microsoft 365 Apps – Click-to-Run). Environment

• Microsoft 365 Copilot license confirmed assigned to user
• Copilot works successfully in Outlook Web
• Outlook Classic (Microsoft 365 Apps, Click-to-Run)
• Latest Office updates installed
• Shared Computer Activation (SCA) not enabled

Troubleshooting Performed

• Verified and corrected Autodiscover V2 registry setting (DisableAutodiscoverV2Service = 0)
• Confirmed correct Office update channel and fully updated Office
• Restarted Outlook and rebooted workstation
• Cleared Office licensing cache (Licensing, OneAuth, IdentityCache)
• Cleared WEF (Web add-in) cache
• Removed and recreated Outlook mail profile
• Verified Connected and Optional Connected Experiences are enabled
• Reviewed Office policy registry keys and ensured no local privacy policies are disabling connected experiences
• Confirmed Copilot appears in ribbon customization but remains greyed out in Classic Outlook

Current Behavior

• Copilot is visible but disabled (greyed out) in Outlook Classic
• Copilot works normally in Outlook Web
• No local policy or licensing errors detected

Based on our testing, this appears to be related to desktop Copilot eligibility, tenant policy configuration, or feature rollout limitations specific to Classic Outlook. Could you please confirm:

1. Whether Copilot is fully supported for this tenant in Outlook Classic on the current build/channel.
2. If there are any tenant-level settings restricting Copilot in desktop apps.
3. If additional backend provisioning is required for Classic Outlook integration.

We appreciate your assistance. Best regards,  Iman AbouhamzehHello,

We are experiencing an issue where Microsoft 365 Copilot is functioning correctly in Outlook Web (OWA) but remains greyed out in Outlook Classic (Microsoft 365 Apps – Click-to-Run).
Environment

• Microsoft 365 Copilot license confirmed assigned to user
• Copilot works successfully in Outlook Web
• Outlook Classic (Microsoft 365 Apps, Click-to-Run)
• Latest Office updates installed
• Shared Computer Activation (SCA) not enabled

Troubleshooting Performed

• Verified and corrected Autodiscover V2 registry setting (DisableAutodiscoverV2Service = 0)
• Confirmed correct Office update channel and fully updated Office
• Restarted Outlook and rebooted workstation
• Cleared Office licensing cache (Licensing, OneAuth, IdentityCache)
• Cleared WEF (Web add-in) cache
• Removed and recreated Outlook mail profile
• Verified Connected and Optional Connected Experiences are enabled
• Reviewed Office policy registry keys and ensured no local privacy policies are disabling connected experiences
• Confirmed Copilot appears in ribbon customization but remains greyed out in Classic Outlook

Current Behavior

• Copilot is visible but disabled (greyed out) in Outlook Classic
• Copilot works normally in Outlook Web
• No local policy or licensing errors detected

Based on our testing, this appears to be related to desktop Copilot eligibility, tenant policy configuration, or feature rollout limitations specific to Classic Outlook.
Could you please confirm:

1. Whether Copilot is fully supported for this tenant in Outlook Classic on the current build/channel.
2. If there are any tenant-level settings restricting Copilot in desktop apps.
3. If additional backend provisioning is required for Classic Outlook integration.

We appreciate your assistance.
Best regards,
[Moderator note: personal info removed] 

Answer 1

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Hi @Iman Abouhamzeh

Thank you for posting your question in the Microsoft Q&A forum.  

First, I’d like to clarify that this is a user‑to‑user support forum. Moderators, contributors, and external Microsoft employees participating here do not have access to backend systems, nor can we directly intervene in Microsoft product features. Our role is limited to providing technical guidance and sharing best practices based on reported issues, requests, or ideas. 

I understand that you are encountering an issue where the Copilot icon in your Classic Outlook ribbon remains inactive (grayed out or not clickable). 

If Copilot works normally on Outlook Web, please try the following steps in Classic Outlook: 

Re‑add your account: 

Remove your email account from Classic Outlook and add it back to force a full sync of settings. 

Repair Outlook 

Run an Online Repair for your Microsoft Office installation.  You can follow Microsoft’s guide here: Repair an Office application - Microsoft Support 

Reinstall Outlook 

If the issue persists after the repair, try uninstalling and reinstalling Outlook. 

Regarding your questions 

Whether Copilot is fully supported for your tenant in Classic Outlook on your current build/channel 

After reviewing documentation and testing in my environment, Copilot still appears normally on the left sidebar and the top‑right corner in Classic Outlook. This indicates the feature continues to function as expected. 

However, depending on your tenant settings and update channel, Copilot might not be fully enabled in Outlook Classic even if it works fine on Outlook Web. 

Whether any tenant‑level settings are restricting Copilot in desktop apps 

Yes, it is possible. There may be tenant‑level policies (Intune, GPO, App Configuration Policies) that restrict Copilot specifically in Classic Outlook, even if no local policy appears on your device. 

You could contact your IT administrator or check if other Microsoft 365 Copilot features work in Word, Excel, or Teams. If Copilot functions in other applications but not Outlook, the issue likely involves Outlook-specific configuration issues rather than organization-wide policy restrictions. 

Whether additional backend provisioning is required for Outlook Classic 

As Microsoft’s official documentation, no separate provisioning is needed for Outlook Classic beyond these three conditions: 

-A valid Microsoft 365 Copilot license. 

-The primary mailbox is in Exchange Online. 

-The device meets app, update channel, privacy, and network requirements. 

If all three conditions are met but Copilot is still grayed out, this strongly suggests a misconfiguration or policy conflict affecting the feature. 

Given the behavior you’re experiencing, the issue may require deeper backend validation. To better address and verify this, Microsoft’s support team will need to step in. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.    

Reference: Get support - Microsoft 365 admin | Microsoft Learn 

Note: To create a support ticket, you need to have Microsoft 365 admin privileges and if you aren’t admin of your organization, please contact the admin of creating a new ticket. 

As forum moderators, we don’t have access to the detailed logs or backend systems needed to troubleshoot this effectively due to privacy and security constraints. For that reason, the most efficient solution would be to contact Microsoft’s support team directly.  

I have found some relevant articles that might help, you could refer via: 

Set Up Microsoft 365 Copilot and Assign Licenses | Microsoft Learn 

Data, Privacy, and Security for Microsoft 365 Copilot | Microsoft Learn 

Copilot icon not showing in Outlook: enable and troubleshoot 

Note: Microsoft is providing this information as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link. 

I hope this helps. 

Please feel free to correct me if I misunderstood your request. If you have any additional concerns, feel free to comment below. I would be more than happy to assist. 

---

Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

Microsoft 365 Copilot is supported in both classic Outlook and the new Outlook client, but only when specific requirements are met. The behavior described (Copilot working in Outlook on the web but greyed out in classic Outlook) is consistent with one of the following supported limitations rather than a missing license or client-side misconfiguration.

Key points from current requirements and behavior:

1. Support in classic Outlook and mailbox location
   • Microsoft 365 Copilot works with classic Outlook and the new Outlook for Windows and Mac.
   • Copilot is only supported on primary mailboxes hosted in Exchange Online. It is not available for:
     • On‑premises primary mailboxes (even in hybrid scenarios)
     • Archive mailboxes
     • Group mailboxes
     • Shared or delegate mailboxes
   • In hybrid deployments where the primary mailbox is on‑premises, Copilot can still work in other Microsoft 365 services, but Copilot in Outlook cannot be grounded in mailbox content and is not supported for that mailbox.
   If the user’s primary mailbox is not in Exchange Online, Copilot in classic Outlook will remain unavailable/greyed out even though it works in Outlook on the web for other Copilot experiences.
2. App and channel requirements
   • Microsoft 365 Apps must be deployed and on a supported update channel.
   • Copilot features are not available when using Semi‑Annual Enterprise Channel. To use Copilot in desktop apps, the device must be on Current Channel or Monthly Enterprise Channel.
   • Copilot is not available when using device‑based licensing for Microsoft 365 Apps.
   The question states that:
   • The correct update channel is already confirmed and Office is fully updated.
   • Shared Computer Activation is not enabled.
   • Licensing is user‑based and Copilot works in OWA.
   Under those conditions, Copilot is supported in classic Outlook provided the mailbox is a primary Exchange Online mailbox and the privacy/network requirements are met.
3. Privacy and connected experiences
   • Copilot availability in Microsoft 365 Apps is affected by privacy controls for connected experiences.
   • For Copilot to appear and be usable, the following must be enabled in the desktop apps:
     • Experiences that analyze your content
     • All connected experiences
   • These can be controlled by tenant‑level policies. If an organization disables these connected experiences via policy, Copilot can appear but remain disabled.
   The question indicates these settings are enabled locally and no local policies are blocking them. If tenant‑level policies are enforcing more restrictive privacy settings, they can still prevent Copilot from being active in classic Outlook even when OWA works.
4. Tenant‑level and backend considerations Based on the documented behavior:
   1. Whether Copilot is fully supported for this tenant in Outlook Classic on the current build/channel
      • If the tenant has Microsoft 365 Copilot licenses assigned and:
        • Users are on Microsoft 365 Apps (Click‑to‑Run) on Current Channel or Monthly Enterprise Channel, and
        • Users have primary mailboxes in Exchange Online, and
        • Device‑based licensing is not used, then Copilot is supported in classic Outlook for that tenant. If the primary mailbox is on‑premises or in an unsupported mailbox type, Copilot in Outlook is not supported even though Copilot works elsewhere.
   2. Tenant‑level settings that can restrict Copilot in desktop apps
      • Tenant or org‑wide policies that control connected experiences and privacy settings for Microsoft 365 Apps can restrict Copilot in desktop apps. Specifically, policies that disable:
        • “Experiences that analyze your content”, or
        • “All connected experiences” will prevent Copilot from being available in Word, Excel, PowerPoint, and Outlook desktop, even if Copilot works in web apps.
   3. Additional backend provisioning for classic Outlook
      • The documented requirements do not describe a separate backend provisioning step specifically for classic Outlook beyond:
        • Assigning a Copilot license that supports Microsoft 365 Copilot.
        • Ensuring the mailbox is a primary Exchange Online mailbox.
        • Meeting app, channel, privacy, and network requirements.
      • No additional Outlook‑specific provisioning is required if those conditions are met.

Recommended checks for this scenario (based on the documented behavior):

1. Verify mailbox location and type
   • Confirm that the affected user’s primary mailbox is hosted in Exchange Online and not on‑premises or only as an archive/shared/delegate mailbox. If it is not a primary Exchange Online mailbox, Copilot in Outlook desktop is not supported.
2. Confirm update channel and licensing model
   • Re‑verify that the client is not on Semi‑Annual Enterprise Channel and is not using device‑based licensing, as both are explicitly unsupported for Copilot.
3. Review tenant‑level privacy/connected experiences policies
   • Have a Microsoft 365 admin review organization‑wide policies that control:
     • Connected experiences
     • “Experiences that analyze your content”
     • “All connected experiences”
   • If these are disabled at the tenant level for desktop apps, Copilot will remain greyed out even when it works in OWA.

If all of the above are confirmed compliant (primary mailbox in Exchange Online, supported channel, user‑based licensing, connected experiences allowed), the configuration meets the documented requirements and no extra backend provisioning for classic Outlook is required.

---

References:

• Microsoft 365 Copilot and on-premises mailboxes
• Microsoft 365 app and network requirements for Microsoft 365 Copilot
• Copilot is missing, disabled, or doesn't work correctly
• How to find and enable missing Copilot button in Microsoft 365 apps
• Microsoft 365 Copilot and privacy controls for connected experiences