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

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.





Windows Server 2012 R2 file information notesImportant Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.16 xxx

    Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Microsoft.identityserver.proxyservice.exe

6.3.9600.16477

63,488

27-Nov-2013

15:33

x86

Microsoft.identityserver.proxyservice.exe.config

Not applicable

1,067

18-Jun-2013

14:55

Not applicable

Microsoft.identityserver.webhost.dll

6.3.9600.16392

172,032

31-Aug-2013

14:23

x86




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

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File property

Value

File name

Amd64_01f5ce74bdcbc4589be5b7ccbd393d70_31bf3856ad364e35_6.3.9600.16477_none_efe8eb19b27435c2.manifest

File version

Not applicable

File size

710

Date (UTC)

28-Nov-2013

Time (UTC)

01:03

File name

Amd64_b08f1d804fb2ba52c1a39f780276f717_31bf3856ad364e35_6.3.9600.16477_none_95426249afcc97f7.manifest

File version

Not applicable

File size

705

Date (UTC)

28-Nov-2013

Time (UTC)

01:03

File name

Msil_microsoft.identityserver.proxyservice_31bf3856ad364e35_6.3.9600.16477_none_46ee2d31e9308eb5.manifest

File version

Not applicable

File size

4,764

Date (UTC)

27-Nov-2013

Time (UTC)

16:14

File name

Msil_microsoft.identityserver.webhost_31bf3856ad364e35_6.3.9600.16477_none_7926ccd9e1870342.manifest

File version

Not applicable

File size

3,334

Date (UTC)

28-Nov-2013

Time (UTC)

01:03


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×