Shared mailbox: Use send-as, not send on behalf from Outlook 2016
Hello,
We have a lot of shared mailboxes. For every shared mailbox, we create a specific security group that contains the members who should have access to that particular shared mailbox.
We give full mailbox permissions and send-as permissions for that particular security group onto the shared mailbox.
For example, security group A has full mailbox access and send-as permissions onto shared mailbox A. By adding users to security group A, they have full access to the shared mailbox.
We create every new shared mailbox/security group combo using Powershell. That has been working flawlessly for the last years.
However, for a recent new shared mailbox/security group combination, when a user that's member of the related security group wants to send an e-mail from the shared mailbox (by changing the from field in Outlook and selecting the shared mailbox from the global address list), Outlook tries to send every time 'send-on behalf'. This only happens for that newly created mailbox.
I compared the output of Get-Mailbox and Get-RecipientPermission for the new problem shared mailbox and an older shared mailbox (which enable users to send mail send-as from outlook just fine) but I couldn't find any differences.
For your information, that's the error we get back immediately after trying to do a send-as for the new shared mailbox:
Your message did not reach some or all of the intended recipients.
Subject: Test from Outlook
Sent: 23/11/2017 9:27
The following recipient(s) cannot be reached:
name of sending user on 23/11/2017 9:27
This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524].
Why does Outlook always tries to do a send on behalf (what we don't want) where else for other shared mailboxes, send-as works fine?
Using send-as from OWA however works just fine for the newest shared mailbox. It only seems a problem related to Outlook (tested on multiple clients that have access to the shared mailbox) and that particular new shared mailbox.
Thanks in advance.
The behavior depends on how you've added the shared mailbox in Outlook (automapped vs additional account), and of course by the method you use to compose the message. Check my ramblings on the topic here: https://www.michev.info/Blog/Post/1430/