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.
Microsoft could easily build an O365 management tool which does the local AD exchange schema update and add the functionality to ADCU (as a tab as it existed before) to manage On-Prem exchange attributes and add exchange PowerShell functionality.
Especially SMB customers which less mailboxes do not want to install and keep an exchange server to achieve a supported environment even it is via the free exchange license Microsoft offers.
An alternativ would be, not setting the Exchange Attributs to read in O365 so configuration could be done on the O365 site.
Or as stated in other comments write back of the sync tools would also an option.
I wonder why Microsoft is not listening to their customers needs.
I am not willing to migrate to Office 365 as long as there is no clean solution for this problem.
Any updates or progress? It would be nice to use the Hybrid exchange for rich mailbox moves to O365 and then remove post migration but maintain DirSync/AADConnect. This is a big thing in the SMB space.
for small business customer isnt a possibel way to let eh exchange instance for management purposes only. MS please get us a solution. Thx.
What we need is to use AD as a identity provider and Exchange online manages the mailboxes. If you run as we do with on prem AD with AAD Connect and adfs you just don't want to manage exchange attributes on-premise, no matter what. We need the option migrate and then cut the attributes synchronization for email. And when we add users we sync the account, and later adds email functionality in Office 365.
Chris K Ellsworth commented
FYI you can mange those items through the Attribute Editor within ADUC
I would echo these comments also, would very much prefer a method to keep AD Connect Sync in place WITHOUT the requirement for Exchange.
I just finished a Hybrid "Express Migration", and am using the only supported way of managing the cloud accounts using Server Essentials Role locally. However this is not as good as a proper AD Connect Sync option.
Robert Cunningham commented
Would be nice to see some progress on this request...
Øystein Rudi commented
This is a higly required feature, under review sine dec. 2014???
Just allow write-back functionality of the proxyAddresses attribute in AAD Connect and allow updates of email addresses in O365/AAD.
Then AAD Connect setup could extend AD schema with just those few needed attributes.
This functionality is the last bit needed!
I'm supposed to be moving 100 users to Exchange online in a month or so, and this isn't looking good.
The PM has been reviewing this request for a year and a half? Asking for feedback looks really bad when there is no communication.
Eric R commented
The importance and priority of this ability is going up the longer time goes by. Customers are on board with the idea of moving all services into the cloud. Having the ability to get a granular "source of authority" transfer into Office 365 vs on-prem Active Directory for just exchange attributes is a big deal. I am dealing with multiple clients that have never had Exchange on-prem. Forest schema has never been extended. They require and need AAD Connect functionality for user, security group management and computer management (Windows 10 domain joined). The fact that this forces them into a pattern of Exchange attributes being also homed to Active Directory as the source of authority is painful. It honestly takes away some of the benefits of Azure AD Connect. Most of my clients are NOT deploying ADFS as well because of the footprint it requires, and with password hash sync and the advancements in AAD there are fewer benefits for using ADFS especially with Windows 10 integration with AzureAD now. PLEASE up the priority of the ability to perform a granular source of authority transfer for exchange/email attributes into AzureAD when using AAD Connect. It will pay big dividends for clients fully adopting the Microsoft Cloud.
Alex Vella commented
Little ridiculous that I can't write back into the ProxyAddresses attribute from Exchange Online yet. I really hate giving the helpdesk a ten minute lecture on the ADSIEDIT tool
Peter Selch Dahl commented
Thanks Brjann Brekkan,
Than I'll reach out to Samuel to continue the dialog directly
Boonhock Lim commented
At least make it possible with Azure Active Directory Premium - User write back feature.
Peter Selch Dahl commented
Microsoft currently use a Master management approach where the object must be managed where it is born. It doesn't matter if the object is born in AAD or AD. The Exchange 2013 is a requirement for writeback support of mail settings.
A better idea would be to implement write-back functionality of the proxyAddresses attribute in AAD Connect and allow updates of email addresses in O365/AAD.
Andrew Sharicz commented
This is not true dirsync does not require an Exchange server, the problem here is for some settings we need the AD attributes from Exchange Schema extension, not a requirement for Exchange server on premise. What I have done in a greenfield environment is perform just the ADPrep step for Exchange 2013. In an existing environment you can uninstall all the Exchange servers and do ADPRep for 2013 if needed. Now this means you have to edit the Attributes in AD directly from ADUC, which works for me as I have familiarity with that, but I can see why some would want to keep a server around for easy editing through the ECP. Its a fine distinction, but worth noting if you don't want to run an Exchange server in house just to have a GUI to edit AD attributes you do not have to.
What is really needed is a schema extension and attribute mgmt tool for Office 365. It is sort of silly that you need Exchange 2013 components for Office 365 it should be a complete solution without Exchange. As such I def vote for this.
+1 for a simple app to replace exchange requirement.
Any update on the PM review?
This would be very nice