Using classic Outlook for Windows in business environments
Hi @Vicente B,
Thank you for the update and for providing the screenshots.
Given the scale of impact in your organization and the fact that the behavior differs from what is observed in my environment, I recommend opening a support case with Microsoft Support for further investigation.
For business support:
- Find your Microsoft 365 admin: If you don't know who the global admin is in your organization, you can find guidance here: How can I find my Microsoft 365 admin? - Microsoft Support
- Submit a service request: The Global Administrator should create a support request with Microsoft to receive advanced technical assistance. For detailed instructions, see: Get support - Microsoft 365 admin | Microsoft Learn
If your subscription is from a partner or reseller, contact the reseller's support provider to help open a service request on behalf of you instead.
When contacting support, I suggest including:
- The screenshots you shared showing Copilot available in the primary mailbox and unavailable in the shared mailbox.
- The Outlook version and build information.
- Details on how the shared mailboxes are configured (Full Access + Send As permissions).
- Confirmation that the issue affects multiple users and shared mailboxes.
- Confirmation that the same shared mailbox works correctly in New Outlook and OWA.
This information should help the support team determine whether this is a tenant-specific issue, a Classic Outlook limitation, or a bug requiring review by the Outlook engineering team.
Please feel free to share any updates from Microsoft Support, as the outcome may be helpful to other community members experiencing similar behavior.
Best regards.