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).
You may experience one of the following symptoms:
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.
You receive the "You’ll need the Internet for this" message when you switch networks or your computer wakes up after a long suspension/sleep.
Outlook displays a "Need Password" option (in the ribbon or task bar), and clicking it causes a white authentication dialog box to appear briefly and then disappear before you enter the password.
When you’re working on a document that’s saved in the cloud, the Office client randomly prompts you for credentials.
When you try to open or save a document in Microsoft SharePoint Online, OneDrive for business, or SharePoint, you’re prompted for credentials. After you enter credentials, you’re prompted again.
Office ProPlus clients prompt you with an activation screen when you’re already activated. When you enter a value of UserID or UserPrincipalName, the screen vanishes before you enter the password.
Note This resolution only applies to Symptom 1.
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.
Note This workaround applies to Symptoms 1-6.
Warning This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the Microsoft Help article:
322756 How to back up and restore the registry in Windows
Change Group Policy to add the following registry value at user login:
Note After a fix for this issue is released, you should remove this registry workaround, or authentication experiences may be degraded. This registry value should not be used as a long-term solution. We will update this article periodically to address the concern about the fix.
- 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.