Forum Discussion
New Setup 2 Domains
What you've described is the setup of a single domain that has an additional routable UPN suffix added to it.
Adding additional routable UPN entries does not mean you have multiple domains. Instead, they are considered additional namespaces within that single domain. There remains only a single account database and so on. All adding a routable UPN achieves is being able to specify a different UPN suffix on a per account basis.
If my interpretation of what you have described is correct, then seeing just the one domain listed in the agent during installation is expected and correct.
Cheers,
Lain
- bfry2461Oct 20, 2023Brass ContributorSo How do I fix it?
- LainRobertsonOct 20, 2023Silver Contributor
Fix what? From your description, everything is showing precisely as it should.
If what you're intending to ask is: how to I get a user with a userPrincipalName in Active Directory of:
someName @ domain.local
To be set as:
someName @ domain.com
(Note, I've had to use spaces to get around this forum stripping out SMTP-style addresses)
Then you are focusing on the wrong thing. You need to read up on and understand how to perform attribute mappings - specifically using expressions (and functions - Replace() would be your best bet), as that kind of name translation has nothing to do with the agent installation.
- Microsoft Entra Cloud Sync new agent configuration - Microsoft Entra | Microsoft Learn
- Attribute mapping in Microsoft Entra Cloud Sync - Microsoft Entra | Microsoft Learn
The other approach you might be able to leverage is changing the existing values for SMTP-like attributes such as userPrincipalName, mail and proxyAddresses in Active Directory first, which would allow you to use direct mappings rather than expressions in the Cloud Sync mappings (see the screenshots in either/both of the articles above).
Cheers,
Lain