HI @NeverKnow-2832,
You don' need to worry about the .local domain. Only domains that you use in Azure must verified.
Users use the UserPrincipalName attribute when they sing in to Azure AD.
Just go ahead.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am a bit confused right now.
I have a local AD server that was setup long ago to domain.local
As it is a non-routable TLD, I am getting confused what I need to do to get AzureAD connect up and running.
On the local AD, I have added domain.com to the list of alternate UPN suffixes in Domains and Trusts.
For each user, I have changed their UPN to the domain.com UPN.
When I get to the "connect directories" step in the wizard, I enter the following:
domainaccount@keyman .com (rather than domain.local\domainaccount)
This successfully verifies the account to the domain.local AD server.
On the following screen, I have :
domain.local Not Added
domain.com Verified
Do I need to worry about the .local being "Not Added"?
All info I read says that both must be verified before continuing.
I don't plan on renaming the domain.
I plan on using the user's email address as the as the attribute to sync on as the username/account name for the O365 account and local AD account do not match (note: no on-prem exchange server)
HI @NeverKnow-2832,
You don' need to worry about the .local domain. Only domains that you use in Azure must verified.
Users use the UserPrincipalName attribute when they sing in to Azure AD.
Just go ahead.
Just update the user mail attribute on local AD to First.last@keyman .com, this will create Azure AD user object First.last@keyman .com
And don't create user object on Azure AD manually, AADC will sync from local AD
Regards,
Ganesamoorthy.S
www.windowstricks.in