This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 44%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Hello,
I'm having issues with migrating a particular user from Exchange on prem up into Exchange Online.
A couple of weeks ago our IT helpdesk assigned this on prem user an Exchange Online license to their O365 account by mistake, and ever since the license was removed there have been issues.
Namely, the user does not appear in the Exchange Online GAL any more - all other on prem users do.
The user cannot be emailed anymore from and Exchange online user.
Having looked into this, I ran the following command to remove any remnants of the erroneous EO mailbox from the users O365 account
Set-User onpremuser@keyman .com -PermanentlyClearPreviousMailboxInfo
Checking the account afterwards, all looks good to me
Get-User onpremuser@keyman .com | Select-Object Name,Recipient
Name PreviousRecipientTypeDetails RecipientType RecipientTypeDetails
---- ---------------------------- ------------- --------------------
onpremuser None User User
Having then tried to set up a migration job for the user to move the mailbox to Exchange online, the batch fails with the following error:
"A recipient wasn't found for "onpremuser@keyman .com" on the target. Create a recipient of the appropriate type for this migration on the target and try again."
So how do you migrate an on prem mailbox in this situation, if assigning an EO license (which I'm assuming is what would create the missing recipient) would then stop the user accessing their on prem mailbox - as was the case originally?
Thanks
OK, it looks like AAD Sync is not triggering the recreation the "Mail User" object for the on prem mailbox user - and I have no idea why.
Anyone come across this before?
Hi Matt,
Check the AAD Connect Sync and look for the user in the metaverse if it is imported in the Connector space. check that user is part of the OU that is sync to the AAD.
Hi Jimmy,
Not sure how to check the user in the Connector space - can you advise?
I am guessing there is an attribute with an incorrect value that has not been cleared/reset on the AD account when the online mailbox was deleted?
Hi Matt,
Check this link for troubleshooting sync issues, very useful to understand the process of CS and MV and how AAD Connect works.
tshoot-connect-object-not-syncing
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
I check in my lab, the synced AD account show as "MailUser" type in "Get-User" command.
So, I would suggest you move this AD account from a sync OU to an unsynchronized OU. Check whether the AAD account disappear.
The remove the 'msExchMailboxGuid' and 'targetAddress' value from this AD account (Backup it first) , after that move back to sync OU and sync again.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Still the same I'm afraid.
Created a new OU, unchecked it AAD Connect
Moved the user to it, synced AAD Connect - user removed from O365 Admin Centre
Removed msExchMailboxGuid (targetAddress not set - nothing to remove?)
Exchange on prem reporting that user is now corrupted (no mbxGuid)
Moved user back to home OU, resynced AAD Connect.
re-added msExchMailboxGuid to AD account on prem, resynced
User re-added to O365 (all previous license assignments still intact), "Mail" tab in O365 still states:
all previous license assignments still intact
Do you mean that you assign license back to this synced account?
How this mailbox show on Exchange on-premises? What is this result for command below:
Get-Mailbox ThisUser | fl PrimarySmtpAddress
Do you mean that you assign license back to this synced account?
No - licenses reassigned automatically - or not unassigned in the first instance
How this mailbox show on Exchange on-premises? What is this result for command below:
User on-prem email address as expected
When a user is created on-premises and synced to Office 365. E1/E3 license assigned which auto-creates a mailbox. Then you create it on on-premises and try to migrate it and you're stuck. If it's a new user, you could just delete the Office 365 user and remove this user from the recycle bin. It will get recreated next sync and then you can migrate the mailbox and assign a license.
There is no "MailUser" object in Exchange Online so the user cannot be migrated
Still investigating this issue.
All attributes synced by AAD Connect look good to me having looked at the article @JimmySalian-2011 shared - https://learn.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-object-not-syncing - thanks
One thing I have noticed when checking the users account in O365 is that there is a legacy value in the sign in field when Get-MsolUser is run, that doesn't match the UPN.
Two questions:
Get-MsolUser -UserPrincipalName User@keyman .com | fl UserP*,Sign*
UserPrincipalName: User@keyman .com
SignInName : User@legacydomain.com
I can find no reference to User@legacydomain.com in the attributes synced to AAD
The user is sure that Sign in name hasn't been used for years.
The legacy domain does still exist however as an accepted domain associated with a completely separate Azure tenant to the one I'm working with.
Did you check the logon email address and proxy addresses on the local AD? Whether this email address exist on it?
Yes.
I have raised a support case with Microsoft. Their backend team are looking at the issue currently.
I will post an update once I have one
This has been resolved after several weeks of troubleshooting with MS Support.
As a last resort the user account needed to be permanently deleted in AAD and O365, then re-synced via AAD Connect.
Following this, the MailUser object was successfully created in Exchange Online