Summary
This article helps you resolve a problem in which signing in to Office 365, Azure, or Microsoft Intune by using single sign-on (SSO) doesn't work from some devices. This problem typically occurs in environments where Azure Seamless Single Sign-On is configured to use either Pass-through Authentication (PTA) or Password Hash Synchronization (PHS) for Active Directory domain-joined devices.
Symptoms
When you try to access a Microsoft cloud service like Office 365, Azure, or Intune through a web-based client or a rich client application by using a federated account, authentication fails from a specific client computer.
When you use a web browser to access the cloud service portal from the same computer by using a federated account, you experience one of the following symptoms:
-
You connect to the portal endpoint and receive one of the following error messages:
- Microsoft Edge cannot display the webpage.
- 403 Page Not Found
-
You connect to the Active Directory Federation Services (AD FS) endpoint and receive one of the following error messages:
- Microsoft Edge cannot display the webpage.
- 403 Page Not Found
-
You receive a certificate warning when you connect to the AD FS endpoint.
-
You connect to the AD FS endpoint while you're signed in to the corporate domain and receive a single credential prompt. This prompt doesn't use forms-based authentication.
-
You connect to the AD FS endpoint by using a third-party web browser and receive looping authentication prompts. These prompts don't use forms-based authentication.
-
You connect to the
login.microsoftonline.comendpoint and receive the following error message:- Access Denied
Cause
This problem usually occurs on a client computer or on a group of client devices. This problem might occur for all users and client computers if SSO isn't fully functional. SSO might not be fully functional if the client settings aren't correctly set up. The following client device situations can cause this issue:
-
Network connectivity is limited.
-
The client device receives incorrect name resolution for the AD FS service from the internal split-brain DNS implementation.
-
If you configure an internet proxy server on the computer, you don't add the AD FS name to the proxy bypass list.
-
You don't add the AD FS name to the local intranet security zone in the Internet Options settings.
-
The client computer isn't authenticated to Active Directory Domain Services (AD DS).
-
The third-party web browser doesn't support Extended Protection for Authentication to the AD FS service.
-
The federation metadata endpoint is hardcoded in the registry because of an earlier Office 365 Beta installation of the SSO Management tool.
-
The AD FS service endpoint that's required for a specific client application is disabled.
Before you continue, make sure that the following conditions are true:
-
Access problems aren't limited to rich client applications on the client computer. If only rich client authentication (as opposed to browser-based authentication) isn't working, this condition likely indicates a rich client authentication issue. For example, it might be an issue that's related to the prerequisites or configuration of the rich-client application. For more information, see How to troubleshoot non-browser apps that can't sign in to Office 365, Azure, or Intune.
-
SSO authentication doesn't fail for all SSO-enabled user accounts. If all SSO-enabled users experience the same symptoms, this condition likely indicates a federation issue. For more information, see Single sign-on doesn't work from some devices in Office 365, Azure, or Intune.
-
SSO authentication for the user account succeeds on other client computers. If the user account can't log on to any cloud services client, see the resolutions in this article that involve the client computer. There might also be some problem that affects the user account and not the client computer. For more information, see Troubleshoot account issues for federated users in Microsoft 365, Azure, or Intune.
-
The keyboard on the client computer is working correctly, and the user name and password are entered correctly.
Resolution
To troubleshoot this problem, use one or more of the following methods, depending on the cause of the problem.
Resolution 1: Can't connect to cloud service portal or AD FS
Try to browse to http://www.msn.com. If this attempt doesn't work, troubleshoot network connectivity issues. Follow these steps:
-
At a command prompt, use the ipconfig and ping tools to troubleshoot IP connectivity. For more information, see How to troubleshoot basic TCP/IP problems.
-
At a command prompt, enter
nslookup www.msn.comto determine whether DNS is resolving internet server names. -
Make sure that Internet Options proxy settings reflect the appropriate proxy server if a proxy server is used in the local network.
-
If a Forefront Threat Management Gateway (TMG) firewall is installed on the boundary of the network, and the firewall requires client authentication, you might have to install a Forefront TMG Client program on the client device for internet access. Contact your cloud service administrator if you need help.
Resolution 2: Can't connect to AD FS
To resolve this problem, follow these steps:
-
Eliminate IP connectivity problems by using Resolution 1.
-
At the command prompt, enter
nslookup <AD FS 2.0 FQDN>, and then press Enter to check if DNS is resolving the AD FS service name correctly.
Note: In this command,
<AD FS FQDN>represents the fully qualified domain name (FQDN) of the AD FS service name. It doesn't represent the Windows host name of the AD FS server.
If the client is connected to the corporate network, make sure that the IP address is a private IP address. The IP address should match one of the following patterns:
-
10.x.x.x -
172.16.x.x -
192.168.x.x
If the client is outside the corporate network, make sure that the IP address is a public IP address. Make sure that it doesn't match one of the following patterns:
-
10.x.x.x -
172.16.x.x -
192.168.x.x
If the IP address is incorrect based on the previous steps, and other client computers don't experience the same behavior, follow these steps:
-
At the command prompt, enter
ipconfig /all, and then check whether the Primary DNS Server entry is appropriate for the network to which the client is attached. -
Open the
%windir%\system32\drivers\etc\hostsfile in Notepad, and then remove any entries for the AD FS FQDN. Save the file. -
At the command prompt, enter
ipconfig /flushdnsto clear the DNS cache.
Note: If client devices are connected to only the corporate network, go to the next step.
- Add the AD FS FQDN to the proxy bypass list. For more information, see Proxy Support in Microsoft Edge.
Resolution 3: Certificate warning when you connect to the AD FS endpoint
To resolve this problem, troubleshoot Secure Sockets Layer (SSL) certificate issues. For more information, see You receive a certificate warning from AD FS when you try to sign in to Office 365, Azure, or Intune.
Resolution 4: You receive a single, unexpected credential prompt when you sign in from a client computer that's connected to the corporate network
To resolve this problem, follow these steps:
-
Make sure that the client computer is successfully signed in to the domain.
-
Select Start > Run, enter
%logonserver%\sysvol, and then select OK. If a credential prompt appears, sign out, and then sign back in by using corporate credentials. -
Add the AD FS FQDN to the local intranet zone.
-
On the Security tab, select Local Intranet > Sites > Advanced.
-
Examine the Websites listing for the fully qualified DNS name of the AD FS service endpoint (for example, sts.contoso.com).
[!NOTE] A wildcard value (for example, "*.consoto.com") also works in this configuration.
-
Add the AD FS FQDN to the proxy bypass list. For more information, see Proxy Support in Microsoft Edge.
Resolution 5: Third-party web browser doesn't support Extended Protection for Authentication, and you receive looping authentication prompts
To resolve this problem, follow these steps:
- Use Microsoft Edge instead of a third-party web browser that doesn't support Extended Protection for Authentication.
If Microsoft Edge isn't an option, see A federated user is repeatedly prompted for credentials during sign-in to Office 365, Azure, or Intune.
Resolution 6: "Access Denied" error message when you try to connect to login.microsoftonline.com
Important: This resolution contains steps that tell you how to modify the registry. Serious problems can occur if you modify the registry incorrectly. Be sure to back up the registry before you modify it. For more information, see How to back up and restore the registry in Windows.
To resolve this problem, use Registry Editor to delete the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\MOCHA\IdentityFederation
AD FS then falls back to the correct endpoint, based on the SSO Relying Party Trust.
Resolution 7: Reset disabled AD FS service endpoint setting to default configuration
For more information about how to do the reset, see Sign in to Office 365, Azure, or Intune fails after you change the federation service endpoint.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: kaushika-msft). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
