Exchange On Prem / Exchange Online / AADConnect - attribute difference

[Stephen Bell]

Hey everyone --

In my environment we are running Exchange Hybrid - only for management.  All of our mailboxes live in O365.  We are running AADConnect on prem for directory sync.

I have a user that was recently created - and their last name was initially spelled incorrectly.

We have gone back and fixed the spelling problem, however, in Exchange Online - the smtp (lowercase) attribute is still showing the misspelled name.  On Prem however, it is correct.  Shouldn't AADConnect take care of this?   Is there anyway that I can fix this manually?  I don't believe it is causing any problems - just an inconsistency that I am afraid somewhere down the line will get in the way of something.

Example:

Correct Spelling:  Eric Ryan, email is eryan@domain.com

On Prem: smtp is eryan@domain.onmicrosoft.com, SMTP is eryan@domain.com

In Cloud: smtp is eryann@domain.onmicrosoft.com, SMTP is eryan@domain.com.

Thanks

Steve

[#2]

Was the UPN / login name also incorrect and updated? If so you'll need to run a command in azuread side to update the login name!

[#3]

Yes - UPN has been corrected. The only difference I can see is the smtp @domain.onmicrosoft.com attribute

[#4]

that should be based off the "alias" attribute on prem. The default policy I believe is based off that attribute like it was for onprem. So go check your alias.

[#5]

I think it's mailnickname is the actual attribute in AD.

[#6]

mailnickname = eryan -- so that is correct.

I guess I am still stuck on why AADConnect doesn't push the on-prem values to the cloud resolving the conflict?

[#7]

We used to have this issue before sometimes. I would have to change another value to force it to update as sometimes the delta wouldn't pickup change on certain values, I just can't remember which one we would change to force it to update then change it back, maybe just try changing or adding in another alias to the e-mail address and see.

[#8]

Simply force a full sync: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler...

[#9]

I just ran a Start-ADSyncSyncCycle -PolicyType Initial -- and also -- went into Sync Services and ran the Full Sync profile. Still seeing the misspelled @domain.onmicrosoft.com in the cloud under the proxyAddress attribute.

[#10]

Yeah, that address isn't actually synced up, it's generated from something and exists on o365 side only, i have this exact problem currently on my test domain so I'll see if I can figure it out and get back to ya ;).

[#11]

kanka">sune

[#12]

@Chris -

Were you ever able to figure out what is going on here?

Thanks
Steve

[#13]

Na, work has been slaying me lately. It's really not an issue that it's not the same, the alias really doesn't do anything and is cosmetic.