This article contains information about a new authentication framework for Microsoft Office 2016.
By default, Microsoft Office 365 ProPlus (2016 version) uses Azure Active Directory Authentication Library (ADAL) framework-based authentication. Starting in build 16.0.7967, Office uses Web Account Manager (WAM) for sign-in workflows on Windows builds that are later than 15000 (Windows Version 1703, build 15063.138).
The Office sign-in workflow stops or shows no on-screen progress. The sign-in window shows a "Signing in" message or a blank authentication screen.
Because of the introduction of WAM, nonsecure endpoints (non-HTTPS) traffic is blocked in authentication workflows.
Make sure that all authentication endpoints follow the HTTPS protocol.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Alternatively, you can change Group Policy to add the following registry value at user log-on:
Note After a fix for this issue is released, you should remove this registry workaround, or authentication experiences may be degraded. This reg value should not be used as a long-term solution.
- On Windows 7, 8, or 8.1, or on Windows 10 builds that are earlier than 15000, ADAL authentication is the only option.
- The Windows build should be later than 15000 (Windows Version 1703, build 15063.138, Generally Available). For more information, see Windows 10 release information.
- This article applies if you use Microsoft Federation or non-Microsoft Federation solutions.