|
| 1 | +--- |
| 2 | +title: 'Tutorial: Configure Zapier 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 Zapier. |
| 4 | +services: active-directory |
| 5 | +documentationcenter: '' |
| 6 | +author: Zhchia |
| 7 | +writer: Zhchia |
| 8 | +manager: beatrizd |
| 9 | + |
| 10 | +ms.assetid: 66e224f9-2311-4564-bb84-99fce59a398f |
| 11 | +ms.service: active-directory |
| 12 | +ms.subservice: saas-app-tutorial |
| 13 | +ms.workload: identity |
| 14 | +ms.tgt_pltfrm: na |
| 15 | +ms.devlang: na |
| 16 | +ms.topic: article |
| 17 | +ms.date: 01/24/2020 |
| 18 | +ms.author: Zhchia |
| 19 | +--- |
| 20 | + |
| 21 | +# Tutorial: Configure Zapier for automatic user provisioning |
| 22 | + |
| 23 | +This tutorial describes the steps you need to perform in both Zapier and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Zapier](https://zapier.com/pricing) 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](../manage-apps/user-provisioning.md). |
| 24 | + |
| 25 | + |
| 26 | +## Capabilities supported |
| 27 | +> [!div class="checklist"] |
| 28 | +> * Create users in Zapier |
| 29 | +> * Remove users in Zapier when they do not require access anymore |
| 30 | +> * Keep user attributes synchronized between Azure AD and Zapier |
| 31 | +> * Provision groups and group memberships in Zapier |
| 32 | +> * Single sign-on to Zapier (recommended) |
| 33 | +
|
| 34 | +## Prerequisites |
| 35 | + |
| 36 | +The scenario outlined in this tutorial assumes that you already have the following prerequisites: |
| 37 | + |
| 38 | +* [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) |
| 39 | +* A user account in Azure AD with [permission](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles) to configure provisioning (e.g. Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). |
| 40 | +* A user account in Zapier with Admin permissions. |
| 41 | + |
| 42 | +## Step 1. Plan your provisioning deployment |
| 43 | +1. Learn about [how the provisioning service works](https://docs.microsoft.com/azure/active-directory/manage-apps/user-provisioning). |
| 44 | +2. Determine who will be in [scope for provisioning](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). |
| 45 | +3. Determine what data to [map between Azure AD and Zapier](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes). |
| 46 | + |
| 47 | +## Step 2. Configure Zapier to support provisioning with Azure AD |
| 48 | + |
| 49 | +1. Sign in to your [Zapier Admin Console](https://zapier.com/app/login/). Navigate to **Settings** under the tenant ID. |
| 50 | + |
| 51 | +  |
| 52 | + |
| 53 | +2. Under **COMPANY SETTINGS**, Select **User provisioning**. |
| 54 | + |
| 55 | +  |
| 56 | + |
| 57 | +3. Copy the **SCIM Base URL** and **SCIM Bearer Token**. These values will be entered in the Tenant URL and Secret Token fields respectively in the Provisioning tab of your Zapier application in the Azure portal. |
| 58 | + |
| 59 | +  |
| 60 | + |
| 61 | +## Step 3. Add Zapier from the Azure AD application gallery |
| 62 | + |
| 63 | +Add Zapier from the Azure AD application gallery to start managing provisioning to Zapier. If you have previously setup Zapier 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](https://docs.microsoft.com/azure/active-directory/manage-apps/add-gallery-app). |
| 64 | + |
| 65 | +## Step 4. Define who will be in scope for provisioning |
| 66 | + |
| 67 | +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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). |
| 68 | + |
| 69 | +* When assigning users and groups to Zapier, 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](https://docs.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps) to add additional roles. |
| 70 | + |
| 71 | +* 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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). |
| 72 | + |
| 73 | + |
| 74 | +## Step 5. Configure automatic user provisioning to Zapier |
| 75 | + |
| 76 | +This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD. |
| 77 | + |
| 78 | +### To configure automatic user provisioning for Zapier in Azure AD: |
| 79 | + |
| 80 | +1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**. |
| 81 | + |
| 82 | +  |
| 83 | + |
| 84 | +2. In the applications list, select **Zapier**. |
| 85 | + |
| 86 | +  |
| 87 | + |
| 88 | +3. Select the **Provisioning** tab. |
| 89 | + |
| 90 | +  |
| 91 | + |
| 92 | +4. Set the **Provisioning Mode** to **Automatic**. |
| 93 | + |
| 94 | +  |
| 95 | + |
| 96 | +5. Under the **Admin Credentials** section, input your Zapier **Tenant URL** and **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to Zapier. If the connection fails, ensure your Zapier account has Admin permissions and try again. |
| 97 | + |
| 98 | +  |
| 99 | + |
| 100 | +6. 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. |
| 101 | + |
| 102 | +  |
| 103 | + |
| 104 | +7. Select **Save**. |
| 105 | + |
| 106 | +8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Zapier**. |
| 107 | + |
| 108 | +9. Review the user attributes that are synchronized from Azure AD to Zapier in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Zapier for update operations. If you choose to change the [matching target attribute](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes), you will need to ensure that the Zapier API supports filtering users based on that attribute. Select the **Save** button to commit any changes. |
| 109 | + |
| 110 | + |Variable|Type| |
| 111 | + |---|---| |
| 112 | + |userName|String| |
| 113 | + |active|Boolean| |
| 114 | + |externalId|String| |
| 115 | + |name.givenName|String| |
| 116 | + |name.familyName|String| |
| 117 | + |emails[type eq "work"].value|String| |
| 118 | + |
| 119 | +10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Zapier**. |
| 120 | + |
| 121 | +11. Review the group attributes that are synchronized from Azure AD to Zapier in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Zapier for update operations. Select the **Save** button to commit any changes. |
| 122 | + |
| 123 | + |Variable|Type| |
| 124 | + |---|---| |
| 125 | + |displayName|String| |
| 126 | + |members|Reference| |
| 127 | + |
| 128 | +12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../manage-apps/define-conditional-rules-for-provisioning-user-accounts.md). |
| 129 | + |
| 130 | +13. To enable the Azure AD provisioning service for Zapier, change the **Provisioning Status** to **On** in the **Settings** section. |
| 131 | + |
| 132 | +  |
| 133 | + |
| 134 | +14. Define the users and/or groups that you would like to provision to Zapier by choosing the desired values in **Scope** in the **Settings** section. |
| 135 | + |
| 136 | +  |
| 137 | + |
| 138 | +15. When you are ready to provision, click **Save**. |
| 139 | + |
| 140 | +  |
| 141 | + |
| 142 | +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. |
| 143 | + |
| 144 | +## Step 6. Monitor your deployment |
| 145 | +Once you've configured provisioning, use the following resources to monitor your deployment: |
| 146 | + |
| 147 | +- Use the [provisioning logs](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-provisioning-logs) to determine which users have been provisioned successfully or unsuccessfully |
| 148 | +- Check the [progress bar](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-when-will-provisioning-finish-specific-user) to see the status of the provisioning cycle and how close it is to completion |
| 149 | +- If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-quarantine-status). |
| 150 | + |
| 151 | +## Additional resources |
| 152 | + |
| 153 | +* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md) |
| 154 | +* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md) |
| 155 | + |
| 156 | +## Next steps |
| 157 | + |
| 158 | +* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md) |
0 commit comments