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.
76 comments
-
Jeff Breunig
commented
As the previous comments have said, the requirement to keep an exchange server on prem for many small organizations doesn’t make sense. Not only does it require resources they likely don’t have, but opens them up to exploits for no real reason. Please address this issue.
-
Anonymous
commented
You can help thousands of your customers with security issues like exchange zero day floating around.
-
Anonymous
commented
Why is this in Started for the last two years? Microsoft doesn’t care about user voice feedback?
-
Anonymous
commented
Any update on this? This is in started status for the last 18 months.
-
Jonathan Weidner
commented
We would really appreciate any further step to the new tool! We have to keep our Exchange Server until you release something finally.
-
Gary Farrugia
commented
Any update?
-
Smith, Chris
commented
Any update?
-
Anonymous
commented
Any update?
-
Anonymous
commented
Any update?
-
Colin
commented
Any update on this?
-
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