one connector is showing for the user in AD Connect server

Question

one connector(On-prem) is showing for the user in AD Connect server.

On-prem changes is not reflecting in azure AD connect after full sync for the user .

In Attribute filtering it is showing like mailnickname is not null error .

But we applied mailnickname in on-prem,still we are getting same error

one connector in ad connect.jpg

Answer 1

Hi @j prasad ,

It sounds like there could still be an attribute mismatch causing Azure AD Connect to not reflect the changes. Have you made sure to update the Alias attribute as well using Set-Mailbox or Set-RemoteMailbox using the steps described here?

• Set-RemoteMailbox

PowerShellAI ConvertCopy

$alias=Get-remotemailbox <user@domain.com>
Set-RemoteMailbox <user@domain.com> -alias "$($alias.alias)1"

• Set-Mailbox

PowerShellAI ConvertCopy

$alias=Get-mailbox <user@domain.com>
Set-Mailbox <user@domain.com> -alias "$($alias.alias)1"**

Also, confirm that the attribute is updated in your Domain Controller under Active Directory Users and Computers > find the user that owns the mailbox > right click on them > select Properties > select the Attribute Editor Tab > find the mailNickname attribute.

See also: mailNickName not updating

If this does not work, please share a screenshot of the error you are receiving and confirm what your setup entails.

Answer 2

Hi Marilee,

we don't have Azure Active directory connector for the user in ad connect server.

How we can run the above comments.

we have applied the mailnickname in on-prem directory but that changes is not refelcting in azure ad connect after full sync cycle

I have attached the attribute filtering error