Connect Windows Server Essentials Experience Server Role to Office 365



Why bother with Windows Server Essentials now? Because although you can rely entirely on Office 365 in the cloud, chances are you want more local control and hands-on capabilities on local servers. That’s the main reason to use Windows Server Essentials, as a supplement to Office 365. (Yes, you can also use Windows Server Essentials in an on-premises-only deployment for basic services.)

By integrating your Windows Essentials Server with Office 365, you can perform much of the administration through the Dashboard on your server. For example, you can create accounts easily; you can manage license assignments; password changes made on-premises are synced to Office 365; and you can manage mobile devices and other services from the server. Granted, you could do this from the Office 365 admin center too, but it’s so much easier to have everything in one place.

In this tutorial how to connect Windows Server Essentials to Office 365 is shown. It contains wizards to handle complex integrations, such as synchronizing directories and setting up single sign-on. Remember: The Office 365 integration works only with a single domain controller, and the wizard must run on that domain controller.


Open Server manager and select add roles and features

2012 ad-2017-08-18-18-44-59

Select the appropriate server

2012 ad-2017-08-18-18-45-59

Select Windows Server Essential Experience server role

2012 ad-2017-08-18-18-46-12

2012 ad-2017-08-18-18-46-15

Click Next to continue

2012 ad-2017-08-18-18-46-28

Confirm and install

2012 ad-2017-08-18-18-46-43

After the installation configure Windows Server Essential Experience

2012 ad-2017-08-18-18-51-37

2012 ad-2017-08-18-18-53-43

2012 ad-2017-08-18-18-54-32

2012 ad-2017-08-18-19-00-02

Open Dashboard

2012 ad-2017-08-18-19-00-16


Integrate with Microsoft office 365

2012 A1 skype 2015-2017-10-03-05-30-46

2012 A1 skype 2015-2017-10-03-05-31-04

Provide username and password

2012 A1 skype 2015-2017-10-03-06-34-41

2012 A1 skype 2015-2017-10-03-06-34-45

Restart the server

2012 A1 skype 2015-2017-10-03-06-39-22

2012 A1 skype 2015-2017-10-03-07-32-48

It is done..

2012 A1 skype 2015-2017-10-03-11-55-17