Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, March 1, 2019 12:38 AM
Hello all,
Our admin has been creating our AD and Exchange accounts for years with no issues. We moved to an exchange hybrid office 365 system and no problems. All of a sudden we are having issues with people who want there names changed. We have had people after the hybrid switch that were changed fine and now issues.
Normally we keep the UPN and sAMAccountName the same in the users account in AD Users and Computers. This all of a sudden seems to be problematic now. If we keep the UPN and sAMAccountName the same then office 365 still wants to use the old email address while AD and on premise outlook is using the new email. The people who have name changes after moving to the hybrid system in the beginning are fine with having the UPN and sAm the same. Not sure what happened in the past month that all of sudden it has become an issue.
How can I get the users with a name change switched over to the new name and keep the UPN and the sAMAccountName the same?
All replies (12)
Friday, March 1, 2019 9:56 AM
I would like to confirm the following before we could :
1. What attribute did you change in on-premises AD? UPN or samAccountName?
2. Which name did you use to log in your email account?
3. Could you please tell us the issue symptom in details? Where did user encounter this issue? In Outlook or OWA?
4. Did the UPN or samAccountName match primary email address for the migrated users? Generally, they should match each other.
Let me know the result.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Friday, March 1, 2019 12:22 PM
In O365 there is a "policy" of sorts, which requires at least one of the proxyaddresses for the users to match their UPN. It doesn't necessarily need to be the primary SMTP, however you need to have such address, if you remove it, it will be re-added automatically. Does that match your symptoms? If so, the only way to solve this is to change the UPN indeed.
Friday, March 1, 2019 1:42 PM
1. In the past we have kept the UPN and the samAccountName the same. I found that if I change the UPN that everything works properly. But I am being told that the UPN and samAccountName need to stay the same.
2. In the past I believe they used their original name and not the new married name.
3. If we keep the UPN and the samAccountName the same then office 365 wants to keep the old email. In AD we changed the Last Name, Display Name and I'm not sure what he used to change when we only had exchange locally. Alias name was brought up a few times, but that isn't an option anymore in ecp. I tried changing the mailNickname attribute in the AD user account to her new name, but I don't think it made a difference.
4. In the past with users that have been here for years it was only their lastname used for the samAccountName and UPN. Any new users starting probably 10 years ago is lastname.firstname now and that matches the email. The old users still have the UPN and samAccountName the same, but their email is lastname.firstname and they work fine.
Friday, March 1, 2019 1:59 PM
The UPN would be the old name and she does have an smtp the same. The primary SMTP should be the new name. If I change the primary SMTP to be the new name, it keeps getting changed back to the old SMTP name I believe.
Friday, March 1, 2019 2:32 PM
I went in and made the UPN and samAccountName the same. In ECP, under "Enterprise" side, the email is the new name. Over in "Office 365" side, it is the old name.
How do I get Office 365 to be the new email address?
Back in "Enterprise" side, under "Email Address", the primary SMTP is the new email and the below that window the "Remote Routing Address" is set to the new email coming from Office 365 and that is wrong and she won't get email because Office 365 thinks it using the old email.
Thursday, March 7, 2019 6:53 AM | 1 vote
Sorry for the delay.
Just now I did the following test in my lab:
Change the primary SMTP address to the new one, let's say [email protected] (the previous one is [email protected]), then I run Set-RemoteMailbox smith -PrimarySmtpAddress [email protected] -EmailAddressPolicyEnabled $false in the on-premises Exchange Powershell and follow it by an AAD Delta sync. After waiting a few minutes, I could see the primary SMTP address have changed to the new one in my O365 portal.
So did you modify your emails address via the above method? We suggest you use that way toward a new mailbox then see if issue persists.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Monday, March 11, 2019 2:01 AM
Just checking in to see if above information was helpful. Please let us know if you would like further assistance.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Tuesday, March 12, 2019 6:12 PM
Do doing that it would keep the username in AD and the UPN at smith, but make their email address andy.smith on local exchange and office 365 side with it being their primary as well? The person that usually does this uses GUI for everything. Is command line the only way to do it?
Tuesday, March 12, 2019 6:17 PM
Another problem I see. When we make a new user in AD they have a mailbox on the enterprise side it takes up to 30-45 minutes for the user to show on the office 365 side under "Recipients" and then under "Migration". Is there any way to speed that up? Will doing a Delta Sync speed it up?
Friday, March 15, 2019 9:37 AM
Do doing that it would keep the username in AD and the UPN at smith, but make their email address andy.smith on local exchange and office 365 side with it being their primary as well? The person that usually does this uses GUI for everything. Is command line the only way to do it?
Yes, it will. We suggest you do it in Powershell, you may verify what I said in your environment first.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Friday, March 15, 2019 9:40 AM
Another problem I see. When we make a new user in AD they have a mailbox on the enterprise side it takes up to 30-45 minutes for the user to show on the office 365 side under "Recipients" and then under "Migration". Is there any way to speed that up? Will doing a Delta Sync speed it up?
Yes, a Delta Sync forces the update or we need to wait for the next sync cycle.
Forcing synchronization with Azure AD Connect 1.1 (AAD Connect 1.1)
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Wednesday, March 27, 2019 9:40 AM
It has been a long time since you made the last reply on this thread. If you don't mind, we'd suggest you mark the replies above as answers, so it will be easy for other community members to find the useful one/ones.
Thanks for your understandings!
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.