Forum Discussion
AutoMapping Shared Mailbox based on security group
- Automapping works via the user who is granted permissions being stamped on the msExchDelegateLinkList attribute of the target object. This attribute only lists mail objects and not groups. No change with 2016 (or O365, which runs a version of 2016 at the moment)
Quite possibly the biggest problem an IT team that deals with Exchange has to contend with in a very large organisation. Assigning individual users to shared mailboxes is a bit of nightmare for tracking who has access to what, its odd that Microsoft would create a feature designed to streamline but then chose to neuter it by tying it to a highly work intensive task.
Imagine an Exchange system with 8,000 users and a couple of hundred shared mailboxes. If enough people asked nicely they may finally make Automapping work with Security Groups, that would be a dream come true.
Hi to all,
I have done this in past week in a customer and have worked:
- Create a Security (Mail Enabled) Group
- Add Members to that group
- Create a Mailbox and gave full access to the Security Group
Auto mapping have worked without any problems and you have a group based permissions that is used to distribute email and have access to a shared mailbox and the same security group have access to a SharePoint site.
You are right, however, Automapping works for all users in a group only when granting access the group for the first time to the shared mailbox, the issue is when adding a new user to the group, automapping won't work for any new user. :(
Would removing FullAccess permissions and re-adding via Powershell cause newly added members to get Auto-mapping? Or does it only work on the initial adding of permission to the shared mailbox?
- Hi Nuno!
Can you share which version of exchange this is?
I'm having the same problem with exchange 2010. My security groups are not mail enabled.Hi Kari,
It was on Exchange 2016 and on Office 365.
I suggest you to upgrade to Exchange 2016 or migrate to Office 365.
