In your ADFS console, check the following endpoint shows enabled (/adfs/services/trust/13/windowstransport): Enable ADAL Enable WS-Trust 1.3 for Desktop Client SSO ADAL So firstly, make sure you have this enabled in your ADFS infrastructure.

Showing users a screen asking if they want to add the account to Windowsįortunately, there is a fix for this, which is listed in a Microsoft article, which lists several symptoms but doesn’t specifically mention SSO issues.įirstly, if you are running a Windows 10 build later than 1703, you will be using ADAL.Activation issues after changing password or UPN.Being unable to obtain a license for Office at all, and Office going into reduced functionality mode, especially if you are using Shared Computer Activation.This is due to issues with Web Account Manager (WAM), which is used for authentication instead Azure Active Directory Authentication Library (ADAL) with Office 365 ProPlus on recent versions of Windows. If you are using an Office 365 ProPlus version prior to 1808, along with Windor later, you may have an issue where Office applications do not use SSO to sign in, and after users enter their email address, they then have to enter their username and password again in the ADFS login form.

Office 2016 won39t activate