Proxy Addresses | ADB2C

Question

I am trying to create uses in ADB2C. I am using MS Graph API /users POST

I am getting this intermittent error

{"error":{"code":"Request_BadRequest","message":"Another object with the same value for property proxyAddresses already exists.","details":[{"code":"ObjectConflict","message":"Another object with the same value for property proxyAddresses already exists.","target":"proxyAddresses"},{"code":"ConflictingObjects","message":"Another object with the same value for property proxyAddresses already exists.","target":"User_5a337ec3-691b-43ec-bd7c-b98b8839fcdb"}],"innerError":{"date":"2023-03-17T08:57:05","request-id":"140f4dc0-7f6d-461c-892b-403b95206303","client-request-id":"140f4dc0-7f6d-461c-892b-403b95206303"}}}

status code : 400

The issue is it's intermittent and I am creating emailAddresses with timestamp attached.. so it's unique each time

Answer 1

Hi @Abhay Chandramouli , the error message you are encountering is due to the fact that two objects in Azure AD have the same value for the property proxyAddresses. Azure AD schema doesn't allow two or more objects to have the same value for the proxyAddresses attribute. Each object in Azure AD must have a unique value of this attribute at a given instance.

To resolve this issue, you need to identify the duplicated proxyAddresses value that's causing the error and also identify which two or more objects are involved in the conflict. The report generated by Azure AD Connect Health for sync can help you identify the two objects. Then, you need to identify which object should continue to have the duplicated value and which object should not. Finally, remove the duplicated value from the object that should not have that value. Make the change in the directory where the object is sourced from. In some cases, you might need to delete one of the objects in conflict. If you made the change in the on-premises AD, let Azure AD Connect sync the change. The sync error report in Azure AD Connect Health for sync is updated every 30 minutes and includes the errors from the latest synchronization attempt.

You can find more information about this error and how to resolve it here. Please let me know if you have any questions.

If this answer helped you please mark it as "Verified" so other users can reference it.

Thank you,

James