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.
We’re working on a solution and will update you when we know more.
Robert Chambers commented
any news on this? I just found out as well that despite never having a hybrid (we did a cutover migration and started the sync AFTER the migration), Azure AD sync is syncing all our Exchange attributes, and I cant make any changes to the mailboxes in the cloud! I even checked that exchange sync and extended attributes was turned off, but in the sync service manager it shows all the exchange attributes syncing. This was not what I wanted, I never asked it to do this, I was explicit in the configuration that I don't want this, and yet, I have it. I'm finding it really hard to stay professional with Microsoft at the moment. Now I am stuck with having to delete users from AD, let them get deleted in 365 and trust that I don't lose anything before restoring them! Thanks Microsoft, thanks very much. Any chance we can get more than just we're working on it please? Show your customers some courtesy please, we are getting absolutely shafted here.
I'm updating our network to WS2019
I have have exchange 2010 on 2008r2 with all my mailboxes in EXO - supported until Jan
I cant install exchange 2016 on ws2019
No hybrid license for exchange 2019 so I would have to purchase a full version through volume license plus re-licience my server all over again to get the ammount of OSEs I need to run the extra vm required $$$$$$$$$
Can someone from icrosoft explain the upgrade path please.
All this to change a few attributes!
Michael O'Toole commented
We still need an update on this - it's not feasible to manage an on-prem exchange server just for AAD Connect - especially when Exchange 2016 which is the version to use for Hybrid won't run on Server 2019.
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.
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….
Much anticipated, by many SMB customers
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.
Yay! That's great to Azure AD Team. Super excited to see what you guys come up with!
Do you have an update on when this will work?
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.
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)