It is a Cloud age and as a Microsoft fan I use and work with Office 365 and Azure (slightly), so I wanted to post a guide about the key stone of the cloud and on-premise authentication – ADFS. As you probably know, Microsoft has so far relased several versions of ADFS and upgrade is not so easy, especially if there is Office 365 involved.

Versions released:

ADFS 1.0 (Windows Server 2003)

ADFS 1.1 (Windows Server 2008)

ADFS 2.0 (Windows Server 2008 R2)

ADFS 2.1 (Windows Server 2012)

ADFS 3.0 (Windows Server 2012 R2)

I will write articles about upgrade from ADFS 2.0 -> 2.1 -> 3.0

Prerequisites:

3rd party trusted certificate with host name of ADFS service published in external DNS (in my case *.salonovi.cz by Comodo)

ADFS servers and AADSync to synchronize identities from on-premise to cloud.

As this is the intro part of the series, let me use it, to show, how to connect to multiple Office 365 customers. It is easy, and if you need more security,do not fill passwords but use (get-credential) instead.

To run function just open new powershell session everytime, you want to connect to Office 365, type: Open-Office365Session and from menu type number you want.

Thats it. I have prepared Office 365 tenant, I have ADFS servers, 3rd party trusted certificate and I can start working on identity sync between On-Premise and Office 365 using AADSync. Latest AAD Sync can be dowloaded from the following link:

When I shortly checked what is new in Windows Management Framework 4.0, I was exciting to see feature Windows PowerShell Desired State Configuration (DSC) because it brings us declarative syntax and basically new concept of scripting, wow.

IMPORTANT: Not all Microsoft server applications are currently compatible with WMF 4.0. Before installing WMF 4.0 Preview, be sure to read the WMF 4.0 Preview Release Notes. Specifically, systems that are running the following server applications should not run WMF 4.0 Preview at this time: