Remove requirement for onprem Exchange when using DirSync
as per : http://tinyurl.com/kqgjvqx
Currently for a small business who want password sync, but make the move to 365. they have to keep Exchange running on premise simply to be able to edit user attributes related to Exchange. - an active directory DLL, standalone app or simply support in the 365 portal would solve this for so many customers.
Anonymous
shared this idea
We’re working on a solution and will update you when we know more.
44 comments
-
Anonymous
commented
MS started this in 2015, we have been told multiple time that this is being looked at over multiple years. We are still waiting. The last update was a timeline to be released ..
"Update - we're still working on this, we expect to be able to update with a timeline in the next 3 months"
It is now mid September what is the status? Is there an update on anything here? How much longer would you like us to wait?
-
Thorsten Stiebig
commented
Hello, if the new tool for syncing the Exchange Attributes between on Premises and Exchange Online is ready for beta, I would like to test it.
-
Anonymous
commented
I was told on MS Ignite 2016 by Microsoft Exchange product specialists, that "we are working on it".... it is now August 2019, and nothing has changed yet….
-
Anonymous
commented
Much anticipated, by many SMB customers
-
Vic
commented
Glad to hear it started. Please update regularly
-
Jared Lambe
commented
Good to hear that it is started. Any more info? Do you need any beta testers?
-
Steve Whitcher
commented
Wow, I got the email that this was changed to Started, that's great! Of course, then I see that notes to that effect were posted in April, which I hadn't seen. And those notes say that there should be an update with a timeline in 3 months. So, I assume that has slipped since today's update has no mention of a timeline.
-
Anonymous
commented
Yay! That's great to Azure AD Team. Super excited to see what you guys come up with!
-
Julie
commented
Do you have an update on when this will work?
-
MSM
commented
Exchange is not actually required, only the Schema changes. It *might* be possible to use the Kerio Connect AD Extension to prep your AD Schema without actually having a running Kerio Connect mail server but consider that "theoretical" ;-)
-
We're working on a solution and will update you when we know more.
-
Rob de Jong (Azure AD IAM)
commented
Update - we're still working on this, we expect to be able to update with a timeline in the next 3 months
-
Hayden Greaves
commented
@Don: sure it is possible to maintain via extended schema attributes, but how many people want to remember exactly which attributes need to be altered (eg. proxyaddress for a simple alias addition, including remembering the syntax and caps vs lowercase SMTP) and then use ADUC in advanced mode, or ADSI edit for simple changes? And the question was specifically for SMB, so how many SMB teams are populated with experts that can be trusted not to break things when modifying AD object attributes? Finally, these standard BAU changes are usually a Lvl 1/2 support function - good luck training those staff with attribute-level changes as opposed to a UX-friendly GUI. Ok, you can script that I hear you say - but you can script anything, the question is why hasn't Microsoft just made simple and common BAU operations available without having to maintain an on-prem hybrid server for a management GUI? BTW, that isn't a whine, it's a pretty reasonable question.
-
Don
commented
For all whiners - stop whine and simply extend your schema! Exchange is not a requirement for Azure AD connect!!!! DO YOUR FREAKING HOMEWORK, after all, you're calling yourselves IT
-
Graham Ford
commented
It seems like this is even more important for the SMB given that the Essentials on Server 2019 won't have password synchronization. That was the only other supported option. Even for large orgs this would make much more sense than having to maintain an exchange server.
-
Ryan Morash
commented
No news on this front was made at Ignite (I asked during the Hybrid session)
-
Travis Short
commented
The complexity of maintaining an onsite Exchange organization for a small business is getting out of hand.
The only feature we want is password sync, yet I am required to continue maintaining a healthy Exchange environment to achieve this (if I want to have a "supported" environment). PLEASE Microsoft, give us SOMETHING to hold on to hope with! Anything!
-
Ryan Morash
commented
Can we expect something to be announced at Ignite?
-
Jake Edwards
commented
The on-prem Exchange server should be decommissionable. The AAD/Msol directory should become source of truth (with editable properties in o365).
-
Douglas Plumley
commented
@Rob de Jong, just being able to source the AD user from on-premises AD via Azure AD Connect and then being able to mail enable/disable directly in EXO would be an amazing start.
So many organizations/institutions are managing complex PS scripts that have to take into account the syncing of AD --> Azure AD, Azure AD --> EXO, EXO --> Azure AD, etc.
Just being able to master mail attributes in EXO would be huge.
Thanks!