Here’s what I did, I found this MS doc for reference:
- I followed this to guide me to make the “primary” tenant.
no, I did not check either checkbox, **** em!
- I read this content to understand the tenant hierarchy.
- I added a custom domain (zewwy.ca), it said, sure no problem no federation issues, just verify. (Create a TXT record on the registrar to verify you own domain.)
*refresh the page and the status will update accordingly.
- I proceeded to download the Azure AD Connect msi file via the provided link after adding the custom domain.
- Install: (This was on Server 2016 Core)
Click Accept Next.
- You must have an Azure AD Global Administrator account for the Azure AD tenant you want to integrate with. This account must be a school or organization account and can’t be a Microsoft account.
- If you use express settings or upgrade from DirSync, you must have an Enterprise Administrator account for your on-premises Active Directory.
- If you use the custom settings installation path, you have more options. For more information, see Custom installation settings.
Enter the Credentials from Step 1 (or enter the credentials provided by your MSP/CSP/VAR.
Enter the credentials of the local domain, enterprise admin account.
If you wish to do a hybrid Exchange setup check the second checkbox, Not sure how to configure this later but I’m sure there is a way. At this time that was not part of this post’s goals.
There was one snippet I missed, it appears to install a SQL express on the DC.
Then it appears to install a dedicated service.
This is Ground Control to Major Tom…
This is Major Tom to Ground Control… You’ve really made the grade!
They got all my passwords!
wait … it worked…. like what? No Errors?… No Service account creations? It actually just worked?…
Goto azure portal login, use my on prem credentials… and it logged me in….
I’m kind of mind blown right now. Well Guess on the next post can cover possibly playing with M365 services. Stay tuned. 😀