Problems signing in to SAML-based single sign-on configured apps

To troubleshoot the sign-in issues below, we recommend the following to better diagnosis and automate the resolution steps:

If you use the testing experience in the Azure portal with the My Apps Secure Browser Extension, you don't need to manually follow the steps below to open the SAML-based single sign-on configuration page.

To open the SAML-based single sign-on configuration page:

  1. Open the Azure portal and sign in as a Global Administrator or Coadmin.

  2. Open the Azure Active Directory Extension by selecting All services at the top of the main left-hand navigation menu.

  3. Type “Azure Active Directory" in the filter search box and select the Azure Active Directory item.

  4. Select Enterprise Applications from the Azure Active Directory left-hand navigation menu.

  5. Select All Applications to view a list of all your applications.

    If you do not see the application you want show up here, use the Filter control at the top of the All Applications List and set the Show option to All Applications.

  6. Select the application you want to configure for single sign-on.

  7. Once the application loads, select Single sign-on from the application’s left-hand navigation menu.

  8. Select SAML-based SSO.

General troubleshooting

Problem when customizing the SAML claims sent to an application

To learn how to customize the SAML attribute claims sent to your application, see Claims mapping in Azure Active Directory.

Verify both the configurations in the portal match what you have in your app. Specifically, compare Client/Application ID, Reply URLs, Client Secrets/Keys, and App ID URI.

Compare the resource you’re requesting access to in code with the configured permissions in the Required Resources tab to make sure you only request resources you’ve configured.