Forum Discussion

Keith Caines's avatar
Keith Caines
Copper Contributor
Jan 09, 2018

Remove On Premises exchange Hybrid and go fully Online

Hello,   I currently have a scenario where there is a Hybrid Exchange environment with 1 server. All my mailboxes have been migrated online.   I would like to completely remove dependency on ...
exchange
hybrid
On-Premises
BrianSmith's avatar
BrianSmith
Copper Contributor
Mar 04, 2019
Deleted wrote:

 

The only reason why Microsoft recommends to keep 1 CAS server/Exchange Hybrid (Free version) is to keep MSexch attributes intact. Once you de-commission Exchange, it removes those attributes from AD as well. However since you have AD Connect sync running the source of authority for the synced objects is on-premise & without those attributes it becomes hard to manage objects at times. Not everyone is a pro when it comes to modifying objects using ADSIedit or PS.

My question to this is: what makes it any different than if I never had Exchange on-prem and started using Office 365? The Exchange attributes wouldn't be attached to the user objects anyway. If all maintenance is to be handled in the cloud, why are the on-prem Exchange attributes needed?

wroot's avatar
wroot
Silver Contributor
Mar 04, 2019
BrianSmith if you only create users in Office 365 (not syncing from local AD) then such requirement is not applied. But i guess there can be a scenario, that you use AD, never used Exchange and want to sync your AD users instead of creating them in Azure AD. I guess in that case you would have to install Exchange on-premise for such hybrid setup.

Resources