According to the article about Exchange Writeback using cloud sync: "This scenario is now supported in cloud sync. Cloud sync detects the Exchange on-premises schema attributes and then "writes back" the exchange on-line attributes to your on-premises AD environment."
The environment is a typical Exchange Hybrid setup using ADConnect sync (updated to latest versions). The proper rules for cloudnoflow as set forth in the pilot documentation have been setup to not sync two separate OU's. These OU's and the users and groups in them are now being synced using cloud sync. I have the agent on two servers in the local environment and both show healthy. According to the list of items that should be "written back" to on prem is new proxy addresses. basically - cloudLegacyExchangeDN to ProxyAddresses.
I have tried this with one configuration in the cloud sync setup, but at the moment I have two. Shown in this attached image.
So, I make a change by adding a new alias email address to the On-premises synced account by opening and editing the account in Entra and I get the proper response:
The sync never tries to start. I have to hit restart sync to give it a boost.
The Group has no issues:
I expect to see the additional proxy address show up in Exchange on-prem or at least in the attribute editor in AD Users and Computers, but it never happens. It never tries to sync it for the user.
How do we get this to work? Where are the exact configurations to ensure Entra Exchange attributes that should sync to AD will actually do that and be visible?
Thanks!