SipProxyAddress AttributeConflictValues while syncing AD On-Premises to Ahzure AD

-
In some cases, where you have the same user in On-Premises AD and Office 365 Azure AD, synchronization may fail. Fixing a common DirSync/ AAD Connect issue with duplicate cloud account.
This is due to the SOFT MATCH (UPN and ProxyAddesses), you must use HARD MATCH.
The duplicate error, which means the Local AD account and the cloud account did not merger due to Immutable ID mismatch.
ExtraErrorDetails:

[{"Key":"ObjectId","Value":["677e2ead-14e8-4e18-9b25-49d5c75472f1"]},{"Key":"ObjectIdInConflict","Value":["7505ed65-e7f5-4dca-9f78-2617a247f047"]},
{"Key":"AttributeConflictName","Value":["SipProxyAddress"]},{"Key":"AttributeConflictValues","Value":["UserName@domain.com"]}]



$upn user@domain.com 
$GUID = (Get-ADUser -Filter {UserPrincipalName -eq $upn}).ObjectGUID 
$ImmutableID = [System.Convert]::ToBase64String($GUID.tobytearray()) 
Set-MSOLuser -UserPrincipalName $upn -ImmutableID $immutableID

This fixes the issue. 

 Some more verifying the ImmutableID:
Get-MsolUser | ft UserPrincipalName,immutableid,lastdirsync* UserPrincipalName

if you have sourceanchor issue, try setting the ImmutableID to $null
Set-MSOLUser -UserPrincipalName user@domain.com -ImmutableID "$null"

Issue with user newly created in Azure AD in the format of user{4-digit}@domain.com.
You must delete the Online USer and remove this object from recycle bin.
Remove-MsolUser -UserPrincipalName user2345@domain.com -RemoveFromRecycleBin

Note:
https://support.microsoft.com/en-us/help/2647098/duplicate-or-invalid-attributes-prevent-directory-synchronization-in-o
https://support.microsoft.com/en-us/help/2643629/one-or-more-objects-don-t-sync-when-the-azure-active-directory-sync-to
https://support.microsoft.com/de-de/help/2430520/error-in-the-office-365-portal-value-of-msrtcsip-primaryuseraddress-or
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-syncservice-features

Comments

  1. SilverBanditOctober 21, 2019 at 11:01 AM

    In your solution, line 3 generates an error on my 2016 server - "You cannot call a method on a null-valued expression."

    ReplyDelete
    Replies
    1. Thomas PoettOctober 21, 2019 at 11:19 AM

      Hi, this is because a typo in the first line:
      $upn = user@domain.com
      the equal is missing

      Delete
    2. SilverBanditOctober 21, 2019 at 12:34 PM

      Thanks Thomas, but no, I spotted that and fixed it (you also need quotes round the email address). Still got the error...

      Delete
    3. Thomas PoettOctober 21, 2019 at 1:07 PM

      This is honestly wired. The error tells you, that ToBase64String($GUID.tobytearray() is empty/ has no value/ the transformed expression should be empty. can you check, the result if ToBase… only

      Delete
  2. Jared LukerNovember 9, 2020 at 10:06 PM

    I get the same thing reported as Thomas Poett. Maybe this blog post should be fixed or taken down?

    ReplyDelete
    Replies
    1. Thomas PoettNovember 10, 2020 at 8:23 PM

      Did you check the ToBase only. What’s your result?

      Delete

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more