Server Fault Asked by Oliver Giesen on February 25, 2021
I want to establish a shared mailbox for a project team. I want this mailbox to be auto-mapped into the team members’ Outlook profiles. However, I do not want them to have Full Access, so I can still control access permissions on individual folders inside that mailbox – for instance, to hide all the superfluous default folders they won’t need, but also to have different folder permissions for project leads and mere stakeholders.
For test purposes I already solved this on our on-premise Exchange Server:
Simply entering the DNs of the team members into the shared mailbox’s msExchDelegateListLink
attribute (via ADSIEdit) does the trick nicely and so far I haven’t discovered any downsides to that approach. However, as far as I can tell there is no way to access that attribute (or any attributes for that matter) in an Office365 environment…. or is there?
It is obviously already possible to have Full-Access permissions without auto-mapping via Add-MailboxPermission -AutoMapping:$false
, why can’t we have the opposite (which to me seems way more useful to begin with)?
I feel Ì must be missing something essential here: Why exactly is auto-mapping tied to Full Access in the first place? Is my use case really that outlandish? Are there other approaches for this that I simply haven’t thought of?
Agree with what joeqwerty has suggested. Automapping is an Exchange & Exchange Online feature, which automatically opens mailboxes with Full Access permissions in a delegate’s Outlook client. The tie between automapping and full access is designed by Microsoft.
By the way, based on your need, why don't you just share the folders? Use the Add-MailboxFolderPermission cmdlet to add folder-level permissions for users in mailboxes. For details, read this Add-MailboxFolderPermission
Answered by Beverly Gao on February 25, 2021
Why exactly is auto-mapping tied to Full Access in the first place?
Because that's how it was designed? Only Microsoft can answer that. Perhaps you can ask them.
Is my use case really that outlandish?
Not outlandish, but not the use case that shared mailboxes is intended to fit.
Are there other approaches for this that I simply haven't thought of?
Look into Office 365 Groups, or potentially Sharepoint document libraries. I'm not sure what the "right" solution is, but shared mailboxes isn't it.
Answered by joeqwerty on February 25, 2021
Get help from others!
Recent Questions
Recent Answers
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP