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/
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?
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 :)