Can't Update Alias in EAC (Accounts are Synced from Local AD to AAD with AD Connect Sync and We have "NO" On-Premises Exchange)

Question

Hello brothers and sisters,

We can't update alias in EAC. User objects are synced from Local AD to AAD with AD Connect. We can add alias in Local AD and which are successfully synced to AAD but we can't change that alias as primary SMTP address in EAC. It said: "An Azure Active Directory call was made to keep object in sync between Azure Active Directory and Exchange Online. However, it failed. Detailed error message: Unable to update the specified properties for on-premises mastered Directory Sync objects or objects currently undergoing migration. DualWrite (Graph) RequestId: c7970e04-bf13-49fe-b6ad-48b3fdceb089. The issue may be transient and please retry a couple of minutes later. If issue persists, please see exception members for more information. ". Is there any way to disable DualWrite or how can we stop proxy address from syncing? Is there any way to set primary SMTP address in EAC which are synced form Local AD? Thank you very much for your helps in advance.

Answer 1

@Aung Phone Pyae

First thing is we need to make sure we understand that the primary SMTP address and username, first name, last name are user attributes in AD. If you are running a hybrid environment with Azure AD Connect, then all changes need to be made on-premises and then synced to Office 365/Azure AD.

Since you are syncing all accounts from on-premises AD to Azure AD, in a Hybrid environment, your active directory is synced with Office 365 using Azure Active Directory Sync tool (DirSync). Therefore, your on-premises active directory is the authority for making any changes to any of the user attributes, and you need to manage the attributes of the user accounts from your on-premises active directory.

Proxy address first gets synced to Azure AD and post that this value gets back synced to EAC. Proxy address is an attribute which is used in EAC.

Do let me know if you have any further questions

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 2

Since you are syncing from on-premises AD, any change needs to be made therein, and not in directly in the cloud. Including changes to the primary SMTP address.