Skip to main content
Sumo Logic

Integrate Sumo with Azure AD

Enable Single Sign-On (SSO)  to Sumo Logic with Azure Active Directory (AD).


Account Type Account Level
Cloud Flex Trial, Enterprise
Credits Trial, Essentials, Enterprise Operations, Enterprise Security, Enterprise Suite

Organizations with Enterprise accounts can provision Security Assertion Markup Language (SAML) 2.0 to enable Single Sign-On (SSO) for user access to Sumo Logic. This page has instructions for integrating Sumo with Azure AD.

Step 1: Configure Sumo as an Enterprise App in Azure AD

In this step you set up Sumo as a non-gallery Enterprise App in Azure AD.

  1. Go into the Microsoft Azure Management Console and select Azure Active Directory in the left-side navigation pane.
  2. Select Manage > Enterprise Applications in the Overview blade. 
  3. Select Manage > All Applications.
  4. Click New application at the top of the All applications blade. 
  5. Select Categories and then select ALL.
  6.  Select Non-gallery application. non-gallery-app.png
  7. On the Add your own application page give your application a name and click Add. Throughout this procedure, we refer to the application name as <app-name>.
  8. Select your new application from the applications list.
  9. In the left-side navigation pane, select Single sign-on.
  10. In the Single sign-on dialog, select SAML-based Sign-on.
  11. In the SAML Signing Certificate section, click the Download link for Certificate (Base64) to download the <app-name>.cer file.
  12. In the Set Up Sumo Logic section, copy and paste the the contents of the following fields into a text document. You will need these values when in the next step. 
    • Login URL
    • Azure AD identifier

    • Logout URL

Step 2: Configure SAML in Sumo

  1. Go to Administration > Security > SAML.
  2. Select an existing configuration, or click the plus (+) icon to create a new configuration.
  3. The Add Configuration page appears.
  4. Configuration Name. Enter a name to identify the SSO policy (or another name used internally to describe the policy).
  5. Debug Mode. Select this option if you'd like to view additional details if an error occurs when a user attempts to authenticate. For more information, see View SAML Debug Information.
  6. Issuer. Enter the Azure AD Identifier that you noted in the substep 12 of Step 1
  7. X.509 Certificate. Use a text editor to open the certificate file you downloaded in substep 11 of Step 1. Copy and paste the contents of the file into the field. 
  8. Attribute Mapping. Select Use SAML subject.
  9. Configure SP-initiated Login. (Optional) This step has instructions for setting up SP-initiated login. When SP-initiated login has been enabled, your SAML configuration will appear as an additional authentication option within your subdomain-enabled account login page.
    1. Click SP Initiated Login Configuration in the Optional Settings section of the SAML configuration page. When you click this option, the following configurations appear. 

    2. Login Path. Enter a unique identifier for your org. You can specify any alphanumeric string (with no embedded spaces), provided that it is unique to your org. (You can't configure a Login Path that another Sumo customer has already configured).  

    3. Authn Request URL. Enter the Login URL that you noted in the substep 12 of Step 1.

    4. Disable Requested Authn Context. Checkmark this option. 

    5. Sign Authn Request. (Optional) If you select this option, Sumo will send signed Authn requests to your IdP. When you click this option, a Sumo-provided X-509 certificate is displayed. You can configure your IDP with this certificate, to use to verify the signature of the Authn requests sent by Sumo. 

  10. Configure on-demand provisioning. (Optional) If you configure on-demand provisioning, Sumo Logic automatically creates a user account the first time a user logs on to Sumo.When the account is created, Sumo Logic credentials are emailed to the user. (Users need both Sumo Logic credentials and SAML permissions.) To complete this procedure, you  supply the First Name and Last Name attributes Azure AD uses to identify users.

    1. Click the On Demand Provisioning checkbox.
    2. First Name Attribute. You might need to provide the full attribute path, which can vary based on the ADFS version (the actual path can be seen in the SAML assertion). Here is an example:
    3. Last Name Attribute. You might need to provide the full attribute path, which can vary based on the ADFS version (the actual path can be seen in the SAML assertion). Here is an example:
    4. On Demand Provisioning Roles. Specify the Sumo RBAC roles you want to assign when user accounts are provisioned. (The roles must already exist.)
  11. Configure logout page. (Optional) Configure a logout page if you would like to point all Sumo users to a particular URL after logging out of Sumo Logic or after their session has timed out. You could choose your company's intranet, for example, or any other site that you'd prefer users in your organization access.
    1. Click the Logout Page checkbox.
    2. Enter the URL of the page to which you want to direct users after logging of Sumo.
  12. Click Add to save the configuration
  13. Select the new configuration from the Configuration List.
  14. Click Copy to copy the Assertion Consumer URL value, and save it in a text file.
  15. Click Copy to copy the Entity ID value, and save it in a text file. This field is only available when SP-initiated login is enabled.

Step 3: Complete Azure configuration

  1. In the Azure Management Console, select your application from the applications list. 
  2. From the left Menu select  Single sign-on for your application
  3. In Section 1, Basic SAML Configuration, edit the configuration.
    1. Identifier (Entity ID). Paste in the Entity ID you copied in substep 15 of Step 2
      If SP-initiated login has not been enabled, enter the service domain of your Sumo Logic account. ex. The easiest way to see which domain your account uses is to look at the Sumo Logic URL. If you see "us2" that means you're running on the US2 pod and the service domain would be If you see "eu" or "au" you're on one of those pods, it would be  or respectively. If none is seen, then it would be for the US1 deployment.
    2. Reply URL (Assertion Consumer URL). Paste in the Assertion Consumer URL you copied in substep 14 of Step 2.
    3. Click Save.
  4. In the left navigation pane, click  Properties in the Manage section.
    1. Enabled for users to sign in? Enter Yes. 
    2. User assignment required? Enter Yes. (This option controls whether a user must be assigned to this group or whether any user in the Azure AD tenant can use Sumo Logic. We recommend setting this to Yes as the Sumo environment has a finite number of users.
    3. Click Save.
  5. On the appname blade (the blade with the name of the selected app in the title), select Users and Groups.
  6. On the appname - User and Group Assignment blade, select the Add command
  7. On the Add Assignment blade, select Users and groups.
  8. On the Users and groups blade, select one or more users or groups from the list and then select the Select button at the bottom of the blade.
  9. On the Add Assignment blade, select Role. Then, on the Select Role blade, select a role to apply to the selected users or groups, and then select the OK button at the bottom of the blade.
  10. On the Add Assignment blade, select the Assign button at the bottom of the blade. The assigned users or groups have the permissions defined by the selected role.

Test SAML Authentication

  • Test IdP-initiated authentication. Login to with your Microsoft credentials and click the tile for the Sumo Logic application that you created above.
  • Test SP-initiated authentication. Point your browser to the URL for the HTTP redirect binding you obtained in the Login Path step (substep 9b) of Step 2, which looks like:


    deployment is your Sumo deployment, and

    OrganizationName is the Login Path you entered.