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)
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?
Re-Adding users (not groups) to the list of users having FullAccess permission will add AutoMapping to those users. Using PowerShell gives you the ability to enabled/disable AutoMapping per user added to the list of users having full access. AutoMapping is enabled/disabled for each user added to the list of users having full access. It is not controlled for the mailbox providing access to.
-Thomas
So, to be clear, re-adding a sec group to the Full Access list, in GUI or Powershell, will not grant users of that group Automapping? Is this different on more recent versions of Exchange (2016 and/or O365)?
If no, is there any way to automap users that have access to a mailbox via their group membership?Thank you for your time.
