Decommissioning Exchange Hybrid

Updated on 8 July 2015

Decommissioning Exchange hybrid deployments have come up as a topic of discussion a lot recently. For management and continuity purposes, I recommend that it not be done. However, I do understand that customers have specific requests and needs. Essentially, it comes down to a few scenarios…

  1. Whether the customer has no need to manage users from on premise;
  2. Whether the customer wants to continue to managing users from on premise; or
  3. Whether the customer has need for an SMTP relay server.

These two references (from Microsoft) outline the specific use cases on whether or not to decommission an Exchange hybrid deployment…

NOTE: Customers with a hybrid configuration often find after a period of time that all of their mailboxes have been moved to Exchange Online. At this point, they may decide to remove the Exchange servers from on-premises. However, they discover that they can no longer manage their cloud mailboxes.  When directory synchronization is enabled for a tenant and a user is synchronized from on-premises, most of the attributes cannot be managed from Exchange Online and must be managed from on-premises. This is not due to the hybrid configuration, but it occurs because of directory synchronization. In addition, even if you have directory synchronization in place without running the Hybrid Configuration Wizard, you still cannot manage most of the recipient tasks from the cloud.

Good luck and have fun!

 

Related Articles in this Blog:

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s