Outlook Shared Mailbox Sent Items Save to Personal Mailbox: Fix

When you send an email from a shared mailbox in Outlook, the sent message often appears in your personal mailbox Sent Items folder instead of the shared mailbox Sent Items. This happens because Outlook by default saves sent items to the sending account, not the mailbox from which the message was sent. This article explains why this behavior occurs and provides step-by-step fixes to redirect sent items back to the shared mailbox.

The root cause involves a registry setting or a mailbox configuration that controls where sent messages are stored. Depending on your Outlook version and Exchange setup, the fix involves either a simple Outlook option, a registry change, or a PowerShell command from an administrator. This guide covers all three methods so you can choose the one that applies to your environment.

By the end of this article, you will be able to configure Outlook to save sent items directly to the shared mailbox Sent Items folder. You will also learn how to verify the fix and what to do if the problem persists after applying the changes.

Why Outlook Saves Shared Mailbox Sent Items to Your Personal Mailbox

Outlook treats each email account as an independent delivery point. When you send an email using the From field set to a shared mailbox address, Outlook still uses your primary mailbox as the sending account for the underlying transport. The default behavior in Outlook is to save a copy of every sent message in the Sent Items folder of the account that sent it — in this case, your personal mailbox.

This behavior is controlled by two settings. The first is the Outlook option Save copies of messages in Sent Items folder, which is enabled by default. The second is a registry value called DelegateSentItemsStyle that tells Outlook to save sent items in the mailbox from which the message was sent rather than the sending account. When both settings conflict, Outlook defaults to the personal mailbox.

In Exchange Online or on-premises Exchange environments, the server-side setting MessageCopyForSentAsEnabled can also override local Outlook behavior. If this property is set to $false, the server will not copy the sent item to the shared mailbox even if Outlook is configured correctly. This is why the fix sometimes requires administrator intervention.

Steps to Redirect Sent Items to the Shared Mailbox

Three methods exist to fix this issue. Choose the one that matches your access level and Outlook version.

Method 1: Change Outlook Options (Recommended for Most Users)

1. Open Outlook and go to File > Options
   In Outlook, click the File tab in the ribbon, then click Options in the left sidebar. This opens the Outlook Options dialog.
2. Select the Mail category
   In the left pane of the Options dialog, click Mail. This displays all mail-related settings.
3. Locate the Save messages section
   Scroll down to the Save messages section. Find the checkbox labeled Save copies of messages in Sent Items folder.
4. Uncheck the checkbox
   Clear the checkbox next to Save copies of messages in Sent Items folder. This tells Outlook not to save a copy in your personal Sent Items.
5. Click OK and restart Outlook
   Click OK to close the Options dialog. Close and reopen Outlook for the change to take effect. Send a test email from the shared mailbox. The sent message should now appear in the shared mailbox Sent Items folder.

Method 2: Add a Registry Entry (For Advanced Users)

If the Outlook option does not work, the registry method forces the behavior. This method applies to Outlook 2016, 2019, 2021, and Microsoft 365 versions.

1. Close Outlook
   Ensure Outlook is completely closed. Press Ctrl + Shift + Escape to open Task Manager and verify no Outlook processes are running.
2. Open Registry Editor
   Press Windows + R, type regedit, and press Enter. Click Yes in the User Account Control prompt.
3. Navigate to the Outlook Preferences key
   In Registry Editor, paste this path into the address bar:
   HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences
   Press Enter. The version number 16.0 applies to Outlook 2016 and later.
4. Create or modify the DelegateSentItemsStyle DWORD
   Right-click in the right pane, select New > DWORD (32-bit) Value. Name it DelegateSentItemsStyle. Double-click the new value, set Value data to 1, and click OK.
5. Close Registry Editor and restart Outlook
   Close Registry Editor. Open Outlook and send a test email from the shared mailbox. The sent item should now be saved in the shared mailbox Sent Items folder.

Method 3: Use Exchange PowerShell (For Administrators)

If the problem persists for multiple users, the Exchange server setting may be blocking the redirect. This method requires Exchange admin privileges.

1. Connect to Exchange Online PowerShell
   Open Windows PowerShell as administrator. Run Connect-ExchangeOnline and sign in with your admin credentials.
2. Check the current mailbox setting
   Run Get-Mailbox -Identity "SharedMailboxName" | fl MessageCopyForSentAsEnabled. Replace SharedMailboxName with the actual shared mailbox alias.
3. Enable the setting
   Run Set-Mailbox -Identity "SharedMailboxName" -MessageCopyForSentAsEnabled $true. This tells Exchange to copy sent items to the shared mailbox Sent Items folder.
4. Disconnect the session
   Run Disconnect-ExchangeOnline to close the remote session. Ask users to restart Outlook and test sending from the shared mailbox.

If Outlook Still Saves Sent Items to Your Personal Mailbox

Outlook cached mode prevents the change from applying

If you are using Outlook in Cached Exchange Mode, the local copy of the mailbox may not sync the change immediately. Wait 15 minutes or manually trigger a send/receive by pressing F9. If the problem continues, switch Outlook to Online Mode temporarily: go to File > Account Settings > Account Settings, select your Exchange account, click Change, and uncheck Use Cached Exchange Mode. Restart Outlook, test the fix, then re-enable cached mode.

The shared mailbox does not have a Sent Items folder

In rare cases, the shared mailbox may be missing the Sent Items folder due to a provisioning error. Have your Exchange administrator run Get-MailboxFolderStatistics -Identity "SharedMailboxName" | ft FolderType,FolderPath in PowerShell. If no Sent Items folder is listed, run New-MailboxFolder -Parent "SharedMailboxName":\ -Name "Sent Items" to create it.

Multiple shared mailboxes cause inconsistent behavior

If you have auto-mapped shared mailboxes, Outlook may apply the DelegateSentItemsStyle registry setting to only one mailbox. Add the registry key for each Outlook profile or set the Exchange server property for each shared mailbox individually using the PowerShell method above.

Outlook Option vs Registry vs PowerShell: Key Differences

Item	Outlook Option (Method 1)	Registry (Method 2)
User access required	Standard user	Local administrator on the PC
Persistence	Resets after Outlook reinstall or profile rebuild	Survives Outlook reinstall, not profile rebuild
Scope	Affects all accounts in the profile	Affects all shared mailboxes in the profile
Administrator needed	No	No
Works with Exchange Online	Yes, if server allows	Yes, if server allows

Method 3 (PowerShell) requires Exchange admin rights and applies to all users accessing that shared mailbox. It overrides both local methods.

After applying one of these fixes, test by sending an email from the shared mailbox and checking the shared mailbox Sent Items folder. If the message appears there, the fix is successful. For ongoing maintenance, monitor the DelegateSentItemsStyle registry key if you use roaming profiles, as it may need to be deployed via Group Policy. The PowerShell method is the most reliable for organizations with many shared mailboxes because it enforces the behavior at the server level.