Merge pull request #170888 from bhavana-129/provisioning-2

v-albemi · web-flow · commit 806dc3cdc481 · 2021-09-07T13:38:48.000-07:00
SaaS App Tutorial: User provisioning connector-2
diff --git a/articles/active-directory/saas-apps/mypolicies-tutorial.md b/articles/active-directory/saas-apps/mypolicies-tutorial.md
@@ -9,92 +9,68 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 03/01/2019
+ms.date: 08/31/2021
 ms.author: jeedes
 ---
 # Tutorial: Azure Active Directory integration with myPolicies
 
-In this tutorial, you learn how to integrate myPolicies with Azure Active Directory (Azure AD).
-Integrating myPolicies with Azure AD provides you with the following benefits:
+In this tutorial, you'll learn how to integrate myPolicies with Azure Active Directory (Azure AD). When you integrate myPolicies with Azure AD, you can:
 
-* You can control in Azure AD who has access to myPolicies.
-* You can enable your users to be automatically signed-in to myPolicies (Single Sign-On) with their Azure AD accounts.
-* You can manage your accounts in one central location - the Azure portal.
-
-If you want to know more details about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](../manage-apps/what-is-single-sign-on.md).
-If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
+* Control in Azure AD who has access to myPolicies.
+* Enable your users to be automatically signed-in to myPolicies with their Azure AD accounts.
+* Manage your accounts in one central location - the Azure portal.
 
 ## Prerequisites
 
-To configure Azure AD integration with myPolicies, you need the following items:
+To get started, you need the following items:
 
-* An Azure AD subscription. If you don't have an Azure AD environment, you can get one-month trial [here](https://azure.microsoft.com/pricing/free-trial/)
-* myPolicies single sign-on enabled subscription
+* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
+* myPolicies single sign-on (SSO) enabled subscription.
 
 ## Scenario description
 
 In this tutorial, you configure and test Azure AD single sign-on in a test environment.
 
