How To Send On Behalf In Outlook: Complete Guide To Mailbox Permissions And Delegate Access

Sending on behalf in Outlook requires the specific Send on Behalf permission, which allows a delegate to compose and transmit emails where the recipient sees both the delegate’s and the owner’s names in the "From" field. This process is distinct from "Send As" permissions and is primarily managed through the Outlook Delegate Access settings or the Microsoft 365 Admin Center, requiring a propagation period of approximately 60 minutes for global synchronization.

Essential Technical Prerequisites and Permission Requirements

Before attempting to configure delegate workflows, it is vital to understand the infrastructure underlying Microsoft Exchange and Microsoft 365 environments. Sending on behalf is not a simple client-side toggle; it is a server-side permission that dictates how the Exchange Information Store handles message headers and transport protocols.

To successfully implement this feature, ensure the following requirements are met:

• Account Compatibility: Both the mailbox owner (the person granting permission) and the delegate (the person sending the mail) must be on the same Exchange organization or Microsoft 365 tenant. Cross-tenant "Send on Behalf" functionality is generally not supported without complex federation.
• Outlook Client Version: While the web interface supports these features, the full desktop version of Outlook (Microsoft 365 Apps for Enterprise or Outlook 2021/2019) provides the most robust management interface for Delegate Access.
• Administrative Access: If the owner cannot access their own settings, a Global Administrator or Exchange Administrator must be available to apply permissions via the Exchange Admin Center (EAC) or PowerShell.
• Global Address List (GAL) Visibility: Both accounts must be visible in the Global Address List. If a mailbox is hidden from the address book, the delegate selection process will fail.
• Estimated Configuration Time: Initial setup takes 5-10 minutes, but server-side propagation can take anywhere from 15 minutes to 2 hours depending on the complexity of the hybrid or cloud environment.

Comprehensive Implementation Framework for Mailbox Delegation

There are two primary methods for establishing "Send on Behalf" permissions: the User-Managed Delegate method and the Admin-Managed Exchange method. The following steps detail both procedures to ensure full coverage regardless of your organizational role.

Step 1: Granting Permissions via Outlook Delegate Access

The most common way for an executive or manager to allow an assistant to send on their behalf is through the Outlook Desktop client. This method is preferred because it allows the owner to maintain control over their own security settings without IT intervention.

1. Launch the Outlook desktop application and navigate to the File tab in the top-left corner of the ribbon.
2. Select Account Settings and click on Delegate Access from the dropdown menu.
3. In the Delegates dialog box, click the Add button. This will launch the Global Address List.
4. Search for and double-click the name of the individual who will be sending on your behalf, then click OK.
5. The Delegate Permissions dialog box will appear. Here, you must define the scope of access. For "Send on Behalf" to function correctly, the delegate does not strictly need "Editor" access to all folders, but they must be added to this list.
6. Ensure the checkbox labeled "Delegate receives copies of meeting-related messages sent to me" is selected if the delegate is also managing your calendar, as this is the most common use case for "Send on Behalf" workflows.
7. Click OK to close the permissions box and then click OK again to finalize the delegate list.

Pro-Tip: Granting "Author" or "Editor" permissions to the Inbox folder specifically is often necessary if you want the delegate to be able to draft and organize messages within your own folder structure in addition to just sending them.

Step 2: Administrative Configuration via Microsoft 365 Admin Center

In scenarios where the mailbox owner is unavailable or when managing shared mailboxes, an IT administrator must perform the configuration at the tenant level. This method is more authoritative and overrides client-side settings.

1. Log in to the Microsoft 365 Admin Center using credentials with at least Exchange Administrator privileges.
2. Navigate to the Users section and select Active Users.
3. Select the user who owns the mailbox (the person the email will be sent "on behalf of").
4. In the fly-out pane that appears, navigate to the Mail tab.
5. Select Manage mailbox permissions.
6. Locate the section labeled Send on behalf of and click Edit.
7. Click Add permissions, search for the delegate's name, select them, and click Save.

Warning: Do not confuse "Send on Behalf" with "Send As." If you grant "Send As" permissions, the recipient will never know a delegate sent the email. If your corporate compliance policy requires an audit trail of who actually clicked "Send," you must strictly use "Send on Behalf."

