When you try to add a delegate in Outlook and grant them Send on Behalf permission, you may see an error message or the delegate simply does not appear in the list. This problem usually occurs because of permission conflicts, Active Directory replication delays, or corrupted Outlook profiles. This article explains the root causes of this failure and provides step-by-step fixes to restore delegate functionality.
Key Takeaways: Fixing Delegate Send on Behalf Permissions
- File > Account Settings > Delegate Access > Remove existing delegate: Clears corrupted permission entries before re-adding the delegate.
- Exchange Admin Center > Mailboxes > Delegation: Manually grant Send on Behalf permissions from the server side when Outlook fails.
- Outlook.exe /cleanreminders or /resetfolders: Command-line switches that repair delegate-related data in the Outlook profile.
Why Outlook Fails to Add a Delegate With Send on Behalf Permission
The Send on Behalf permission requires both the mailbox owner and the delegate to have valid Exchange Online or on-premises Exchange mailboxes. When Outlook cannot add a delegate, the most common root cause is a corrupted delegate permission entry that prevents the new assignment from being saved. Other causes include:
- Active Directory replication delay: After a delegate is added or removed in Exchange Admin Center, the change may take 15 to 60 minutes to propagate to all domain controllers. Outlook may still see the old state.
- Outlook profile corruption: A damaged profile can block delegate modifications even when the server settings are correct.
- Permission conflicts: If the delegate already has Editor or Reviewer permissions on the mailbox, Outlook may refuse to add Send on Behalf on top of existing rights.
- Licensing issues: Both the manager and delegate must have an Exchange Online license (Plan 1 or higher) for delegate features to work.
In many cases, the error message is generic, such as “The delegate could not be added” or “Cannot save changes to delegate settings.” The fixes below address each of these root causes.
Steps to Fix Delegate Send on Behalf Permission Errors
Method 1: Remove and Re-Add the Delegate in Outlook
- Open Delegate Access settings
In Outlook, go to File > Account Settings > Delegate Access. If you have multiple accounts, select the correct mailbox from the drop-down list. - Remove the existing delegate entry
Select the delegate name that is causing the error and click Remove. Confirm the removal. Close the Delegate Access dialog. - Restart Outlook
Close and reopen Outlook to clear cached delegate data from the profile. - Add the delegate again
Return to File > Account Settings > Delegate Access. Click Add, search for the delegate, and select their name. In the Delegate Permissions dialog, set the appropriate folder permissions. For Send on Behalf, check the box Editor for the Calendar folder and any other folders the delegate needs. The Send on Behalf permission is automatically granted when you add a delegate with Editor-level access on the Calendar. - Verify Send on Behalf
Click OK twice to save. Send a test email to yourself and check that the delegate can send on your behalf using the From field.
Method 2: Grant Send on Behalf Permission via Exchange Admin Center
If the Outlook method fails, assign the permission directly on the Exchange server. This bypasses Outlook profile issues.
- Sign in to Exchange Admin Center
Go to https://admin.exchange.microsoft.com and sign in with your global admin or Exchange admin credentials. - Open the mailbox of the manager
Navigate to Recipients > Mailboxes. Search for the manager’s mailbox and click to open its properties. - Go to Mailbox delegation
In the left pane, click Mailbox delegation. Under Send on Behalf, click Manage delegation. - Add the delegate
Click Add users, search for the delegate, select them, and click Add. Click Confirm and then Save. - Wait for replication and test
Allow up to 60 minutes for the change to replicate. In Outlook, the delegate should now appear in the Address Book with Send on Behalf rights. Test by composing a new email and selecting the manager’s name in the From field.
Method 3: Repair the Outlook Profile Using Command-Line Switches
- Close Outlook
Ensure Outlook is not running. - Run Outlook with the cleanreminders switch
Press Windows Key + R, typeoutlook.exe /cleanreminders, and press Enter. This switch removes corrupted reminder and delegate data from the profile. - Run Outlook with the resetfolders switch (if needed)
If the delegate issue persists, close Outlook again and runoutlook.exe /resetfolders. This restores default folder views and permissions for the profile. - Test delegate permissions
After Outlook opens, try adding the delegate again using Method 1.
If Outlook Still Has Issues After the Main Fix
Outlook shows “You do not have sufficient permission to perform this operation”
This error occurs when the delegate’s mailbox is in a different Exchange organization or when the manager’s mailbox is hidden from the address list. Verify that both mailboxes are in the same Exchange environment and that the manager’s mailbox is visible in the Global Address List. In Exchange Admin Center, go to Recipients > Mailboxes, select the manager’s mailbox, and under Mailbox features, ensure Hide from address lists is unchecked.
Delegate can send on behalf but cannot see the manager’s calendar
Send on Behalf permission does not automatically grant folder visibility. The delegate must also have at least Reviewer permission on the manager’s Calendar folder. In Outlook, go to File > Account Settings > Delegate Access, select the delegate, click Permissions, and set Calendar to Reviewer (or higher). Click OK and test again.
Changes to delegate permissions do not apply to Outlook for Mac
Outlook for Mac does not support delegate management from within the app. All delegate changes must be made in Outlook for Windows or Exchange Admin Center. After making the change on the server, the Mac user must restart Outlook to see the updated permissions.
Outlook Delegate Permissions vs Send on Behalf: Key Differences
| Item | Send on Behalf | Send As |
|---|---|---|
| Permission type | Delegate permission | Mailbox permission |
| Recipient sees | “Delegate Name on behalf of Manager Name” | Only “Manager Name” |
| Granted via | Outlook Delegate Access or Exchange Admin Center | Exchange Admin Center or PowerShell |
| Typical use case | Assistant sends meeting requests for a manager | Shared mailbox where multiple users send as the mailbox |
| Minimum folder permission required | Editor on Calendar | None required |
When you configure a delegate in Outlook, the Send on Behalf permission is automatically granted if you set the Calendar folder to Editor level. If you need the delegate to send as the manager without the “on behalf of” tag, you must assign the Send As permission separately in Exchange Admin Center or via the Add-MailboxPermission PowerShell cmdlet.
After following the steps in this article, you can successfully add a delegate with Send on Behalf permission in Outlook. Start by removing and re-adding the delegate to clear corrupted entries. If Outlook still fails, use Exchange Admin Center to assign the permission directly. For persistent profile problems, run Outlook with the /cleanreminders switch. To avoid future issues, always verify that both mailboxes are in the same Exchange organization and that the manager’s mailbox is visible in the Global Address List.