Merge pull request #188182 from v-missam/prodpad

doc-1

Author: v-ccolin

articles/active-directory/saas-apps/bullseyetdp-provisioning-tutorial.md

@@ -0,0 +1,146 @@
+---
+title: 'Tutorial: Configure BullseyeTDP for automatic user provisioning with Azure Active Directory | Microsoft Docs'
+description: Learn how to automatically provision and de-provision user accounts from Azure AD to BullseyeTDP.
+services: active-directory
+documentationcenter: ''
+author: twimmers
+writer: Thwimmer
+manager: beatrizd
+
+ms.assetid: a1a4e5ab-87ae-4cad-b187-cc474a8ea185
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.devlang: na
+ms.topic: article
+ms.date: 02/03/2022
+ms.author: Thwimmer
+---
+
+# Tutorial: Configure BullseyeTDP for automatic user provisioning
+
+This tutorial describes the steps you need to perform in both BullseyeTDP and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [BullseyeTDP](https://www.bullseyeengagement.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
+
+
+## Capabilities supported
+> [!div class="checklist"]
+> * Create users in BullseyeTDP.
+> * Remove users in BullseyeTDP when they do not require access anymore.
+> * Keep user attributes synchronized between Azure AD and BullseyeTDP.
+> * [Single sign-on](bullseyetdp-tutorial.md) to BullseyeTDP.
+
+## Prerequisites
+
+The scenario outlined in this tutorial assumes that you already have the following prerequisites:
+
+* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md). 
+* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
+* The Tenant URL and Secret Token.
+* Global Administrative rights for the Active Directory.
+* Access rights to set up Enterprise applications.
+
+
+## Step 1. Plan your provisioning deployment
+1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
+1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+1. Determine what data to [map between Azure AD and BullseyeTDP](../app-provisioning/customize-application-attributes.md). 
+
+## Step 2. Configure BullseyeTDP to support provisioning with Azure AD
+Contact to BullseyeTDP technical support team <[email protected]> in order to obtain a SCIM Token. Under the Admin Credentials section, enter `https://scim.bullseyeengagement.com/scim` in Tenant URL. Input the provided value in Secret Token.
+
+## Step 3. Add BullseyeTDP from the Azure AD application gallery
+
+Add BullseyeTDP from the Azure AD application gallery to start managing provisioning to BullseyeTDP. If you have previously setup BullseyeTDP for SSO, you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
+
+## Step 4. Define who will be in scope for provisioning 
+
+The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+* When assigning users and groups to BullseyeTDP, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add more roles. 
+
+* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+
+## Step 5. Configure automatic user provisioning to BullseyeTDP 
+
+This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in BullseyeTDP based on user and/or group assignments in Azure AD.
+
+### To configure automatic user provisioning for BullseyeTDP in Azure AD:
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
+
+	![Enterprise applications blade](common/enterprise-applications.png)
+
+1. In the applications list, select **BullseyeTDP**.
+
+	![The BullseyeTDP link in the Applications list](common/all-applications.png)
+
+1. Select the **Provisioning** tab.
+
+	![Provisioning tab](common/provisioning.png)
+
+1. Set the **Provisioning Mode** to **Automatic**.
+
+	![Provisioning tab automatic](common/provisioning-automatic.png)
+
+1. Under the **Admin Credentials** section, input your BullseyeTDP Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to BullseyeTDP. If the connection fails, ensure your BullseyeTDP account has Admin permissions and try again.
+
+ 	![Token](common/provisioning-testconnection-tenanturltoken.png)
+
+1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
+
+	![Notification Email](common/provisioning-notification-email.png)
+
+1. Select **Save**.
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to BullseyeTDP**.
+
+1. Review the user attributes that are synchronized from Azure AD to BullseyeTDP in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in BullseyeTDP for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the BullseyeTDP API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+
+   |Attribute|Type|Supported for filtering|Required by BullseyeTDP|
+   |---|---|---|---|
+   |userName|String|&check;|&check;
+   |externalId|String|&check;|&check;
+   |userType|String||&check;
+   |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager|String||
+   |active|Boolean||
+   |title|String||&check;
+   |emails[type eq "work"].value|String||&check;  
+   |name.givenName|String||&check; 
+   |name.familyName|String||&check; 
+   |addresses[type eq "work"].locality|String||&check;
+   |phoneNumbers[type eq "work"].value|String||
+   |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber|String||
+   |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department|String||&check;  
+
+1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+1. To enable the Azure AD provisioning service for BullseyeTDP, change the **Provisioning Status** to **On** in the **Settings** section.
+
+	![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
+
+1. Define the users and/or groups that you would like to provision to BullseyeTDP by choosing the desired values in **Scope** in the **Settings** section.
+
+	![Provisioning Scope](common/provisioning-scope.png)
+
+1. When you are ready to provision, click **Save**.
+
+	![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
+
+This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. 
+
+## Step 6. Monitor your deployment
+Once you've configured provisioning, use the following resources to monitor your deployment:
+
+* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
+* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it is to completion
+* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md). 
+
+## More resources
+
+* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
+* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+
+## Next steps
+
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/evercate-provisioning-tutorial.md

@@ -67,7 +67,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 
 ## Step 3. Add Evercate from the Azure AD application gallery
 
-Add Evercate from the Azure AD application gallery to start managing provisioning to Evercate. If you have previously setup Evercate for SSO, you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
+Add Evercate from the Azure AD application gallery to start managing provisioning to Evercate. If you have previously setup Evercate for SSO, you can use the same application. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
 
 ## Step 4. Define who will be in scope for provisioning 
 
@@ -100,7 +100,7 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 	![Provisioning tab automatic](common/provisioning-automatic.png)
 
-1. Under the **Admin Credentials** section, input your Evercate Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Evercate. If the connection fails, ensure your Evercate account has Admin permissions and try again.
+1. Under the **Admin Credentials** section, input your Evercate Tenant URL as `https://adscimprovisioning.evercate.com/scim` and corresponding Secret Token. Click **Test Connection** to ensure Azure AD can connect to Evercate. If the connection fails, ensure your Evercate account has Admin permissions and try again.
 
  	![Token](common/provisioning-testconnection-tenanturltoken.png)