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.
66 comments
-
Anonymous
commented
Congratulations on one year anniversary. Unfortunately, this is sitting in STARTED status for the last one year. May be time to change the status to Thinking about it?
-
Axel Gruböck
commented
How about only the Exchange Schema Updates and the Exchange Management Tools installed on-premise? Is this a supported way to go?
-
Libor Dusek
commented
Can we have a more detailed estimate on this? "Several months if not years" is hardly a thing I can tell a customer. Or it would be beneficial if some PO explains in a blog post the complexity behind because costumers are simply pointing out that it's just setting up the attributes in AD.
There is no need to migrate mailboxes or anything like that - this requirement is really for simple scenario where everything but AD is run in the cloud, so there is no need to do any fancy magic.
-
Anonymous
commented
@Azure AD Team, The status was changes to Stated in August 2019. It has been 10 months.... It has been several months.
Are you saying that you need several more months? Several more years?
-
Anonymous
commented
> this is a work item that will take several months if not years to implement.
Really? We just need a simple attribute management solution that's supported.
Other solutions are available and they didnt take years. However they cost and are unsupported.
Please explain the complexity. -
MCS UK Infra
commented
interested to know when this will be updated
-
Anonymous
commented
@Azure AD Team - What is the complexity here, surely its just a few attributes that need to be written back to on prem?
If its more complex than that, what is the complexity? We are all responsible for having to explain this to our management teams and just 'Microsoft say its too hard' is not okay.
-
Update - we are aware of the importance of this requirement. Unfortunately this is a work item that will take several months if not years to implement. We are working on this but will likely not provide a solution in the coming months.
-
Webs
commented
This is realy a big problem - we also want for our customers just a simple password sync.
A lot of our customers want to shut down there old on-prem exchange(2007,2010...) and moving to 365. Managing E-Mail on Exchange Online and the rest on On-Prem AD... this should n`t be a so huge problem!? ... State today: a clean migration from On-Rem Exchange to 365 inculding turn off local excange is not possible :( -
Daniel
commented
Hi , may i know the status
-
Anonymous
commented
Hi, whats the status here?
-
Petter Arnesen
commented
This is the top voted on idea for Azure AD Connect and is also requested on other uservoice sites, e.g:
https://office365.uservoice.com/forums/273493-office-365-admin/suggestions/16644265-ability-to-manage-exchange-online-without-the-requ
https://office365.uservoice.com/forums/264636-general/suggestions/13616214-decommission-exchange-server-after-migration-to-ofWe need something more than just "working on it" after nearly six(!) years
-
NateP
commented
This is HUGE. We are moving from Exchange 2013 to Office 365 currently. I've now learned that I need to spin up Exchange 2016/2019 on-premise just for management. My team does not want to edit attributes manually.
Isn't the whole point of moving to O365 to get rid of our Exchange servers?
How do large enterprises sync their AD to O365 if they're not using AAD Connect?
-
Thorsten
commented
It would be really nice to hear something about the actual status and maybe plans of the publishing date.
-
Jared Lambe
commented
Any news? Very keen for this.
-
Patrick Gorden
commented
Needing an on-prem exchange is dumb. Please remove the 'unsupported' verbiage from your articles. Powershell, AD, ADSI Edit - they're all valid tools and are even easier than EMC, and don't require security patching as often!
-
Anonymous
commented
Soon?
-
Anonymous
commented
>We’re working on a solution and will update you when we know more.
Its been 4 months since the above comment.
End of support for 2008R2 is Jan, and this is blocking infrastructure change for me.
Could you give us an update please. -
Justin King
commented
This is insane.
Right now anyone can technically do this by editing the attribute directly in an ugly fashion using classic MMC tools. To still have to stand up an entire exchange server _just_ so you can give a better GUI to the lvl1 tech is crazy.
This shouldn't be hard.
-
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.