Forum Discussion
Move from Staged Hybrid Migration to full Exchange Online
Every configuration involving dirsync, including password sync, requires you to keep an Exchange box for management purposes. Otherwise you will be in "unsupported" configuration. You dont have to follow the Microsoft recommendations on it, you can manage the objects just fine with other tools, but you riks being denied support.
Here's an example article that goes into more detail: https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises/
You cannot have both. You either manage the accounts directly in O365, which means no password sync, or use dirsync/password sync, but manage them on-premises. The latter also requires you to keep one Exchange box for management purposes, if you want to stay in "supported" scenario. If you don't care about that part, you can just manage them via ADUC/PowerShell/whatever.
I have AD Sync configured on on-premisis domain controller.
I did not realize that in order to syncronize passwords I would have to keep my exchange box around. Is this correct?
I want to completly decomission my exchange server. If this means that I lose the ability to sync passwords then so be it. Just seems strange.
Is there a way to easlily "enable" management from the Admin Portal?
Keith CainesActually, this is not longer the case. Because now there is ad connect. Ad Connect allows you to sync passwords only, without an exchange server.
Why are you reviving an old topic with redundant and somewhat misleading information? It was already stated, that you can use dirsync (ad connect is just a new version of that) without a local exchange server and using other tools to manage exchange properties, but this will be deemed as unsupported setup by MS support. So you do this at your own risk.
Ywroot You seem upset, how bout you take a chill pill. No one said ANYTHING about exchange properties. In fact, the whole point of the post was getting RID of exchange altogether. Doing this, have all of your exchange functions handled in O 365 and leave you with only syncing passwords with AD.
Every configuration involving dirsync, including password sync, requires you to keep an Exchange box for management purposes. Otherwise you will be in "unsupported" configuration. You dont have to follow the Microsoft recommendations on it, you can manage the objects just fine with other tools, but you riks being denied support.
Here's an example article that goes into more detail: https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises/
VasilMichev wrote:Every configuration involving dirsync, including password sync, requires you to keep an Exchange box for management purposes. Otherwise you will be in "unsupported" configuration. You dont have to follow the Microsoft recommendations on it, you can manage the objects just fine with other tools, but you riks being denied support.
Here's an example article that goes into more detail: https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises/
Thank you for sharing that thread. Wow. You were not kidding. I wonder why MS hasn't provided what seems to be a very simple solution to an obvious pain point!?
They're looking into it, at least that's the answer we get anytime we raise this topic :)
