Various processes exist where service accounts need access. If not, migrating these can actually cause more problems. This needs to be done carefully and kept up-to-date.
This can be an Administrative Assistant having access to the people they support, colleagues covering for each other, or several other everyday use cases. Perhaps the second most common, and the use case that comes to mind more often, is simply just delegating access to someone. It should be noted that configurations provide access with an AD Group, Individual Users, or both. When conducting migrations, you need to test this process and ensure it is working correctly! This means that during a migration, when a Shared Account gets migrated, if the permissions are wrong, this will directly impact the organization’s ability to service customers. This is very common for work teams communicating with clients. It is not uncommon for organizations to have more Shared Mailboxes than people at the company. The most common Full Mailbox Permission use case is Shared Mailboxes. In the summary article on migrating Exchange Mailbox Permissions, we discussed that these are permissions set by the Administrator, which are not visible to the user. In this article, we will review these use cases and how they impact migrations. This includes both user-driven and administration-driven functions. There will be slight differences if you are running this against on-prem Exchange, but remember that you can also look at the AD attributes there (msExchDelegateListLink and msExchDelegateListBL).Full Office 365 Mailbox Permissions have several use cases. Name Alias Database ProhibitSendQuota ExternalDirectoryObjectId List all mailboxes to which a particular security principal has Send on behalf of permissions:
0 kommentar(er)
