Map on premises domain.local to custom domain on azure AD

Filippo

12/20/22, 7:37 AM

Our on premises windows domain is not public, it is myDomain.local. In Azure Active directory we have created a custom public domain publicDomain.com and we have the legacy domain publicDomain.onMicrosoft.com. We want to sync users from myDomain.local to publicDomain.com but they are created inside publicDomain.onMicrosoft.com.

According to Microsoft support the only way to achieve this goal is to re-install Azure Connect and tell it to use a specific field to create new users in Azure AD. For example we can set user mail field to [email protected] to create that user principal name in Azure AD. I found this related post which says to put a DNS entry , but I cannot understand how it may work.

Is there another way to force Azure AD to map users from myDomain.local to azure custom domain publicDomain.com ? Can the synchronization rules editor be used for this scope ?

1 + 0

azure-active-directory

Score:0

Server

joeqwerty

12/20/22, 2:13 PM

According to Microsoft support the only way to achieve this goal is to re-install Azure Connect and tell it to use a specific field to create new users in Azure AD.

I don't know where you read that, but it isn't correct. Here's what I'd suggest:

Here's what I'd suggest:

Reconfigure Azure AD Connect to sync an empty OU. This will put all of your AD accounts out of scope and will cause them to be deleted in Office 365. Note that this will only affect the user accounts that have been synced from on premises AD. It will not affect your existing Office 365 "cloud only" users.

Add your Office 365 verified domain as a UPN suffix in AD.

For one AD user account set the new UPN suffix on their user account. Make sure that the User Logon Name matches the Office 365 username for the existing Office 365 "cloud only" user ([email protected]). If it doesn't, change the AD User Logon Name to match the Office 365 username. This won't affect the AD users ability to logon to the domain, unless they're logging on with their User Logon Name.

Permanently delete the Office 365 account for this user. - https://practical365.com/permanently-remove-deleted-microsoft-365-users-from-azure-ad/

Move this user in AD to your empty OU and initiate an Azure AD Connect delta sync cycle. The user should now be synced to the existing Office 365 user account. If it is, then repeat the above for all of your AD users. If it isn't then open a support case in your Office 365 tenant.

0 + 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Map on premises domain.local to custom domain on azure AD

TH: แมปในสถานที่ domain.local กับโดเมนที่กำหนดเองบน Azure AD

RO: Hartați domeniul local.local către domeniul personalizat pe Azure AD

RU: Сопоставление локального домена domain.local с личным доменом в Azure AD

VI: Bản đồ tại cơ sở domain.local sang miền tùy chỉnh trên Azure AD

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.