How To Send Mail From A Shared Mailbox: The Complete Enterprise Guide

Sending mail from a shared mailbox requires specific configuration permissions such as Send As or Send on Behalf, allowing users to collaborate seamlessly without exposing individual user credentials. Achieving this requires correct Exchange Online directory settings, client-side caching updates, and a clear understanding of how the From field behaves across Outlook, Outlook on the Web, and mobile environments.

Essential Prerequisites and Permissions Checklist

Deploying a shared mailbox workflow successfully relies on proper administrative provisioning, Active Directory synchronization, and client-side configuration. Without these foundational elements, users will encounter non-delivery reports, permission errors, and missing identity parameters when attempting to dispatch communications.

• Essential Tools and Software: Access to the Microsoft 365 Admin Center, Exchange Admin Center (EAC), or remote PowerShell modules, coupled with a supported desktop or web-based mail client like Outlook for Windows, Outlook for Mac, or Outlook on the Web.
• Mandatory Prerequisite Knowledge: Global Administrator, Exchange Administrator, or User Administrator privileges to assign permissions; familiarity with Azure Active Directory and hybrid environments.
• Estimated Setup and Execution Duration: 5 to 15 minutes for permission propagation, and 2 to 24 hours for global address list synchronization across cloud and hybrid tenants.

Step-by-Step Configuration and Execution Workflow

Step 1: Verify and Assign Send As and Send on Behalf Permissions

• Log in to the Microsoft 365 Admin Center using administrative credentials and navigate to the Teams and groups page, followed by Shared mailboxes.
• Select the specific shared mailbox you wish to configure to open its property pane on the right side of the interface.
• Locate the Members section and click Edit next to Read and manage permissions and Send as permissions to add the target users or security groups.
• Alternatively, connect to Exchange Online PowerShell via administrative console and execute the Add-RecipientPermission cmdlet with the trusted user Principal Name and AccessRights parameter set to SendAs.

Pro-Tip: Always assign Send As permissions through security groups rather than individual user accounts if your organization manages a large volume of rotating personnel; this drastically reduces administrative overhead during staffing transitions.

Step 2: Add the Shared Mailbox to Your Outlook Desktop Client

• Open Microsoft Outlook on your desktop and navigate to the File tab in the upper-left corner of the ribbon interface.
• Ensure you are on the Info category, click Account Settings, and select Account Settings from the drop-down menu.
• Highlight your primary exchange account in the list and click Change, then select More Settings in the lower right corner.
• Navigate to the Advanced tab, click the Add button, and type the exact email address of the shared mailbox before clicking Apply and OK to save the directory lookup.

Warning: Do not attempt to add a shared mailbox as a completely separate secondary email account using its own password, as shared mailboxes are designed to be non-interactive accounts without direct sign-in credentials.

Step 3: Configure the From Field and Dispatch Your Message

• Click the New Email button in Outlook to open a fresh compose window, and locate the From field positioned above the To line.
• If the From field is not immediately visible, navigate to the Options tab in the ribbon and click the From toggle button to expose the sender identity selector.
• Click the From button, select Other Email Address from the drop-down menu, and browse the Global Address List to choose the shared mailbox.
• Compose your message content, verify that the sender address reflects the shared identity, and click Send to transmit the email through the organizational exchange transport pipeline.

Shared Mailbox Feature Comparison and Permission Matrix

Common Configuration Failures and Field Fixes

• Symptom: Non-Delivery Report (NDR) with error code 5.7.1 client permissions deny when attempting to send.
  
  
  • Root Cause: The issuing client has not synchronized the recent permission changes from the Azure Active Directory or Offline Address Book (OAB).
  • Actionable Fix: Force an update of the Offline Address Book in Outlook via Send / Receive tab > Send/Receive Groups > Download Address Book, or wait up to 60 minutes for permission propagation.
• Symptom: Sent items are saved only in the sender's personal Sent Items folder rather than the shared mailbox.
  
  
  • Root Cause: The mailbox configuration lacks the parameter telling Exchange to copy sent items to the shared container.
  • Actionable Fix: Run the PowerShell command Set-Mailbox -Identity "SharedMailbox" -MessageCopyForSentAsEnabled $True and Set-Mailbox -Identity "SharedMailbox" -MessageCopyForSendOnBehalfEnabled $True.
• Symptom: The From drop-down menu does not retain the shared mailbox address for future compositions.
  
  
  • Root Cause: AutoComplete cache corruption or missing Read and Manage permissions required to cache the mailbox directory entry.
  • Actionable Fix: Ensure the user has at least Read and Manage permissions assigned alongside Send As, clear the Outlook AutoComplete list cache, and re-add the mailbox via Account Settings.

Frequently Asked Questions

Can I send mail from a shared mailbox on mobile devices?

Yes, users can send mail from a shared mailbox on mobile devices by adding the shared mailbox as an additional account in Outlook mobile, provided they have Full Access and Send As permissions. Alternatively, users can manually type the shared email address in the From field within Outlook on iOS or Android if the mailbox has already been added to their desktop profile.

Do shared mailboxes require an active Microsoft 365 license?

Shared mailboxes up to 50 gigabytes of storage do not require a paid license as long as usage stays within standard organizational limits. If storage exceeds 50 GB, or if the mailbox is used for archiving or automated retention compliance beyond standard parameters, an Exchange Online Plan 2 license must be assigned.

Why do my recipients see "on behalf of" when I send from a shared mailbox?

This occurs when you have been granted Send on Behalf permissions rather than Send As permissions. To remove the "on behalf of" indicator and display only the shared mailbox name, an administrator must update your permissions to Send As inside the Exchange Admin Center.

How do I stop sent items from disappearing when using a shared mailbox?

By default, Microsoft 365 saves sent messages only in the personal mailbox of the user who clicked send. To ensure sent items also reside within the shared mailbox sent folder for team visibility, administrators must enable the MessageCopyForSentAsEnabled property via Exchange Online PowerShell.

Can external users send mail using our organization's shared mailbox?

External users cannot be granted permissions to send mail from an internal shared mailbox unless they are provisioned as guest users with authenticated directory accounts within your tenant. Allowing external relay without authentication is blocked by default to prevent spam and relay exploitation.

Streamline your organization's collaborative communications by auditing your shared mailbox permissions and deploying standardized enterprise policies today.