ITGURU Posted May 21, 2022 Posted May 21, 2022 I'm currently migrating mailboxes from local exchange to office 365. Imported csv file of mailboxes from exchange to do initial sync. I have 17 mailboxes which won't sync due to the error below: I've ran powershell on the exchange server for 2 accounts as shown below - the one on the left gives me the above error message. The one on the right has synchronised successfully. There is no domain listed which isnt accepted as both accounts have the same domains... Please can anyone help? thanks
CrootUK Posted May 21, 2022 Posted May 21, 2022 Have you ensured all the accounts not working don’t have any traces of .local set as upn suffix/email/proxy address?
ITGURU Posted May 21, 2022 Author Posted May 21, 2022 Have you ensured all the accounts not working don’t have any traces of .local set as upn suffix/email/proxy address? The accounts have the UPN as the full public domain name/email address in AD If i look in local Exchange ECP and open both accounts (a working and non working) i see all the same domains shown on each account as per the screenshot above of the 2 accounts.. Where else should i look for any differences?
CrootUK Posted May 21, 2022 Posted May 21, 2022 For sanity. Email field in AD on general tab of user. Proxy addresses in attribute editor of the user These both same between working and failed?
ITGURU Posted May 21, 2022 Author Posted May 21, 2022 For sanity. Email field in AD on general tab of user. Proxy addresses in attribute editor of the user These both same between working and failed? Yes just check - email field in AD shows correct public domain and attribute editor shows same addresses as the screenshot above. Guess will be a case with MS 1
chaplic Posted May 22, 2022 Posted May 22, 2022 .local addresses cannot exist on the internet thus cannot exist in O365. However, if you license the account before you migrate it, it will ignore unvalidated domains. My guess is the right hand domains have a license already.
ITGURU Posted May 22, 2022 Author Posted May 22, 2022 (edited) Thank you. that was it. The user didn't have a license on 365 and has now synced without issue misleading error message Edited May 22, 2022 by ITGURU
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now