How to Fix Shared Mailbox Sending Permissions in Microsoft 365
Summary
This guide helps you troubleshoot and resolve: How to Fix Shared Mailbox Sending Permissions in Microsoft 365. Follow the steps below to fix the issue.
Common Causes
Fix Shared Mailbox Sending Permissions in Microsoft 365
Shared mailboxes in Microsoft 365 allow multiple team members to access a single email address, such as info@yourdomain.com.au or sales@yourdomain.com.au. A common issue occurs when staff members can open the shared mailbox and read messages, but receive an error when attempting to send emails from that address. This usually happens because the Send As or Send on Behalf permissions have not been correctly assigned to the user account. This guide explains how to resolve shared mailbox sending permissions for your organisation.
Before You Begin
You must sign in with an account that has Global Administrator or Exchange Administrator privileges in Microsoft 365. Before assigning permissions, confirm that the object is actually a shared mailbox and not a user mailbox or a distribution group. Sending permissions cannot be applied to distribution groups in the same way.
Assign Send As Permissions
Send As allows a user to send email that appears to come directly from the shared mailbox address. Recipients will not see the individual staff member's name in the sender field.
Via the Microsoft 365 Admin Centre
- Sign in to the Microsoft 365 admin centre.
- In the left-hand navigation, select Teams & groups, then choose Shared mailboxes.
- Click on the shared mailbox you need to modify to open its properties pane.
- Select the Mailbox permissions tab.
- Under Send As, select Edit.
- Select Add permissions.
- Search for the staff member who needs sending rights and select their name from the results.
- Select Add, then select Save changes.
Via Exchange Online PowerShell
Use this method if you prefer PowerShell or need to script permission changes.
- Connect to Exchange Online PowerShell using an administrator account.
- Run the following command, replacing the values with your shared mailbox and user details:
Add-MailboxPermission -Identity "info@yourdomain.com.au" -User "jane.doe@yourdomain.com.au" -AccessRights SendAs
Assign Send on Behalf Permissions
Send on Behalf allows a user to send email from the shared mailbox, but recipients will see that the message was sent on behalf of the shared mailbox by the individual staff member. For example, the sender may appear as "Jane Doe on behalf of Sales Team".
Via the Exchange Admin Centre
- Sign in to the Exchange admin centre.
- In the left-hand navigation, select Recipients, then choose Mailboxes.
- Click on the shared mailbox to open its properties.
- Select the Mailbox delegation tab.
- Under Send on Behalf, select Edit.
- Select Add permissions.
- Search for and select the required user.
- Select Add, then select Save.
Via Exchange Online PowerShell
- Connect to Exchange Online PowerShell using an administrator account.
- Run the following command, replacing the values with your shared mailbox and user details:
Set-Mailbox -Identity "info@yourdomain.com.au" -GrantSendOnBehalfTo "jane.doe@yourdomain.com.au"
Grant Full Access Permissions
In most cases, a user who needs to send from a shared mailbox also requires Full Access so they can open the mailbox and manage its contents. Without Full Access, sending permissions may not function as expected in Outlook.
Via the Microsoft 365 Admin Centre
- Sign in to the Microsoft 365 admin centre.
- Navigate to Teams & groups > Shared mailboxes.
- Select the shared mailbox and open the Mailbox permissions tab.
- Under Full Access, select Edit.
- Select Add permissions, choose the user, then select Add and Save changes.
Via Exchange Online PowerShell
Add-MailboxPermission -Identity "info@yourdomain.com.au" -User "jane.doe@yourdomain.com.au" -AccessRights FullAccess -AutoMapping $true
Troubleshooting Sending Issues
User Still Cannot Send After Permissions Are Assigned
- Permission changes in Microsoft 365 can take up to 60 minutes to replicate across all servers. Ask the affected user to wait at least one hour before testing if the change does not work immediately.
- Ask the user to restart Microsoft Outlook. Desktop clients often cache permissions and require a restart to recognise new rights.
- If using Outlook on the web, sign out and sign back in to refresh the session.
- Confirm the user has Full Access to the shared mailbox in addition to Send As or Send on Behalf rights.
- Verify that the object is a shared mailbox and not a user mailbox or distribution group.
Outlook Cached Credentials and Profile Issues
- Open Windows Credential Manager and remove any cached credentials related to the shared mailbox or the user's Microsoft 365 account. Outlook may be attempting to send using stale credentials.
- If the issue persists, recreate the user's Outlook profile. A corrupted OST file or damaged profile can prevent sending even when server-side permissions are correct.
- After recreating the profile, allow Outlook to download the shared mailbox folder again before testing.
Mail Flow and Transport Rules
- Check the Exchange admin centre for any mail flow rules or transport rules that might be blocking or redirecting messages sent from the shared mailbox.
- If your organisation uses hybrid Exchange with on-premises servers, ensure directory synchronisation is healthy. Permission changes made in the cloud may not replicate to on-premises Exchange if sync is broken.
Error: "You Do Not Have Permission to Send to This Recipient"
- Verify that the correct permission type was assigned. Send As and Send on Behalf are not interchangeable.
- Ensure the user account is not blocked from sending mail due to suspicious activity or a compromised password.
- Check whether the shared mailbox has been disabled or converted to a different mailbox type.
If you have followed these steps and staff members still cannot send from the shared mailbox, Open a Ticket with our Brisbane support team for further assistance.
Still Having Issues?
💻 Open a Ticket