|
| 1 | +--- |
| 2 | +title: 'Tutorial: Configure TAP App Security for automatic user provisioning with Azure Active Directory | Microsoft Docs' |
| 3 | +description: Learn how to automatically provision and de-provision user accounts from Azure AD to TAP App Security. |
| 4 | +services: active-directory |
| 5 | +documentationcenter: '' |
| 6 | +author: twimmers |
| 7 | +writer: Thwimmer |
| 8 | +manager: beatrizd |
| 9 | + |
| 10 | +ms.assetid: affd297c-2b6f-4dc2-b4c3-d29458cf4b1b |
| 11 | +ms.service: active-directory |
| 12 | +ms.subservice: saas-app-tutorial |
| 13 | +ms.workload: identity |
| 14 | +ms.devlang: na |
| 15 | +ms.topic: article |
| 16 | +ms.date: 02/03/2022 |
| 17 | +ms.author: Thwimmer |
| 18 | +--- |
| 19 | + |
| 20 | +# Tutorial: Configure TAP App Security for automatic user provisioning |
| 21 | + |
| 22 | +This tutorial describes the steps you need to perform in both TAP App Security and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [TAP App Security](https://tapappsecurity.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). |
| 23 | + |
| 24 | + |
| 25 | +## Capabilities supported |
| 26 | +> [!div class="checklist"] |
| 27 | +> * Create users in TAP App Security. |
| 28 | +> * Remove users in TAP App Security when they do not require access anymore. |
| 29 | +> * Keep user attributes synchronized between Azure AD and TAP App Security. |
| 30 | +> * [Single sign-on](tap-app-security-tutorial.md) to TAP App Security. |
| 31 | +
|
| 32 | +## Prerequisites |
| 33 | + |
| 34 | +The scenario outlined in this tutorial assumes that you already have the following prerequisites: |
| 35 | + |
| 36 | +* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md). |
| 37 | +* 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). |
| 38 | +* A user account in TAP App Security with Admin permissions. |
| 39 | + |
| 40 | + |
| 41 | +## Step 1. Plan your provisioning deployment |
| 42 | +1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md). |
| 43 | +1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). |
| 44 | +1. Determine what data to [map between Azure AD and TAP App Security](../app-provisioning/customize-application-attributes.md). |
| 45 | + |
| 46 | +## Step 2. Configure TAP App Security to support provisioning with Azure AD |
| 47 | + |
| 48 | +Contact [TAP App Security support ](mailto:[email protected]) in order to obtain a SCIM Token. |
| 49 | + |
| 50 | + |
| 51 | +## Step 3. Add TAP App Security from the Azure AD application gallery |
| 52 | + |
| 53 | +Add TAP App Security from the Azure AD application gallery to start managing provisioning to TAP App Security. If you have previously setup TAP App Security 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). |
| 54 | + |
| 55 | +## Step 4. Define who will be in scope for provisioning |
| 56 | + |
| 57 | +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). |
| 58 | + |
| 59 | +* When assigning users and groups to TAP App Security, 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. |
| 60 | + |
| 61 | +* 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). |
| 62 | + |
| 63 | + |
| 64 | +## Step 5. Configure automatic user provisioning to TAP App Security |
| 65 | + |
| 66 | +This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TAP App Security based on user and/or group assignments in Azure AD. |
| 67 | + |
| 68 | +### To configure automatic user provisioning for TAP App Security in Azure AD: |
| 69 | + |
| 70 | +1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**. |
| 71 | + |
| 72 | +  |
| 73 | + |
| 74 | +1. In the applications list, select **TAP App Security**. |
| 75 | + |
| 76 | +  |
| 77 | + |
| 78 | +1. Select the **Provisioning** tab. |
| 79 | + |
| 80 | +  |
| 81 | + |
| 82 | +1. Set the **Provisioning Mode** to **Automatic**. |
| 83 | + |
| 84 | +  |
| 85 | + |
| 86 | +1. Under the **Admin Credentials** section, input your TAP App Security Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to TAP App Security. If the connection fails, ensure your TAP App Security account has Admin permissions and try again. |
| 87 | + |
| 88 | +  |
| 89 | + |
| 90 | +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. |
| 91 | + |
| 92 | +  |
| 93 | + |
| 94 | +1. Select **Save**. |
| 95 | + |
| 96 | +1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to TAP App Security**. |
| 97 | + |
| 98 | +1. Review the user attributes that are synchronized from Azure AD to TAP App Security in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in TAP App Security 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 TAP App Security API supports filtering users based on that attribute. Select the **Save** button to commit any changes. |
| 99 | + |
| 100 | + |Attribute|Type|Supported for filtering|Required by TAP App Security| |
| 101 | + |---|---|---|---| |
| 102 | + |userName|String|✓|✓ |
| 103 | + |active|Boolean||✓ |
| 104 | + |phoneNumbers[type eq "mobile"].value|String|| |
| 105 | + |displayName|String||✓ |
| 106 | + |title|String||✓ |
| 107 | + |
| 108 | +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). |
| 109 | + |
| 110 | +1. To enable the Azure AD provisioning service for TAP App Security, change the **Provisioning Status** to **On** in the **Settings** section. |
| 111 | + |
| 112 | +  |
| 113 | + |
| 114 | +1. Define the users and/or groups that you would like to provision to TAP App Security by choosing the desired values in **Scope** in the **Settings** section. |
| 115 | + |
| 116 | +  |
| 117 | + |
| 118 | +1. When you are ready to provision, click **Save**. |
| 119 | + |
| 120 | +  |
| 121 | + |
| 122 | +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. |
| 123 | + |
| 124 | +## Step 6. Monitor your deployment |
| 125 | +Once you've configured provisioning, use the following resources to monitor your deployment: |
| 126 | + |
| 127 | +* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully |
| 128 | +* 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 |
| 129 | +* 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). |
| 130 | + |
| 131 | +## More resources |
| 132 | + |
| 133 | +* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md) |
| 134 | +* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md) |
| 135 | + |
| 136 | +## Next steps |
| 137 | + |
| 138 | +* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md) |
0 commit comments