• Microsoft Office 365 provisioning
• Proxy addresses

First, verify if a duplicate proxy address exists in the AD. Please refer to this Microsoft video for the next steps.

If a duplicate proxy address does not exist on the AD and the Okta side and the error still pops up:

1. On the Azure/Office 365 side, check logs to determine if the account is conflicting with the errored-out account's proxy address.
2. Update the Username/UPN/Proxy address of the conflicting account on the Office side temporarily to any value other than the duplicate value. Only update the values that conflict with the proxy address of the errored-out account.
   • Check the Office Logs to determine which proxyAddress is creating conflict. We need to update that address for the conflicting user, even if it is the correct address for the user. This will be a temporary change until we are able to successfully push the errored-out account from Okta. This is to clear the shadow attribute values of the errored-out user on the Azure side. Successful sync from Okta will clear the incorrect proxy address value (that matches with the conflicting account) in the shadow attribute of the user on the Azure side. This is what prevents the profile push from Okta and creates conflict.
3. Retry profile push from the Okta task page for the errored-out user.
4. Revert the Username/UPN/Proxy address of the conflicting account that was changed in step 2.

The video below showcases an example: