Entra-only setup reveals internal-only user UPN?
retained text
In our hybrid on-prem AD to Entra setup, we would use an internal UPN separate from users email addresses. The point is email addresses get used as accounts in external websites and if that site gets hacked, there's no users matching that email address in our tenant to attempt to log in as due to our UPNs are completely different. We're setting up a new Entra-only tenant using UPNs of xxxxx@domainB.com and users email are firstname.lastname@PrimaryDomainA.com. The problem is external Microsoft Teams users, if they start a new Teams chat to one of our email addresses, then they click on that person in the chat, it reveals our internal UPN on our users Teams profile. The difference is that with on-prem to Entra sync we could set the SIP: address of the user, but with Entra-only, it sets the SIP: address to the UPN. Myself and even a better admin have tried everything we can, but that SIP address keeps getting set back to the UPN. Microsoft tickets for Entra and microsoft admin hit the wall. AI searches come up with no way out of this. Are we completely SOL?
document fetched 2026-10-22 00:39 · canonical https://reddit.com/r/sysadmin/comments/1xbovfs/entraonly_setup_reveals_internalonly_user_upn