Error: MigrationPermanentException: Active Directory property ’homeMDB’ is not writeable on recipient for particular mailbox could be one of the error you may face while migrating your on-premise mailbox to Office 365 Exchange online. Recently I came across the similar issue on the Hybrid Exchange setup with Exchange 2007 and Office 365 cloud I was working. Surprisingly, this happened to certain users only.
The main reason for this error is permission of particular user account on the domain. Wrong or missing user permission of the account is stopping the Exchange command to move the mailbox from on-premise Exchange servers to Office 365 online. Here is the way to solve Error: MigrationPermanentException: Active Directory property ’homeMDB’ is not writeable on recipient account error.
We need to enable the inheritance of permission for the particular Active Directory account.
1) To enable the required security permission for AD user, we must see the security tab in Active Directory Users list. Open Active Directory users and computers on your domain controller and change the view to Advanced Features as below.
Now you should be seeing the security tab for the users and computers.
2) Open the user account which gives the error while migrating to Office 365. Under ‘Security’ tab (this will be visible when you enable Advanced View as mentioned in step 1), click on ‘Advanced’ button. Mostly the inheritance permission for this user would be disabled. Enabling this permission will solve the issue, click on ‘Enable inheritance’ button and apply the changes.
3) On hybrid setup, you should sync the change of user account to Office 365 through Azure AD Connect. If you can wait for the scheduled sync to happen, otherwise run the delta sync manually by the following command on the server where Azure AD sync tool installed.
Start-ADSyncSyncCycle -PolicyType Delta
Once this change synchronized to Office 365, you should be able to migrate the mailbox from on-premise Exchange server to Office 365 online without Active Directory property ’homeMDB’ error.