-
Title
Hybrid migration to Office 365, mailbox rights such as Full Mailbox Access, Send As and Send on Behalf are not getting migrated -
Description
Hybrid migration has been set up. Source users are located in on-premises Active Directory and source mailboxes are in on-premises Exchange, users migrate to target Active Directory forest and mailboxes migrate to Office 365 using Quest Migration Manager. Microsoft Azure Active Directory Connect is set up to synchronize users from target on-premises AD to Office 365. Everything is working as expected, however mailbox rights such as Full Mailbox Access, Send As and Send on Behalf are not getting migrated.
Is there a way to migrate these rights?
-
Cause
As per Migration Manager documentation, it is strongly recommended to use only the Empty Active Directory to Microsoft Office 365 mapping template during migrating objects and synchronizing directories. If you need to process specific permissions such as Send on behalf, add the corresponding mapping rules to the template.
-
Resolution
1. In Quest Migration Manager for AD (Microsoft Office 365) console create a new static collection with problem users or use the existing collection2. Click Change near the "Schema template" field and select the "Empty Active Directory to Microsoft Office 365" template.3. Create Mapping Rules to synchronize full mailbox access and Send As permissions to Office 365. Click Add mapping rule.a. Target class: Userb. Target attribute: ExchangeSecurityDescriptorc. Action: Merge Withd. Source Class: usere. Source Attribute: msExchMailboxSecurityDescriptor4. Create another mapping rulea. Target class: Userb. Target attribute: ExchangeSecurityDescriptorc. Action: Merge Withd. Source Class: usere. Source Attribute: nTSecurityDescriptor5. Create another mapping rulea. Target class: Userb. Target attribute: GrantSendOnBehalfToc. Action: Merge Withd. Source Class: usere. Source Attribute: publicDelegates6. Migrate the users -
Additional Information
The procedure has been tested for use in hybrid migration scenario described in Problem Description part of this article, for other scenarios approach may vary. Please confirm the steps with Quest professional services representative before using in different migration scenarios.