Using Azure AD Connect to create Office 365 user accounts
I was recently onboarded into the Microsoft Office 365 Pro Plus subscription and I now have an initial tenant set up named mycompany.onmicrosoft.com.
I have over 100 users so I was hoping to be able to populate my Users in Office 365 by using the Azure AD Connect tool, thus allowing me to import users from my local AD and create user accounts for them. My goal was to make it as easy as possible to authenticate with Microsoft Office 365 the first time they launch it. I had hoped for a seamless way to have it pass their AD credentials to Azure but it doesn’t seem like I can do that since there is no way for me to add a new domain matching my AD name since it can’t be verified (it isn’t registered publicly and is squatted).
Office 365 is installed entirely on our test machines in a VDI pool. I have been able to launch it using my manually created
Do I have any way to make this easy or will I just need to have each user know that when they log into Office 365 for the first time they will have to just put username@mycompany.onmicro
I have over 100 users so I was hoping to be able to populate my Users in Office 365 by using the Azure AD Connect tool, thus allowing me to import users from my local AD and create user accounts for them. My goal was to make it as easy as possible to authenticate with Microsoft Office 365 the first time they launch it. I had hoped for a seamless way to have it pass their AD credentials to Azure but it doesn’t seem like I can do that since there is no way for me to add a new domain matching my AD name since it can’t be verified (it isn’t registered publicly and is squatted).
Office 365 is installed entirely on our test machines in a VDI pool. I have been able to launch it using my manually created
Do I have any way to make this easy or will I just need to have each user know that when they log into Office 365 for the first time they will have to just put username@mycompany.onmicro
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Adam Brown
I should add, if you have a public email address domain, you can use that domain as your UPN suffix if you like.
ASKER
That's where it gets a little sticky. Our parent company owns our email domain and hosts our email services. We are just an affiliate with our own independent AD and O365 subscription. I think I will go with your first suggestion because we do have another public domain name we can use. I appreciate the advice and link to the resource!