-* myPolicies supports **IDP** initiated SSO
-
-## Adding myPolicies from the gallery
-
-To configure the integration of myPolicies into Azure AD, you need to add myPolicies from the gallery to your list of managed SaaS apps.
-
-**To add myPolicies from the gallery, perform the following steps:**
-
-1. In the **[Azure portal](https://portal.azure.com)**, on the left navigation panel, click **Azure Active Directory** icon.
-
-	![The Azure Active Directory button](common/select-azuread.png)
-
-2. Navigate to **Enterprise Applications** and then select the **All Applications** option.
-
-	![The Enterprise applications blade](common/enterprise-applications.png)
-
-3. To add new application, click **New application** button on the top of dialog.
+* myPolicies supports **IDP** initiated SSO.
 
-	![The New application button](common/add-new-app.png)
+* myPolicies supports [Automated user provisioning](mypolicies-provisioning-tutorial.md).
 
-4. In the search box, type **myPolicies**, select **myPolicies** from result panel then click **Add** button to add the application.
+## Add myPolicies from the gallery
 
-	 ![myPolicies in the results list](common/search-new-app.png)
-
-## Configure and test Azure AD single sign-on
-
-In this section, you configure and test Azure AD single sign-on with myPolicies based on a test user called **Britta Simon**.
-For single sign-on to work, a link relationship between an Azure AD user and the related user in myPolicies needs to be established.
-
-To configure and test Azure AD single sign-on with myPolicies, you need to complete the following building blocks:
-
-1. **[Configure Azure AD Single Sign-On](#configure-azure-ad-single-sign-on)** - to enable your users to use this feature.
-2. **[Configure myPolicies Single Sign-On](#configure-mypolicies-single-sign-on)** - to configure the Single Sign-On settings on application side.
-3. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with Britta Simon.
-4. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable Britta Simon to use Azure AD single sign-on.
-5. **[Create myPolicies test user](#create-mypolicies-test-user)** - to have a counterpart of Britta Simon in myPolicies that is linked to the Azure AD representation of user.
-6. **[Test single sign-on](#test-single-sign-on)** - to verify whether the configuration works.
+To configure the integration of myPolicies into Azure AD, you need to add myPolicies from the gallery to your list of managed SaaS apps.
 
-### Configure Azure AD single sign-on
+1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
+1. On the left navigation pane, select the **Azure Active Directory** service.
+1. Navigate to **Enterprise Applications** and then select **All Applications**.
+1. To add new application, select **New application**.
+1. In the **Add from the gallery** section, type **myPolicies** in the search box.
+1. Select **myPolicies** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
-In this section, you enable Azure AD single sign-on in the Azure portal.
+## Configure and test Azure AD SSO for myPolicies
 
-To configure Azure AD single sign-on with myPolicies, perform the following steps:
+Configure and test Azure AD SSO with myPolicies 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 myPolicies.
 
-1. In the [Azure portal](https://portal.azure.com/), on the **myPolicies** application integration page, select **Single sign-on**.
+To configure and test Azure AD SSO with myPolicies, perform the following steps:
 
-    ![Configure single sign-on link](common/select-sso.png)
+1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
+    1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
+    1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
+1. **[Configure myPolicies SSO](#configure-mypolicies-sso)** - to configure the single sign-on settings on application side.
+    1. **[Create myPolicies test user](#create-mypolicies-test-user)** - to have a counterpart of B.Simon in myPolicies that is linked to the Azure AD representation of user.
+1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
 
-2. On the **Select a Single sign-on method** dialog, select **SAML/WS-Fed** mode to enable single sign-on.
+## Configure Azure AD SSO
 
-    ![Single sign-on select mode](common/select-saml-option.png)
+Follow these steps to enable Azure AD SSO in the Azure portal.
 
-3. On the **Set up Single Sign-On with SAML** page, click **Edit** icon to open **Basic SAML Configuration** dialog.
+1. In the Azure portal, on the **myPolicies** application integration page, find the **Manage** section and select **single sign-on**.
+1. On the **Select a single sign-on method** page, select **SAML**.
+1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
 
-	![Edit Basic SAML Configuration](common/edit-urls.png)
+   ![Edit Basic SAML Configuration](common/edit-urls.png)
 
 4. On the **Set up Single Sign-On with SAML** page, perform the following steps:
 
-    ![myPolicies Domain and URLs single sign-on information](common/idp-intiated.png)
-
     a. In the **Identifier** text box, type a URL using the following pattern:
     `https://<tenantname>.mypolicies.com/`
 
@@ -112,81 +88,48 @@ To configure Azure AD single sign-on with myPolicies, perform the following step
 
 	![Copy configuration URLs](common/copy-configuration-urls.png)
 
-	a. Login URL
-
-	b. Azure AD Identifier
-
-	c. Logout URL
-
-### Configure myPolicies Single Sign-On
-
-To configure single sign-on on **myPolicies** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [myPolicies support team](mailto:support@mypolicies.com). They set this setting to have the SAML SSO connection set properly on both sides.
-
 ### Create an Azure AD test user 
 
-The objective of this section is to create a test user in the Azure portal called Britta Simon.
-
-1. In the Azure portal, in the left pane, select **Azure Active Directory**, select **Users**, and then select **All users**.
-
-    ![The "Users and groups" and "All users" links](common/users.png)
-
-2. Select **New user** at the top of the screen.
-
-    ![New user Button](common/new-user.png)
-
-3. In the User properties, perform the following steps.
-
-    ![The User dialog box](common/user-properties.png)
-
-    a. In the **Name** field enter **BrittaSimon**.
-  
-    b. In the **User name** field type **brittasimon\@yourcompanydomain.extension**  
-    For example, BrittaSimon@contoso.com
-
-    c. Select **Show password** check box, and then write down the value that's displayed in the Password box.
+In this section, you'll create a test user in the Azure portal called B.Simon.
 
-    d. Click **Create**.
+1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
+1. Select **New user** at the top of the screen.
+1. In the **User** properties, follow these steps:
+   1. In the **Name** field, enter `B.Simon`.  
+   1. In the **User name** field, enter the username@companydomain.extension. For example, `B.Simon@contoso.com`.
+   1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
+   1. Click **Create**.
 
 ### Assign the Azure AD test user
 
-In this section, you enable Britta Simon to use Azure single sign-on by granting access to myPolicies.
+In this section, you'll enable B.Simon to use Azure single sign-on by granting access to myPolicies.
 
-1. In the Azure portal, select **Enterprise Applications**, select **All applications**, then select **myPolicies**.
+1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
+1. In the applications list, select **myPolicies**.
+1. In the app's overview page, find the **Manage** section and select **Users and groups**.
+1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
+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.
+1. 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.
+1. In the **Add Assignment** dialog, click the **Assign** button.
 
-	![Enterprise applications blade](common/enterprise-applications.png)
+## Configure myPolicies SSO
 
-2. In the applications list, select **myPolicies**.
-
-	![The myPolicies link in the Applications list](common/all-applications.png)
-
-3. In the menu on the left, select **Users and groups**.
-
-    ![The "Users and groups" link](common/users-groups-blade.png)
-
-4. Click the **Add user** button, then select **Users and groups** in the **Add Assignment** dialog.
-
-    ![The Add Assignment pane](common/add-assign-user.png)
-
-5. In the **Users and groups** dialog select **Britta Simon** in the Users list, then click the **Select** button at the bottom of the screen.
-
-6. If you are expecting any role value in the SAML assertion then in the **Select Role** dialog select the appropriate role for the user from the list, then click the **Select** button at the bottom of the screen.
-
-7. In the **Add Assignment** dialog click the **Assign** button.
+To configure single sign-on on **myPolicies** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [myPolicies support team](mailto:support@mypolicies.com). They set this setting to have the SAML SSO connection set properly on both sides.
 
 ### Create myPolicies test user
 
 In this section, you create a user called Britta Simon in myPolicies. Work with [myPolicies support team](mailto:support@mypolicies.com) to add the users in the myPolicies platform. Users must be created and activated before you use single sign-on.
 
-### Test single sign-on 
+myPolicies also supports automatic user provisioning, you can find more details [here](./mypolicies-provisioning-tutorial.md) on how to configure automatic user provisioning.
 
-In this section, you test your Azure AD single sign-on configuration using the Access Panel.
+## Test SSO
 
-When you click the myPolicies tile in the Access Panel, you should be automatically signed in to the myPolicies for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](../user-help/my-apps-portal-end-user-access.md).
+In this section, you test your Azure AD single sign-on configuration with following options.
 
-## Additional Resources
+* Click on Test this application in Azure portal and you should be automatically signed in to the myPolicies for which you set up the SSO.
 
-- [List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](./tutorial-list.md)
+* You can use Microsoft My Apps. When you click the myPolicies tile in the My Apps, you should be automatically signed in to the myPolicies for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
 
-- [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+## Next steps
 
-- [What is Conditional Access in Azure Active Directory?](../conditional-access/overview.md)
+Once you configure myPolicies you can enforce 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](/cloud-app-security/proxy-deployment-aad).
diff --git a/articles/active-directory/saas-apps/new-relic-limited-release-tutorial.md b/articles/active-directory/saas-apps/new-relic-limited-release-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 04/13/2021
+ms.date: 08/31/2021
 ms.author: jeedes
 ---
 
@@ -34,6 +34,8 @@ 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](new-relic-by-organization-provisioning-tutorial.md).
+
 ## Add New Relic from the gallery
 
 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.
@@ -145,6 +147,9 @@ In this section, you create a user called B.Simon in New Relic.
    
    1. To save the user, select **Add User**.
 
+> [!NOTE]
+> New Relic also supports automatic user provisioning, you can find more details [here](./new-relic-by-organization-provisioning-tutorial.md) on how to configure automatic user provisioning.
+
 ## Test SSO 
 
 In this section, you test your Azure AD single sign-on configuration with following options. 
diff --git a/articles/active-directory/saas-apps/olfeo-saas-tutorial.md b/articles/active-directory/saas-apps/olfeo-saas-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 01/27/2021
+ms.date: 08/31/2021
 ms.author: jeedes
 
 ---
@@ -33,7 +33,9 @@ To get started, you need the following items:
 
 In this tutorial, you configure and test Azure AD SSO in a test environment.
 
-* Olfeo SAAS supports **SP** initiated SSO
+* Olfeo SAAS supports **SP** initiated SSO.
+
+* Olfeo SAAS supports [Automated user provisioning](olfeo-saas-provisioning-tutorial.md).
 
 ## Adding Olfeo SAAS from the gallery
 
@@ -46,7 +48,6 @@ To configure the integration of Olfeo SAAS into Azure AD, you need to add Olfeo
 1. In the **Add from the gallery** section, type **Olfeo SAAS** in the search box.
 1. Select **Olfeo SAAS** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
 
-
 ## Configure and test Azure AD SSO for Olfeo SAAS
 
 Configure and test Azure AD SSO with Olfeo SAAS 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 Olfeo SAAS.
@@ -120,6 +121,8 @@ To configure single sign-on on **Olfeo SAAS** side, you need to send the **App F
 
 In this section, you create a user called Britta Simon in Olfeo SAAS. Work with [Olfeo SAAS support team](mailto:equipe-rd@olfeo.com) to add the users in the Olfeo SAAS platform. Users must be created and activated before you use single sign-on.
 
+Olfeo SAAS also supports automatic user provisioning, you can find more details [here](./olfeo-saas-provisioning-tutorial.md) on how to configure automatic user provisioning.
+
 ## Test SSO 
 
 In this section, you test your Azure AD single sign-on configuration with following options. 
@@ -130,7 +133,6 @@ In this section, you test your Azure AD single sign-on configuration with follow
 
 * You can use Microsoft My Apps. When you click the Olfeo SAAS tile in the My Apps, this will redirect to Olfeo SAAS Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md).
 
-
 ## Next steps
 
 Once you configure Olfeo SAAS you can enforce 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](/cloud-app-security/proxy-deployment-any-app).
diff --git a/articles/active-directory/saas-apps/opentext-directory-services-tutorial.md b/articles/active-directory/saas-apps/opentext-directory-services-tutorial.md
@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 06/22/2021
+ms.date: 08/31/2021
 ms.author: jeedes
 ---
 
@@ -34,6 +34,7 @@ In this tutorial, you configure and test Azure AD SSO in a test environment.
 
 * OpenText Directory Services supports **SP and IDP** initiated SSO.
 * OpenText Directory Services supports **Just In Time** user provisioning.
+* OpenText Directory Services supports [Automated user provisioning](open-text-directory-services-provisioning-tutorial.md).
 
 ## Add OpenText Directory Services from the gallery
 
@@ -142,6 +143,9 @@ To configure single sign-on on **OpenText Directory Services** side, you need to
 
 In this section, a user called B.Simon is created in OpenText Directory Services. OpenText Directory Services supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in OpenText Directory Services, a new one is created after authentication.
 
+> [!NOTE]
+> OpenText Directory Services also supports automatic user provisioning, you can find more details [here](./open-text-directory-services-provisioning-tutorial.md) on how to configure automatic user provisioning.
+
 ## Test SSO 
 
 In this section, you test your Azure AD single sign-on configuration with following options. 
