Jump to content

Recommended Posts

Posted

I've done this before with local exchange but experiencing a slight difference with office 365.

Due to a name/domain change all users should send from their new email address and receive on both new and old email address.

In AD, the users UPN and Email address have been updated to their new email address and left to sync with azure AD connect.

The user can then sign in with their new email address and receive on their new email address but the old one them disappears as an alias and emails are rejected.

Please could someone assist/advise how to get this working as required.

thanks in advance.

Posted
Is their old primary smtp still listed in exchange/AD user object proxyaddresses attribute as a secondary smtp address? Assuming yes, that should work, so what does AD connect (server and cloud side) say about syncing that change?
Posted
I will look in the morning. However, when I did change the primary and login to outlook for web, it shows the users email address as the new email address but when sending an email, the recipient still saw it coming from the users old email address but will want the new domain as primary sending and receiving, but receive on both old and new.
Posted
I will look in the morning. However, when I did change the primary and login to outlook for web, it shows the users email address as the new email address but when sending an email, the recipient still saw it coming from the users old email address but will want the new domain as primary sending and receiving, but receive on both old and new.

 

Have you checked @Boredguy reply as above. The capital SMTP instead of lowercase smtp.

Posted

Does anyone have script or online links to scripts that will add the additional alias all local AD accounts first as assume need to be that first before changing 365.

This seems a lot of more complex than when i've done changes on local exchange as you just update the email address policy and auto applies to all users and then set new one as default!

Posted
you need to update the proxyAddress AD field with SMTP:address@newdomain and smtp:address@olddomain if you want them to have an alias as well.

 

The proxyaddress attribute is currently is this because there is only 1 currently based on the UPN suffix. Di i need to add in both the existing and new alias/email addresses with the primary one as SMTP:

Posted
The proxyaddress attribute is currently is this because there is only 1 currently based on the UPN suffix. Di i need to add in both the existing and new alias/email addresses with the primary one as SMTP:
Yes. If it empty in AD it won't sync, and the upon will be used by default.

 

In AD you'll have to set it this way (and the capitalisation designates the primary).

 

If you DM me I'll dig out an old script that I used to change them in bulk in AD.

Posted (edited)
The proxyaddress attribute is currently is this because there is only 1 currently based on the UPN suffix. Di i need to add in both the existing and new alias/email addresses with the primary one as SMTP:

 

Yes. 100%. Both need to be present.

 

SMTP:[email protected]

smtp:[email protected]

Edited by Roberto
Posted (edited)
Is that definitely correct? I thought having smtp: was enough - and if SMTP: was not present it would just use the UPN.

 

If you wish to use a primary and secondary SMTP address with On-Prem or Hybrid exchange then both/all addresses should be listed. I'm not saying it won't work any other way, but this is the approved/supported method.

 

Don't forget that with on-prem accounts there's no requirement for your UPN to be the same as your email address at all.

Edited by Roberto
Posted
Is that definitely correct? I thought having smtp: was enough - and if SMTP: was not present it would just use the UPN.

 

Yes. AADSyc will error without capital SMTP so address based on UPN but it's not elegant.

 

Also, dump all proxyAddresses from O365 too as might be blank in AD but you might find some X500 addresses in O365. If so, add them to AD proxyaddresses too.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...