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/
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.
Have you read what Vasil has provided? If you sync on-premise AD users with dirsync/ad connect and you use Exchange Online (topic's author IS using Exchange, so it IS relevant here), how are you going to say add another alias or change current SMTP address or any other Exchange attribute of a user, so it would reflect in his/her EO mailbox? You have to do this on-premise. You can use AD Users console/PowerShell for that. But Microsoft might decline to provide you support, if you have no local Exchange server in such setup, because for now having local Exchange server when using hybrid setup is the only officially supported way (not technically, but from a support eligibility standpoint).
wrootDo you know how Microsoft defines "supported?" I do, because I worked there for 12 years. It is defined at "we have tested this and can therefore guarantee a certain level of outcome." Whenever said it was "unsupported" we still gave best effort. Oh and just an FYI, have several clients with NO onsite exchange server and they are able to sync passwords with AD, without issue. They also have no issue adding aliases, which is done in the cloud, where the mailbox resides.