Thinking about how to decommission Exchange 2010 after Office 365 hybrid migration. Are you facing difficulty while migrating Exchange mailbox data to Exchange Online manually? Do not panic! This guide will describe the best and relevant approaches to decommission On-premises Exchange into Office 365. So, let’s get started!
When the Exchange users wish to use the service of Office 365, then they first go for the Office 365 Deployment. As it’s name suggest ‘hybrid’, it is the combination of cloud and On-premises. It provides the facility to use the Exchange Server with Exchange Online mailboxes. However, when the user or an organisation wants to completely move their mailboxes from On-premises to Exchange Online. In such an instance, hybrid deployment creates the problem such as getting error messages. As a result, users are unable to decommission Exchange after Migration to Office 365. In the upcoming section, users will know the reason why hybrid deployment is not a good option for the Exchange mailbox migration.
From the last few years, the growing popularity of MS O365 and its advanced feature attracts the most users. Also, Office 365 Hybrid Server gives the flexibility of gradual migration to Online but it is upto some extent. Because when it comes to full migration from On-premises to Office 365, hybrid deployment becomes cumbersome.
The reason behind is a requirement of minimum one On-premises hybrid server for user management. It is because of the presence of Active Directory Synchronization or DirSync. It is a part of the pre-requisite that is mandatory to deploy a hybrid process. Its work is to make a copy of local On-premises directory and then communicate into cloud tenant. So, when the DirSync (or Directory Synchronization) is enabled, most of the actions or task is managed from on-premises instead from O365. That is why organizations cannot remove on-premises mailboxes completely and move into Office 365 after hybrid migration.
Well! After understanding the reasons, let’s look at the approaches that help the users to remove Exchange 2013, 2010 from hybrid configuration.
This workaround is helpful for those users who already move all the important On-premises mailboxes to Exchange Online. Now, they do not want to keep AD synchronization for user management on On-premises. So, follow this method to disable DirSync
1. To start the process, you need to run the following command:
Get-OrganizationConfig | f1 PublicFoldersEnabled
Note: If the above-mentioned cmdlet is set up to Remote, then use batch migration process to move Public folder in MS Office 365 account.
2. Next, ensure that MX and Autodiscover DNS record are set for Office 365 Exchange Online rather than local hybrid server.
3. After that, you need to eliminate the SCP (Service Connection Point) values from the On-premises Exchange Server. This action ensures that you are using DNS record for AutoDiscover. Use the following command to remove SCP.
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri $Null
4. In the MS Office 365 Admin portal, go to Admin Centers > > Exchange.
5. In EAC, click on mail flow option and then select connectors. Here, you can disable the inbound/outbound connectors that were used for hybrid deployment process. Ensure that the connectors that used currently are not deleted.
6. In order to delete the On-premises Exchange relationship, follow the below instructions
7. After that, if you configured Exchange Hybrid with OAuth, then you have to disable it from Office 365 and local Exchange environment too. To do this, follow the below steps:
Get-IntraorganizationConnector -Identity ExchangeHybridOnPremisesToOnline | Set-IntraOrganizationConnector -Enabled $False
Run Get-IntraorganizationConnector -Identity ExchangeHybridOnlineToOnPremises | Set-IntraOrganizationConnector -Enabled $False
8. Finally, you can disable Directory Synchronization from the Exchange Online tenants. Now, On-premises Exchange Server is decommissioned
Is it worth to follow a long- step procedure to migrate from On-premises Exchange to Office 365? For the organizations, time is calculated as a money. In such an instance, deploy such a complex method is not beneficial. Moreover, depending on the Exchange Server edition, the steps to complete migration manually also changes. Adding to it, any single mistake of a comma in PowerShell command results in data loss issues. So, it is better to choose a solution that is reliable and automated instead of a complex one.
One such software is Exchange to Office 365 Migration that successfully import On-premises mailbox data to Exchange Online tenant. Also, users can move unlimited size of mailboxes to Office 365. It provides the facility to extract all Exchange mailbox data such as emails, contacts and more and directly exports it to Office 365 account. Above all, it is easy to use interface makes the entire process so facile even a naive user can easily operate it.
Due to the advanced functionality of Office 365, many enterprises moving towards it. However, users face problem while completely decommission On-premises Exchange Server after hybrid migration because of DirSync. Therefore, in this post, we have discussed the most appropriate method to remove Exchange Server after hybrid deployment. If an organization wants to directly import all the mailboxes of Exchange 2007, 2010, 2013, 2016, then click on On-premise to Office 365 Migrator. It is the smartest way to import the mailbox data into Exchange Online mailboxes