'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Cannot Send Email from a Shared Outlook Folder
Question details
Users are unable to send emails from shared Outlook folders, even after being granted the necessary permissions.
- Product
- Microsoft Outlook
- Device & OS
- not provided
- Scenario
- Replying to or sending emails using a shared mailbox folder's address.
- Observed behavior
- Sending fails across multiple mailboxes and in Outlook on the web, with the problem persisting despite having Send As permissions.
Verify with your IT administrator that your account still has active 'Send As' permissions for the shared mailbox, and allow up to 24 hours for newly applied permissions to fully sync across servers.
Remove and Reassign Mailbox Permissions
Resetting folder permissions forces Outlook to synchronize the correct access rights, which often resolves hidden server-side conflicts.
In many cases, permission synchronization fails between the Exchange server and the Outlook client. Completely removing and re-adding permissions is the most effective way to clear the bad cache.
Log in to your Outlook Web App to check if the error is isolated to the desktop client or affects the web version as well.
Have your Exchange administrator completely remove your account's 'Send As' and folder permissions for the affected shared mailbox in the Exchange Admin Center.
Wait a few minutes, then have the administrator re-add the 'Send As' permissions for your user account.
Right-click the shared folder in your Outlook view and remove it. Restart the Outlook application, and add the shared folder back to force a fresh sync.
Test with an Alternative Shared Mailbox
Testing another mailbox helps identify if the issue is specific to a single folder or a broader Microsoft 365 service outage.
Upgrade Your Productivity with WPS Office
While Exchange and Outlook server issues require IT administration to resolve, you can ensure your personal and team productivity remains uninterrupted. WPS Office is a powerful, free alternative to Microsoft Office that is fully compatible with your existing documents.
- 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the software: Run the downloaded installer file and follow the on-screen instructions to set up WPS Office on your device.
- 3. Open your files: Launch WPS Office and seamlessly open your existing Microsoft Office documents, spreadsheets, and presentations.
Frequently Asked Questions
Why does Outlook say I don't have permission to send from this mailbox?
This error often happens if the offline address book is out of sync in the desktop app, or if the 'Send As' permissions haven't fully replicated across Microsoft Exchange servers after being granted.
How long does it take for Send As permissions to take effect in Outlook?
It can take anywhere from a few hours up to 24 hours for 'Send As' or 'Send on Behalf' permissions to fully propagate and function correctly in your Outlook client.
Can I test if I have proper permissions using Outlook on the web?
Yes. Opening the shared mailbox directly in Outlook on the web (OWA) is the best way to verify if you have the correct permissions, as it bypasses local desktop caching issues.
