Skip to main content

Setting Up SSO with Azure Active Directory

Product Enablement avatar
Written by Product Enablement
Updated over a month ago

This guide walks you through configuring Single Sign-On (SSO) between ObservePoint and Azure Active Directory using SAML 2.0.

Prerequisites

  • Admin access to your Azure Active Directory account

  • Admin access to your ObservePoint account

  • Access to start an SSO configuration in ObservePoint

Step 1: Start SSO Configuration in ObservePoint

  1. Log into ObservePoint as an Account Admin

  2. Navigate to Settings > Single Sign-on

  3. Click to start a new SSO configuration

Step 2: Create Enterprise Application in Azure

  1. Sign into the Azure Portal

  2. Navigate to Azure Active Directory > Enterprise Applications > All Applications

  3. Click New Application

  4. Click Create your own application at the top

  5. Give your application a name (e.g., "ObservePoint")

  6. Make sure Integrate any other application you don't find in the gallery (Non-gallery) is selected

  7. Click Create

Step 3: Configure SAML Single Sign-On

  1. Once your application is created, click the "getting started" link inside the box named "Set up single sign on".

  2. Select SAML as your SSO method.

Step 4: Configure Basic SAML Settings

  1. Click Edit on Section 1: Basic SAML Configuration

  2. Identifier (Entity ID): Copy values from ObservePoint

  3. Reply URL (Assertion Consumer Service URL): Copy values from ObservePoint

  4. Click Save and close the Basic SAML Configuration panel

  5. Note: You do not need to edit Section 2 (User Attributes & Claims) or other sections. The default Azure claims align with ObservePoint's requirements.

Step 5: Assign Users and Groups

  1. Click Users and groups in the left navigation

  2. Click Add user/group near the top

  3. Under Users, click None Selected

  4. Search for and select the users who need access to ObservePoint

  5. Click Select at the bottom

  6. Click Assign to complete the assignment

Step 6: Get the Federation Metadata URL

  1. Return to Single sign-on in the left navigation

  2. Scroll to Section 3: SAML Certificates

  3. Copy the App Federation Metadata URL

Step 7: Complete ObservePoint Configuration

  1. Return to the ObservePoint SSO configuration screen

  2. Paste the Azure App Federation Metadata URL into the configuration field

  3. ObservePoint will validate the URL and retrieve all necessary configuration data

  4. Click Next

Step 8: Configure ObservePoint SSO Settings

  1. Choose an account subdomain for SSO login (e.g., yourcompany.app.observepoint.com)

  2. User provisioning: Choose whether to automatically create ObservePoint accounts for users who don't already exist

    • Users are matched by email address from your identity provider

    • If auto-provisioning for new users is disabled, users must have an existing ObservePoint account before logging in via SSO

Step 9: Test and Activate

  1. Click Test SSO, then LAUNCH SSO TEST

  2. Verify that you can successfully authenticate

  3. If the test is successful, click Activate to enable SSO for your account

Your Azure AD SSO integration is now live login using your custom subdomain!

Advanced Features

Once your basic SSO setup is complete, you can configure these additional features:

  • Require signed SAMLRequests: Enhanced security requiring Azure AD to import ObservePoint's certificate from the metadata file

  • Single Sign-On (SSO): Allow users to launch ObservePoint directly from the Azure portal or My Apps

  • Single Logout (SLO): When a user's Azure AD session ends, their ObservePoint session will also end

    • Note: ObservePoint will not terminate the Azure AD session

Troubleshooting

If you encounter issues:

  • Verify that the App Federation Metadata URL is correct and accessible

  • Ensure users are properly assigned to the enterprise application

  • Check that email addresses match between Azure AD and ObservePoint

  • Confirm that your subdomain is unique and available

  • Review the SAML assertions to ensure claims are being sent correctly

Did this answer your question?