Tutorial: Azure Active Directory single sign-on (SSO) integration with New Relic

In this tutorial, you'll learn how to integrate New Relic with Azure Active Directory (Azure AD). When you integrate New Relic with Azure AD, you can:

  • Control in Azure AD who has access to New Relic.
  • Enable your users to be automatically signed-in to New Relic with their Azure AD accounts.
  • Manage your accounts in one central location: the Azure portal.

Prerequisites

To get started, you need:

Scenario description

In this tutorial, you configure and test Azure AD SSO in a test environment.

  • New Relic supports SSO that's initiated by either the service provider or the identity provider.

  • New Relic supports Automated user provisioning.

To configure the integration of New Relic into Azure AD, you need to add New Relic (By Organization) from the gallery to your list of managed SaaS apps.

  1. Sign in to the Azure portal by using either a work or school account, or a personal Microsoft account.
  2. Select the Azure Active Directory service.
  3. Select Enterprise applications > New application.
  4. On the Browse Azure AD Gallery page, type New Relic (By Organization) in the search box.
  5. Select New Relic (By Organization) from the results, and then select Create. Wait a few seconds while the app is added to your tenant.

Configure and test Azure AD SSO for New Relic

Configure and test Azure AD SSO with New Relic by using a test user called B.Simon. For SSO to work, you need to establish a linked relationship between an Azure AD user and the related user in New Relic.

To configure and test Azure AD SSO with New Relic:

  1. Configure Azure AD SSO to enable your users to use this feature.
    1. Create an Azure AD test user to test Azure AD single sign-on with B.Simon.
    2. Assign the Azure AD test user to enable B.Simon to use Azure AD single sign-on.
  2. Configure New Relic SSO to configure the single sign-on settings on the New Relic side.
    1. Create a New Relic test user to have a counterpart for B.Simon in New Relic linked to the Azure AD user.
  3. Test SSO to verify whether the configuration works.

Configure Azure AD SSO

Follow these steps to enable Azure AD SSO in the Azure portal.

  1. In the Azure portal on the New Relic by Organization application integration page, find the Manage section. Then select Single sign-on.

  2. On the Select a single sign-on method page, select SAML.

  3. On the Set up Single Sign-On with SAML page, select the pencil icon for Basic SAML Configuration to edit the settings.

    Screenshot of Set up Single Sign-On with SAML, with pencil icon highlighted.

  4. In the Basic SAML Configuration section, fill in values for Identifier and Reply URL.

    • Retrieve these values from the New Relic authentication domain UI. From there:
      1. If you have more than one authentication domain, choose the one to which you want Azure AD SSO to connect. Most companies only have one authentication domain called Default. If there's only one authentication domain, you don't need to select anything.
      2. In the Authentication section, Assertion consumer URL contains the value to use for Reply URL.
      3. In the Authentication section, Our entity ID contains the value to use for Identifier.
  5. In the User Attributes & Claims section, make sure Unique User Identifier is mapped to a field that contains the email address being used at New Relic.

    • The default field user.userprincipalname will work for you if its values are the same as the New Relic email addresses.
    • The field user.mail might work better for you if user.userprincipalname isn't the New Relic email address.
  6. In the SAML Signing Certificate section, copy App Federation Metadata Url and save its value for later use.

  7. In the Set up New Relic by Organization section, copy Login URL and save its value for later use.

Create an Azure AD test user

In this section, you'll create a test user in the Azure portal called B.Simon.

  1. From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
  2. Select New user at the top of the screen.
  3. In the User properties, follow these steps:
    1. In the Name field, enter B.Simon.
    2. In the User name field, enter the username@companydomain.extension. For example, B.Simon@contoso.com.
    3. Select the Show password check box, and then write down the value that's displayed in the Password box.
    4. Click Create.

Assign the Azure AD test user

In this section, you'll enable B.Simon to use Azure single sign-on by granting access to New Relic.

  1. In the Azure portal, select Enterprise Applications, and then select All applications.
  2. In the applications list, select New Relic.
  3. In the app's overview page, find the Manage section and select Users and groups.
  4. Select Add user, then select Users and groups in the Add Assignment dialog.
  5. In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
  6. If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
  7. In the Add Assignment dialog, click the Assign button.

Configure New Relic SSO

Follow these steps to configure SSO at New Relic.

  1. Sign in to New Relic.

  2. Go to the authentication domain UI.

  3. Choose the authentication domain to which you want Azure AD SSO to connect (if you have more than one authentication domain). Most companies only have one authentication domain called Default. If there's only one authentication domain, you don't need to select anything.

  4. In the Authentication section, select Configure.

    1. For Source of SAML metadata, enter the value you previously saved from the Azure AD App Federation Metadata Url field.

    2. For SSO target URL, enter the value you previously saved from the Azure AD Login URL field.

    3. After verifying that settings look good on both the Azure AD and New Relic sides, select Save. If both sides are not properly configured, your users won't be able to sign in to New Relic.

Create a New Relic test user

In this section, you create a user called B.Simon in New Relic.

  1. Sign in to New Relic.

  2. Go to the User management UI.

  3. Select Add user.

    1. For Name, enter B.Simon.

    2. For Email, enter the value that will be sent by Azure AD SSO.

    3. Choose a user Type and a user Group for the user. For a test user, Basic user for Type and User for Group are reasonable choices.

    4. To save the user, select Add User.

Note

New Relic also supports automatic user provisioning, you can find more details here on how to configure automatic user provisioning.

Test SSO

In this section, you test your Azure AD single sign-on configuration with following options.

SP initiated:

  • Click on Test this application in Azure portal. This will redirect to New Relic Sign on URL where you can initiate the login flow.

  • Go to New Relic Sign-on URL directly and initiate the login flow from there.

IDP initiated:

  • Click on Test this application in Azure portal and you should be automatically signed in to the New Relic for which you set up the SSO.

You can also use Microsoft My Apps to test the application in any mode. When you click the New Relic tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the New Relic for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.

Next steps

Once done, you can verify that your users have been added in New Relic by going to the User management UI and seeing if they're there.

Next, you will probably want to assign your users to specific New Relic accounts or roles. To learn more about this, see User management concepts.

In New Relic's authentication domain UI, you can configure other settings, like session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Cloud App Security.