It has been a while since we blogged about the ability to control the behavior of Sent Items for shared mailboxes when users either send as or on behalf of shared mailboxes. Today, we are glad to share with you that this feature is currently rolling out for User mailboxes also! What does that mean in real life?
Let’s say you have the following scenario:
- Mary is a delegator/manager on the team
- Rob is a delegate on Mary’s mailbox; Rob has Send As or Send on behalf of rights on Mary’s mailbox.
- When Rob sends an email as Mary, the email will be only in Rob’s Sent Items folder
With this feature enabled on Mary’s mailbox, Exchange will copy the message that Rob sends as Mary to the Sent Items folder in Mary’s mailbox. In other words, both Rob and Mary will have the message in their Sent Items folders.
We have heard this request more than once, and now we are rolling it out to an Exchange Online mailbox near you! The configuration and behavior of the feature is the same as for the shared mailbox.
Note: If the user has used the Outlook 2013 feature to change the folder that Sent Items are saved to, the messages will be copied to that folder instead of the user’s Sent Items folder. Users can reconfigure this by clicking the Save Sent Items To button on the Email Options tab.
Enable message copySent On Behalf of the delegatorFor emails Sent On Behalf of the delegator:
Set-Mailbox <delegator mailbox name> -MessageCopyForSendOnBehalfEnabled $true
Disable message copySent On Behalf of the delegatorFor emails Sent On Behalf of the delegator:
Set-Mailbox <delegator mailbox name> -MessageCopyForSendOnBehalfEnabled $false
|To...||For messages...||Use this command...|
|Enable message copy||Sent As the delegator||
Set-Mailbox <delegator mailbox name> -MessageCopyForSentAsEnabled $true
|Disable message copy||Sent As the delegator||
Set-Mailbox <delegator mailbox name> -MessageCopyForSentAsEnabled $false
Note, you can use the Office 365 Portal to configure this for shared mailboxes, but to configure user mailboxes, you'll need to use PowerShell (the team would like to hear if you feel it should be in the Portal too!). For various other details of behavior please see the shared mailbox post.
Next question that some might have is: What about on-premises?
Update 4/17/2016: As it stands right now, we plan to release this feature as a part of the Exchange 2016 CU6 release.