Forum Discussion
Remove On Premises exchange Hybrid and go fully Online
Everything you need to know right here ..
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx
If you have removed Azure AD Connect then you can remove on-premise Exchange. It's the presence of this component that would necessitate keeping an on-premise Exchange Server for mailbox management
Sorry Ian, but that is incorrect. We ourselves, as well as the majority of our clients, run Azure AD Connect WITHOUT an on premise exchange server.
I use AD to create users inside my Active Directory for old LAN drives (shares) and local printers. I set their password there -
I then use Office 365 to provision and maintain their mailboxes without issue.
Under what scenario/functionality are you thinking a local Exchange Server is required?
Joe Wichowski Hi Joe, Thanks for your clear information. I am trying to get to your solution. I have got all my mailboxes moved, found all the funny SMTP connectors for devices, got al my DNS pointing to O365, nothing is happening on the onprem server.
I have tested everything ana as you say creating a local user works fine and they can get a mailbox once they are synched to the O365. If I chose not to sync a user that does not need a mailbox it can exsist locally (for managing a device say)
I have the latest AAD connect which has options for Hybrid exchange and Public folders selected.
I ma trying to acertain the order for removing stuff (the Exchange option in AAD Connect, the Exchange Hybrid stuff, and the on prem server), and ideas?
- I am trying to remove Exchange Hybrid but keep the Azure AD connect. The latest version has options for Exchange Hybrid and Public Folders. If I uncheck them does that mean that the Exchange attributes are no longer synched, so I cna them remove the hybrid organization then uninstall Exchange on prem?
Well, the main scenario that springs to mind is that removing the last Exchange server puts you in an unsupported environment ..
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx
Of course you can use tools such as adsiedit etc to modify Exchange attributes of your local accounts prior to sync - but again, unsupported.
If you are still using Azure AD Connect to sync your accounts to the cloud then the only supported way to manage recipients is with a local Exchange Server. That may change but to my knowledge that hasn't happened - yet.
I'm sorry - still not seeing it. It says "not recommended" - can you explain the part where it is actually "required"?
Or more importantly - are you saying that I cannot change the email address for a user from Active Directory console or add an alias (which I can)? Or update their manager, or address, or title? (Which I can)
I'm trying to find someone from Pernille-Eskebo.com that says it's not supported. But everything I read, its a MVP or someone not from the company saying it's a requirement. Should be easy to find in official documents no? Alas - there is nothing about it in AD Connect pre-requisites, and Microsoft only says its required "during hybrid" but I have yet to see an actual document state its required even after your hybrid deployment is complete.
Happy to be wrong - I just haven't seen it yet -
