Office 365 - Bodged user migration

[MatthewL]

I'm picking up the pieces to an issue where a user account migration has been bodged and in a semi working state. I'm have no access to 365 admin and I am been a middle man and also not done any migrations so all a bit new to me.

 

Currently running a hybrid setup, all users migrated to O365 no issues except this account due to it having been deleted in the past on the on-premise and then re-instated against another user account.

 

Que migration and all hell breaks loose, account ended up staying on premises. Account has been successfully migrated except some issues are haunting us.

 

Can login to the O365 portal and setup mobile phone to get email, Outlook fat client wouldn't work until i used username/email of [email protected] rather than [email protected], it wouldn't auto populate user details like others have so an issue there.

 

Outlook sorted, reshared calendar out and set permissions no issues, us other users can view the calendar in fat Outlook but unable to add to it like we should do, can do on O365 web portal. From what I can work out account has been created to match the AD account in O365 and the pair are not linked as such if that sounds right. I've found this article about SMTP matching, not sure if this or even this proxyAddress article is something we should be looking at.

 

Any help would be appreciated.

[Mako]

Currently running a hybrid setup, all users migrated to O365 no issues except this account due to it having been deleted in the past on the on-premise and then re-instated against another user account.

 

A new user account will have a new SID, so the SID of the account in O365 will be different. Times where I've had this, I've just deleted anything left hanging in O365 and started again, but if you don't have admin access then that'll be a problem.

 

You may be able to bodge it with adding the "correct" e-mail as a proxyAddress, which will then add the e-mail as an alias to the O365 account. But you'll be forever hitting migration issues as the accounts are different and changing the on-premises password may not sync across either.

 

Someone with more expertise in unpicking account and SID issues feel free to jump in and take over, but I think keeping the working on-premises account active and removing leftover stuff in O365 is the quickest option.

[MatthewL]

Thought as much.

 

If it was me I would just delete both accounts and start again, would export the mailbox pst and import in after the account is working. I'd quite happily do it but just don't have access and it can stay that way for my liking, I'm just stuck trying to help out!

[Mako]

What is it that's providing the barrier of not having O365 administrative access? If it's preventing you from doing your job then there's a good cause for it to be delegated to you.

 

Admin roles can be defined so as not to give you the whole shabang, but "User management administrator" would be exceptionally useful to you.

[MatthewL]

Don't even go there, that is another conversation for another day!