asked on
I have a 100% on-premise setup going currently, with Active Directory and Exchange. Windows 2012 R2 servers, and 2008 R2 servers.
We have O365 licenses that are not being used, unfortunately. I want to sync a pilot group to start using things like Skype for Business, and SharePoint online, then later down the road have a hybrid Exchange setup.
Couple issues I noticed, however, is there are a couple hundred accounts already sitting in O365, that appear to be the result of a screwy sync a while back. I don't think deleting them will do anything, as I know nobody in the organization is using O365 for anything (besides people like me with an Admin account that can login and manage stuff).
Is there any harm in removing all those accounts from O365, and re-deploying a DirSync server? Deploying the DirSync server, does that start automatically doing things an admin wouldn't want it to do? Or when deploying, am I setting it up on my terms? Like being able to only select a specific OU for syncing (like my pilot group)?
Lastly (I think), is there a need to verify our federated domain (we'd be authenticating with O365 with our UserPrincipalName) with an mx or txt record or anything, or is that only for Exchange Online?
We have O365 licenses that are not being used, unfortunately. I want to sync a pilot group to start using things like Skype for Business, and SharePoint online, then later down the road have a hybrid Exchange setup.
Couple issues I noticed, however, is there are a couple hundred accounts already sitting in O365, that appear to be the result of a screwy sync a while back. I don't think deleting them will do anything, as I know nobody in the organization is using O365 for anything (besides people like me with an Admin account that can login and manage stuff).
Is there any harm in removing all those accounts from O365, and re-deploying a DirSync server? Deploying the DirSync server, does that start automatically doing things an admin wouldn't want it to do? Or when deploying, am I setting it up on my terms? Like being able to only select a specific OU for syncing (like my pilot group)?
Lastly (I think), is there a need to verify our federated domain (we'd be authenticating with O365 with our UserPrincipalName) with an mx or txt record or anything, or is that only for Exchange Online?
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 11 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Most Valuable Expert award recognizes technology experts who passionately share their knowledge with the community, demonstrate the core values of this platform, and go the extra mile in all aspects of their contributions. This award is based off of nominations by EE users and experts. Multiple MVEs may be awarded each year.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.