I need to stand up a test domain to try and fix accounts that have been synced into AAD. I have had zero experience with Azure AD or O365, so I'm not sure how to proceed.
A previous admin setup our company's O365 account and setup AD Connect, apparently without ever reading up or testing. AD here has been a mess.
I am the 4th person to inherit this mess. All the previous admins had their idea of the proper AD structure and best practices for groups and group policy. I've spent the better part of a year putting out fires and replaced a couple DCs and cleaned up ghosts of DCs past. We have not had any replication issues in 6 months, so I feel confident in moving forward with trying to get O365 working.
====================== The problem(s): Accounts that are synced have firstname.lastname@example.org names and do not allow us to log into O365. The only working accounts have been created in the cloud using their email addresses.
My plan: Setup a new DC (Hyper-V) Allow it to replicate. Shutdown DC and clean up AD so there are no ghosts left. Bring the DC up in an isolated network. Setup a trial O365 account. Sync AD to trial account. Try to fix the problems we have in our production domain.
Here is where I have questions.
I need to allow this test domain to have access to the internet and O365.
Will I be able to setup a trial O365 account and setup AD connect to sync just like the production domain?
Will I be able to setup a hybrid Exchange environment to test moving mailboxes to the cloud in a trial?
The IDfix tool says I need to fix ProxyAddresses. Do I set it to our users SamAccountNames or email addresses.
I'm probably missing a lot here. Please let me know what I've missed and where I need to be looking.
Thanks for your help! dot19408