How to disconnect a mailbox & re-assign it to new user in a Hybrid Scenario

How to disconnect a mailbox & re-assign it to new user in a Hybrid Scenario

Scenario objectives: We have an Exchange Hybrid setup between on-premises and Exchange Online (Office 365). All users are synced and the mailbox is located at Exchange Online.

We need to separate an existing mailbox from its user account and re-connect this mailbox to a new user account. If the mailbox in this scenario was located at the on-premises Exchange it would be an easy process just using the Exchange Management Console. But in a Hybrid scenario, the process includes many steps since the mailbox is not directory conencted to the Active Directory user account but it is conected to the Azure AD Synced User Account.

For the ease of the guide we will name the Existing User Account: OLDUSER and the New User Account: NEWUSER.

We will disconnect the Exchange Online Mailbox from the OLDUSER and connect it to the NEWUSER.

Step 1.

At the on-premises Active Directory, at an OU that is not synced with Azure AD, create the new user account. The “NEWUSER”. Ensure that you do not enter nothing at the email field. Just a user account with no email attributes.

Step 2.

Move the “OLDUSER” to an OU that is not synced with Azure AD

Step 3.

Run a Delta Sync. Go to the server that the AD Connect is installed, open the PowerShell and run “Start-ADSyncSyncCycle”

Step 4.

We need to get the GUID of the NEWUSER. To do so login to a Domain Controller, open PowerShell and run:

Copy the GUID to a Notepad

Step 5.

Open the Office 365 Admin Center and Restore the deleted user “OLDUSER”

Go to Users –> Deleted Users –> Select the user “OLDUSER” –>Click Restore

Step 6.

Connect to Azure AD and set the GUID of the “NEWUSER” to the Office 365 “OLD USER”. Details for connecting to Azure AD “https://technet.microsoft.com/en-us/library/dn975125.aspx

Step 5.

Open the Office 365 Admin Center and Delete the old user “OLDUSER”

Go to Users –> Active users –> Select the “OLDUSER” –> click Delete user

Step 6.

Clean the on-premises Active Directory account of the old user “OLDUSER” from all attributes that will be added to the new user, like Proxy addresses, Target, address, Alias name, nickname etc.

Step 7.

Make the “NEWUSER” user account a Remote Mailbox object

At the on-premises Exchange, open the Exchange Management Shell and run:

Step 8.

Move the “NEWUSER” to an OU that is Synced with Azure AD and run a Delta Sync like Step 3.

After that the “NEWUSER” active directory account will be connected with the “OLDUSER” Exchange Online mailbox and all attributes of the Exchange Online mailbox will be replaced with the “NEWUSER’s” values.

 

I suppose there are other ways, maybe easier, to accomplish this task, but following this process you will have the desired result without problems.

Share

3 comments

  1. Hi Pantelis,

    thanks for the info… I was wondering, if I want to REPLACE my AD completely, i.e. have OLD AD syncing with O365, create NEW AD servers, do I just shutdown the old AD, create the new users and then Connect to Azure AD and set the GUID of the “NEWUSER” to the Office 365 “OLD USER” using:
    Set-MsolUser -UserPrincipalName [email protected] -ImmutableId vMZGJpW6CUGY09bduJ5dlw==
    and then in O365 delete the OLD USERS, then SYNC my NEW AD to O365?

    Thanks,
    Stefan

    1. You don’t need to delete the old O365 users.
      1. create the new AD
      2. add the immutableid from local AD to Office 365 (Azure AD)
      3. add the ExchangeGUID from Exchange Online mailbox to the local AD user
      4. sync and the new local AD Users will connect with the old O365 users.

  2. Hi,
    My situation is this.

    A users account was deleted in AD so I restored the mailbox to “cloud only”

    I recovered the old AD account and now they are showing as 2 seperate accounts within the O365 console.

    We are on a federated domain so had to change the UPN to @domain.onmicrosoft.com before trying to set the immutable.

    Still, when trying to set it I am getting this:
    set-msoluser : Uniqueness violation. Property: SourceAnchor.

    Any ideas?

    Thanks

Leave a Reply