Users losing secondary smtp from ProxyAddresses in a two way sync

It sounds like you are missing the CopyTargetAddress xml, which is required for a Hybrid configuration you are implementing.  Please be sure to use your services people for configuration assistance, if needed, but this explains what's required, including the above mentioned xml.

https://support.quest.com/technical-documents/reference-materials-for-migration/8.14/migrating-to-microsoft-office-365/12#TOPIC-711742

The CopyTargetAddress.xml will help by copying the proxies, from the source to the onprem target for AAdConnect (whatever the current name is), to sync to the cloud.

Luke

It sounds like you are missing the CopyTargetAddress xml, which is required for a Hybrid configuration you are implementing.  Please be sure to use your services people for configuration assistance, if needed, but this explains what's required, including the above mentioned xml.

https://support.quest.com/technical-documents/reference-materials-for-migration/8.14/migrating-to-microsoft-office-365/12#TOPIC-711742

The CopyTargetAddress.xml will help by copying the proxies, from the source to the onprem target for AAdConnect (whatever the current name is), to sync to the cloud.

Luke

Hi

We have the proxyaddresses syncing fine as part of migrations & sync.

This issue happens at both ends, it randomly just deletes the secondary proxy addresses.

I am not sure if this is Quest causing this, or something in Azure AD.

We're setting up auditing on the proxyaddresses hopefully, so then we'll be able to see what account modifies the account. I will report back if it happens again.

Thanks,