Forum Discussion
On premise Active directory and Azure Active directory synchronization
- Sep 13, 2017
Hi Brian,
There is no requirements that the shared and custom domain names must match. When you create an AAD instance, you're assigned a sheared domain (which is '*.onmicrosoft.com'), then you need to create a public DNS record (your public domain name) and verify it as documentation suggests (via TXT or MX record). Once it is done, you would have two domain names associated with your directory and you need to change it to 'Primary' (the public one I mean). Then keep going with prerequisites to make AD Sync work.
Please follow:
https://www.microsoftpressstore.com/articles/article.aspx?p=2315271
https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-prerequisites (Azure AD Connect prerequisites).
Hi Brian,
There is no requirements that the shared and custom domain names must match. When you create an AAD instance, you're assigned a sheared domain (which is '*.onmicrosoft.com'), then you need to create a public DNS record (your public domain name) and verify it as documentation suggests (via TXT or MX record). Once it is done, you would have two domain names associated with your directory and you need to change it to 'Primary' (the public one I mean). Then keep going with prerequisites to make AD Sync work.
Please follow:
https://www.microsoftpressstore.com/articles/article.aspx?p=2315271
https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-prerequisites (Azure AD Connect prerequisites).
- DeletedSep 14, 2017
Thanks Alex!!!