Using classic Outlook for Windows in business environments
Hi @Nadir Hasan
Thank you for the details. I’m a fellow community user, so I can’t check your tenant, but here is my thought.
Since the user can already send from the shared mailbox in OWA and New Outlook, the permission itself seems to be working on the server side. Outlook (Classic) can take longer to pick up a newly granted or changed permission, because it relies on settings synced to the local profile.
Could you please try the following?
1.Wait about one day if the Send As or Send on Behalf permission was granted or changed recently, then try sending a new email from Classic again.
2.Because the issue started recently, an admin can try removing and re-granting the relevant send permission. Please also verify the existing permissions with Exchange Online PowerShell, rather than relying only on what the Exchange admin center shows.
3.In Classic, temporarily test the account in Online Mode. If sending works in Online Mode but not in Cached Exchange Mode, the problem may be related to delegation data stored in the OST or Outlook’s cache. This option may be grayed out. If so please contact your admin to change the policy that is locking it
4.Remove the shared mailbox from the Classic profile and add it again. Automapping is on by default, so the shared mailbox appears in Classic automatically while the user has Full Access, and the user can’t remove it from Outlook themselves.
To remove it, an admin can remove the user’s Full Access permission in the Exchange admin center (Manage mailbox delegation > Read and manage). The mailbox should disappear from the profile after some time. Please keep the Send As/Send on Behalf permission unchanged. To add it back without automapping, an admin runs the following in Exchange Online PowerShell. The first command removes Full Access, and the second grants it again with automapping disabled:
Remove-MailboxPermission -Identity <SharedMailbox> -User <User> -AccessRights FullAccess -Confirm:$false
Add-MailboxPermission -Identity <SharedMailbox> -User <User> -AccessRights FullAccess -AutoMapping $false
Then the user adds the mailbox manually in Classic: File > Account Settings > Account Settings > select the Exchange account > Change > More Settings > Advanced > Add. Type the shared mailbox name, click OK, then Next and Finish. Menu names can differ slightly between versions.
Please refer the following article: Remove automapping for a shared mailbox | Microsoft Learn
5.Create a brand-new Outlook profile: Control Panel > Mail > Show Profiles > Add. Configure only the user’s primary mailbox, then test the shared mailbox again. The issue occurring on multiple devices doesn’t fully rule out a profile problem if the same account and the same automapped configuration are used on all of them.
Please let me know the result.