• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 120
  • Last Modified:

Exchange 2013 decommission post migration to Office 365

I want to decommission our Exchange 2013 platform which we have in Office 365 Azure AD sync environment, we had a DAG set-up and now down to single Exchange 2013, this is post cut over migration to Office 365 (we used CodwTwo), we want to neatly clean and remove Exchange 2013 without deleting users etc..  I can't find any real documentation for this, quite mixed opinions as some suggest to leave Exchange in existing cloud.

Is there a process to do this cleanly?  We have Azure AD Sync in place and all working 100%, just need to remove Exchange cleanly.

3 Solutions
Jason CrawfordTransport NinjaCommented:
I'm not familiar with CodeTwo, but if you performed a Cutover Migration to Exchange Online you wouldn't be syncing your on-prem AD unless you maybe configured Office 365 Azure AD Sync post-migration?  Can you clarify?
Jason CrawfordTransport NinjaCommented:
Regardless, if you're syncing AD I've always been on the opinion it is best to leave the last Exchange server on-prem so you can continue to manage mail attributes in AD (2010 but same concepts apply):


Most of the time the reason for most organizations that have configured a hybrid deployment, removing the last Exchange server from the on-premises environment will have adverse effects. In most cases, we recommend that you leave at least one Exchange 2010 Server on-premises for mailbox management unless you are getting rid of the on-premises messaging and identity management dependencies all together.
Todd NelsonSystems EngineerCommented:
Here are a few references, directly from MS and MVPs.  The key to being able to remove Exchange from on premises is directory synchronization.  If you plan on keeping AAD Connect (which determines your source of authority as on premises), to remain supported you must keep at least one Exchange server on premises.

If you want to remove Exchange, 1) get rid of AAD Connect, 2) disable directory sync in O365, 3) remove Exchange, and then 4) get comfortable with managing identities in two locations.

P.S. In the MVA course, pay very close attention to the Hybrid Best Practices. Also, read all comments in the last reference.
Sandeep KumarAssociate ConsultantCommented:
Refer to below discussions for Decommissioning Exchange Server post migration for 'to neatly clean and remove Exchange 2013 without deleting users' query.

PberSolutions ArchitectCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- Jason Crawford (https:#a42418587)
-- Todd Nelson (https:#a42418859)
-- Sandeep Kumar (https:#a42421202)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now