What nobody tells you about setting up Microsoft Cloud services
Are you toying with the idea of introducing Microsoft Cloud Services in your company? Are you wondering how to best begin? Here are three practical tips:
The tenant is the administrative object of all your Microsoft Office 365 services. It continuously appears in the URLs. If you use this service as an exchange platform with customers, partners, or suppliers, they will see the tenant name in the URL. It is best to name it after your company. Careful! It cannot be changed.
The user information your employees are already familiar with should be used for logging in - the way it is already recorded in your local Active Directory (AD). Depending on whether you'd like to make it really simple or really secure, there are two options:
Option 1: Establish Microsoft Azure Active Directory Connect (AADC)
With the synchronization service between the user information in your local Active Directory and the cloud services, replication is asynchronous. This is a problem when you block or delete a user locally. In the time until replication occurs, this user can still access the cloud services.
Option 2: Use Microsoft Active Directory Federation Services (ADFS)
By implementing Active Directory Federation Services in addition, you shift the login process directly into the local Active Directory. Then you know exactly what users can log in when. This is a little more complex but guarantees maximum security.
You've done it! Now activate your first cloud service. Skype for Business is the ideal choice. You can use this Microsoft product as a conference tool or instant messaging platform, for example. No local adaptations are required either – you can just dive right in.
If you're interested in learning more about Microsoft cloud services, get in touch. We'd be happy to help.