Forum Discussion
Detailed error message: Exception happened when doing AAD dual-write.
trying to delete and add contacts in 365, got error below An Azure Active Directory call was made to keep object in sync between Azure Active Directory and Exchange Online. However, it failed. D...
Marvin Oco I'm having the same issue when attempting to create a new group. I don't have AD setup yet.
this is because of recent update from MS that they have enabled dual write feature for all tenants and this will be permanent feature as of now.
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-improvements-to-accelerate...
I faced various issues like not able to add alias.
Getting error: Another object with the same value for property EmailAddresses already exists.
The issue may be transient and please retry a couple of minutes later. If issue persists, please see exception members for more information.
Cmdlet-UnableToWriteToAadException]
If you look at the error details it says "UnableToWriteToAadException". When we connect to powershell of the tenant and run command:
- Ran command: Get-OrganizationConfig | fl IsDualWriteEnabled
IsDualWriteEnabled : True
A support ticket and you need to tell MS to disable the feature. Then you can remove shared mailbox.
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-improvements-to-accelerate...
I faced various issues like not able to add alias.
Getting error: Another object with the same value for property EmailAddresses already exists.
The issue may be transient and please retry a couple of minutes later. If issue persists, please see exception members for more information.
Cmdlet-UnableToWriteToAadException]
If you look at the error details it says "UnableToWriteToAadException". When we connect to powershell of the tenant and run command:
- Ran command: Get-OrganizationConfig | fl IsDualWriteEnabled
IsDualWriteEnabled : True
A support ticket and you need to tell MS to disable the feature. Then you can remove shared mailbox.
ok now in my tenant
might be related to incident EX235961.
