Dirsynced user not showing up as a Mail user in Office 365.
Hello,
We have an environment that has a on premise Exchange 2010 SP3 server. We have created the hybrid configuration with Office 365. Directory Synchronization is enabled.
At this point we have some on premise users that are showing "Synced with Active Directory" in the O365 portal, but do not have a mail user.
We are in the midst of performing a mailbox migrations to Office 365, and the only way to perform the move to Exchange online is for the user to have a Mail user setup in Contacts on the O365 portal.
Ive seen other forums with the option of Remove-MsolUser and removing from recycle bin then allowing another synchronization from on premise.
Ive also read that Microsoft has helped this situation by doing something to the AD Attributes which they do not go into detail about.
Could someone shed on some light to what could be done to add these users as Mail Users to Office 365 without removing them from Office 365 completely?
Thanks in advance!
We have an environment that has a on premise Exchange 2010 SP3 server. We have created the hybrid configuration with Office 365. Directory Synchronization is enabled.
At this point we have some on premise users that are showing "Synced with Active Directory" in the O365 portal, but do not have a mail user.
We are in the midst of performing a mailbox migrations to Office 365, and the only way to perform the move to Exchange online is for the user to have a Mail user setup in Contacts on the O365 portal.
Ive seen other forums with the option of Remove-MsolUser and removing from recycle bin then allowing another synchronization from on premise.
Ive also read that Microsoft has helped this situation by doing something to the AD Attributes which they do not go into detail about.
Could someone shed on some light to what could be done to add these users as Mail Users to Office 365 without removing them from Office 365 completely?
Thanks in advance!
ASKER
Gareth,
No sir. Their UPNs are set correctly.
No sir. Their UPNs are set correctly.
Most likely you are missing some attribute in the on-prem object. Off the top of my head, mail, displayname, targetaddress, proxyaddresses need to be populated.
Check here: http://social.technet.microsoft.com/wiki/contents/articles/19901.dirsync-list-of-attributes-that-are-synced-by-the-windows-azure-active-directory-sync-tool.aspx#How_directory_synchronization_determines_what_isn_t_synced_from_the_on-premises_environment_to_Windows_Azure_AD
Check here: http://social.technet.microsoft.com/wiki/contents/articles/19901.dirsync-list-of-attributes-that-are-synced-by-the-windows-azure-active-directory-sync-tool.aspx#How_directory_synchronization_determines_what_isn_t_synced_from_the_on-premises_environment_to_Windows_Azure_AD
ASKER
Thanks for the input Vasil
All attributes were set correctly before hand.
All attributes were set correctly before hand.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Only solution to solving this issue.
For the accounts that are missing is the UPN configured differently than the ones that are working?