Step 3: Enabling and Using the From Field in Outlook

Once permissions are granted, the delegate must manually trigger the "Send on Behalf" functionality within their own Outlook compose window. It is not always visible by default.

1. Open a New Email message window in Outlook.
2. Navigate to the Options tab on the ribbon.
3. In the Show Fields group, click the From button. This adds a "From" dropdown menu above the "To" field.
4. Click the From button that now appears in the message header and select Other Email Address.
5. In the dialog box, click the From button to select the owner's name from the Global Address List. Do not type it manually, as this can cause resolution errors with the underlying X.500 address.
6. Compose your message as usual and click Send.

The recipient will receive an email where the sender information reads: "Delegate Name on behalf of Owner Name."

Technical Comparison of Mailbox Permissions

Understanding the technical nuances between different permission levels is critical for maintaining security and operational transparency. The following table breaks down the three primary methods of sending email through another account in a Microsoft Exchange environment.

Troubleshooting Common Send on Behalf Failures

Even with correct configurations, the interaction between local Outlook caches and Exchange servers can lead to delivery failures or permission errors. Use the following remedies to resolve the most frequent issues.

• Error: "You do not have permission to send the message on behalf of the specified user."

  
  
  
  • Root Cause: This is typically caused by a delay in Active Directory synchronization or a corrupted Offline Address Book (OAB).
  • Actionable Fix: Force an update of the Offline Address Book. Go to the Send/Receive tab, click Send/Receive Groups, and select Download Address Book. Ensure "Download changes since last Send/Receive" is checked. If the error persists, the delegate should delete the owner's address from their "Auto-Complete" list by clicking the 'X' next to the name when typing in the "From" field, then re-selecting it from the GAL.

• Issue: The "From" field does not show the owner's email address as an option.

  
  
  
  • Root Cause: The delegate has not manually added the address to their compose window "From" dropdown, or the profile has not yet recognized the new server-side permissions.
  • Actionable Fix: In a new email, click From > Other Email Address and physically select the owner from the Global Address List. This "pins" the address to the delegate's Outlook profile for future use.

• Issue: Sent items appear in the Delegate's Sent Items folder instead of the Owner's.

  
  
  
  • Root Cause: By default, Exchange places sent messages in the folder of the person who actually clicked "Send."
  • Actionable Fix: An administrator must run a PowerShell command to change this behavior. Use the command: Set-Mailbox -MessageCopyForSendOnBehalfEnabled $true. This ensures a copy of the sent message is placed in both the delegate's and the owner's Sent Items folders.

Frequently Asked Questions

Can I send on behalf of someone from the Outlook Web App (OWA)?

Yes, you can send on behalf in OWA by clicking "New Mail," clicking the ellipsis (three dots) for more options, and selecting "Show From." Right-click your own address in the From field, click "Remove," and then type the name of the person you are sending on behalf of.

Does "Send on Behalf" work on Outlook for iOS or Android?

The mobile app support for "Send on Behalf" is limited. While you can sometimes see shared mailboxes, the ability to toggle the "From" field to a "Send on Behalf" delegate status often requires the account to be added as a shared mailbox rather than relying on delegate permissions alone.

What is the limit on how many delegates can send on behalf of one person?

While there is no hard-coded limit for the number of delegates, Microsoft recommends keeping this number under 10 for performance reasons. Excessive delegates can cause synchronization delays and issues with the "Delegate Information" property in the mailbox metadata.

Why does the email say "on behalf of" even when I want it to be secret?

This is the intended design of the "Send on Behalf" permission. If you require the sender's identity to be hidden so that only the owner's name appears, you must ask your IT Administrator to change your permissions from "Send on Behalf" to "Send As" in the Exchange Admin Center.

How do I remove Send on Behalf permissions?

To remove permissions, the owner should go to File > Account Settings > Delegate Access, select the user, and click Remove. If the permission was granted by an admin, it must be removed via the Microsoft 365 Admin Center under the "Manage mailbox permissions" section of the user's mail settings.

Optimize Your Corporate Communications Today

Mastering Microsoft 365 permissions ensures your executive team operates with maximum efficiency and security. Contact our technical support team to implement advanced mailbox architecture and streamline your administrative workflows.