Office 365 authentication fails when a client user is outside the corporate network in Windows Server 2012 R2

Vrijedi za: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 FoundationWindows Server 2012 R2 Standard

Symptoms


Consider the following scenario:
  • You have a Windows Server 2012 R2-based server that has Active Directory Federation Services (AD FS) 3.0 installed.
  • You have Windows 7-based or Windows 8-based client computers.
  • The value of the NtlmOnlySupportedClientAtProxy property is set to TRUE on the server.
  • You try to edit or save a Microsoft Office document while you are using a client computer that is outside the corporate network.
In this scenario, Microsoft Office 365 authentication fails. 

Cause


This issue occurs because the AD FS proxy code looks for a "WWWAuthenticate" header in the Security Token Service (STS) response headers instead of in the request headers.

The Office 365 authentication component requests the AD FS proxy to use "negotiate" as the authentication mechanism between the Windows 7-based or Windows 8-based client computers. A WWWAuthenticate header is added to the request header. However, the proxy code looks for the header in the STS response headers instead of in the request headers. Therefore, the header cannot be found when the server tries to authenticate the client computer. Windows 7-based and Windows 8-based client computers cannot perform the Windows Challenge/Response (NTLM) authentication.

Resolution


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates