Skip to content

Commit 9891941

Browse files
authored
Merge pull request #103080 from v-hagamp/newrelic(limitedrelease)
Product Backlog Item 917872: SaaS App Tutorial: New Relic (Limited Re…
2 parents 395380f + 4bc2977 commit 9891941

File tree

2 files changed

+160
-0
lines changed

2 files changed

+160
-0
lines changed
Lines changed: 158 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,158 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with New Relic (Limited Release) | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and New Relic (Limited Release).
4+
services: active-directory
5+
documentationCenter: na
6+
author: jeevansd
7+
manager: mtillman
8+
ms.reviewer: barbkess
9+
10+
ms.assetid: 2ffbcf4a-b6b4-45ac-922f-358abe4c05e8
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.topic: tutorial
16+
ms.date: 02/04/2020
17+
ms.author: jeedes
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# Tutorial: Azure Active Directory single sign-on (SSO) integration with New Relic (Limited Release)
23+
24+
In this tutorial, you'll learn how to integrate New Relic (Limited Release) with Azure Active Directory (Azure AD). When you integrate New Relic (Limited Release) with Azure AD, you can:
25+
26+
* Control in Azure AD who has access to New Relic (Limited Release).
27+
* Enable your users to be automatically signed-in to New Relic (Limited Release) with their Azure AD accounts.
28+
* Manage your accounts in one central location - the Azure portal.
29+
30+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
31+
32+
## Prerequisites
33+
34+
To get started, you need the following items:
35+
36+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
37+
* New Relic (Limited Release) single sign-on (SSO) enabled subscription.
38+
39+
## Scenario description
40+
41+
In this tutorial, you configure and test Azure AD SSO in a test environment.
42+
43+
* New Relic (Limited Release) supports **IDP** initiated SSO
44+
45+
* Once you configure the New Relic you can enforce session controls, which protect exfiltration and infiltration of your organization’s sensitive data in real-time. Session controls extend from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-any-app).
46+
47+
## Adding New Relic (Limited Release) from the gallery
48+
49+
To configure the integration of New Relic (Limited Release) into Azure AD, you need to add New Relic (Limited Release) from the gallery to your list of managed SaaS apps.
50+
51+
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
52+
1. On the left navigation pane, select the **Azure Active Directory** service.
53+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
54+
1. To add new application, select **New application**.
55+
1. In the **Add from the gallery** section, type **New Relic (Limited Release)** in the search box.
56+
1. Select **New Relic (Limited Release)** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
57+
58+
59+
## Configure and test Azure AD single sign-on for New Relic (Limited Release)
60+
61+
Configure and test Azure AD SSO with New Relic (Limited Release) using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in New Relic (Limited Release).
62+
63+
To configure and test Azure AD SSO with New Relic (Limited Release), complete the following building blocks:
64+
65+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
66+
* **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
67+
* **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
68+
1. **[Configure New Relic (Limited Release) SSO](#configure-new-relic-limited-release-sso)** - to configure the single sign-on settings on application side.
69+
* **[Create New Relic (Limited Release) test user](#create-new-relic-limited-release-test-user)** - to have a counterpart of B.Simon in New Relic (Limited Release) that is linked to the Azure AD representation of user.
70+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
71+
72+
## Configure Azure AD SSO
73+
74+
Follow these steps to enable Azure AD SSO in the Azure portal.
75+
76+
1. In the [Azure portal](https://portal.azure.com/), on the **New Relic (Limited Release)** application integration page, find the **Manage** section and select **single sign-on**.
77+
1. On the **Select a single sign-on method** page, select **SAML**.
78+
1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
79+
80+
![Edit Basic SAML Configuration](common/edit-urls.png)
81+
82+
1. On the **Basic SAML Configuration** section, if you have **Service Provider metadata file**, perform the following steps:
83+
84+
a. Click **Upload metadata file**.
85+
86+
![image](common/upload-metadata.png)
87+
88+
b. Click on **folder logo** to select the metadata file and click **Upload**.
89+
90+
![image](common/browse-upload-metadata.png)
91+
92+
c. Once the metadata file is successfully uploaded, the **Identifier** and **Reply URL** values get auto populated in Basic SAML Configuration section:
93+
94+
![image](common/idp-intiated.png)
95+
96+
> [!Note]
97+
> If the **Identifier** and **Reply URL** values are not getting auto polulated, then fill in the values manually according to your requirement.
98+
99+
1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
100+
101+
![The Certificate download link](common/copy-metadataurl.png)
102+
103+
### Create an Azure AD test user
104+
105+
In this section, you'll create a test user in the Azure portal called B.Simon.
106+
107+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
108+
1. Select **New user** at the top of the screen.
109+
1. In the **User** properties, follow these steps:
110+
1. In the **Name** field, enter `B.Simon`.
111+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
112+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
113+
1. Click **Create**.
114+
115+
### Assign the Azure AD test user
116+
117+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to New Relic (Limited Release).
118+
119+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
120+
1. In the applications list, select **New Relic (Limited Release)**.
121+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
122+
123+
![The "Users and groups" link](common/users-groups-blade.png)
124+
125+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
126+
127+
![The Add User link](common/add-assign-user.png)
128+
129+
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
130+
1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
131+
1. In the **Add Assignment** dialog, click the **Assign** button.
132+
133+
## Configure New Relic (Limited Release) SSO
134+
135+
To configure single sign-on on **New Relic (Limited Release)** side, you need to send the **App Federation Metadata Url** to [New Relic (Limited Release) support team](https://support.newrelic.com/). They set this setting to have the SAML SSO connection set properly on both sides.
136+
137+
138+
### Create New Relic (Limited Release) test user
139+
140+
In this section, you create a user called B.Simon in New Relic (Limited Release). Work with [New Relic (Limited Release) support team](https://support.newrelic.com/) to add the users in the New Relic (Limited Release) platform. Users must be created and activated before you use single sign-on.
141+
142+
## Test SSO
143+
144+
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
145+
146+
When you click the New Relic (Limited Release) tile in the Access Panel, you should be automatically signed in to the New Relic (Limited Release) for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
147+
148+
## Additional resources
149+
150+
- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
151+
152+
- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
153+
154+
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
155+
156+
- [Try New Relic (Limited Release) with Azure AD](https://aad.portal.azure.com/)
157+
158+
- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)

articles/active-directory/saas-apps/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -960,6 +960,8 @@
960960
href: netsuite-tutorial.md
961961
- name: New Relic
962962
href: new-relic-tutorial.md
963+
- name: New Relic (Limited Release)
964+
href: new-relic-limited-release-tutorial.md
963965
- name: Nexonia
964966
href: nexonia-tutorial.md
965967
- name: Nimblex

0 commit comments

Comments
 (0)