|
| 1 | +--- |
| 2 | +title: 'Tutorial: Configure Juno Journey 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 Juno Journey. |
| 4 | +services: active-directory |
| 5 | +documentationcenter: '' |
| 6 | +author: zchia |
| 7 | +writer: zchia |
| 8 | +manager: beatrizd |
| 9 | + |
| 10 | +ms.assetid: 79813b19-c96e-4459-a4e5-636a6b6f5041 |
| 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: 04/16/2020 |
| 18 | +ms.author: Zhchia |
| 19 | +--- |
| 20 | + |
| 21 | +# Tutorial: Configure Juno Journey for automatic user provisioning |
| 22 | + |
| 23 | +This tutorial describes the steps you need to perform in both Juno Journey and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Juno Journey](https://www.junojourney.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](../manage-apps/user-provisioning.md). |
| 24 | + |
| 25 | + |
| 26 | +## Capabilities supported |
| 27 | +> [!div class="checklist"] |
| 28 | +> * Create users in Juno Journey |
| 29 | +> * Remove users in Juno Journey when they do not require access anymore |
| 30 | +> * Keep user attributes synchronized between Azure AD and Juno Journey |
| 31 | +> * [Single sign-on](https://docs.microsoft.com/azure/active-directory/saas-apps/juno-journey-tutorial) to Juno Journey (recommended) |
| 32 | +
|
| 33 | +## Prerequisites |
| 34 | + |
| 35 | +The scenario outlined in this tutorial assumes that you already have the following prerequisites: |
| 36 | + |
| 37 | +* [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) |
| 38 | +* 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). |
| 39 | +* A [Juno Journey tenant](https://www.junojourney.com/getstartedwithjuno). |
| 40 | +* A user account in Juno Journey 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 Juno Journey](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes). |
| 46 | + |
| 47 | +## Step 2. Configure Juno Journey to support provisioning with Azure AD |
| 48 | + |
| 49 | +1. For **Secret Token ** and **Tenant URL ** contact Juno Journey support team at [email protected]. This value will be entered in the **Secret Token ** and **Tenant URL ** fields respectively in the Provisioning tab of your Juno Journey application in the Azure portal. |
| 50 | + |
| 51 | +## Step 3. Add Juno Journey from the Azure AD application gallery |
| 52 | + |
| 53 | +Add Juno Journey from the Azure AD application gallery to start managing provisioning to Juno Journey. If you have previously setup Juno Journey 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). |
| 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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). |
| 58 | + |
| 59 | +* When assigning users and groups to Juno Journey, 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. |
| 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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). |
| 62 | + |
| 63 | + |
| 64 | +## Step 5. Configure automatic user provisioning to Juno Journey |
| 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 TestApp based on user and/or group assignments in Azure AD. |
| 67 | + |
| 68 | +### To configure automatic user provisioning for Juno Journey 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 | +2. In the applications list, select **Juno Journey**. |
| 75 | + |
| 76 | +  |
| 77 | + |
| 78 | +3. Select the **Provisioning** tab. |
| 79 | + |
| 80 | +  |
| 81 | + |
| 82 | +4. Set the **Provisioning Mode** to **Automatic**. |
| 83 | + |
| 84 | +  |
| 85 | + |
| 86 | +5. Under the **Admin Credentials** section, input the tenant URL value retrieved earlier in **Tenant URL**. Input the secret token value retrieved earlier in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to Juno Journey. If the connection fails, ensure your Juno Journey account has admin permissions and try again. |
| 87 | + |
| 88 | +  |
| 89 | + |
| 90 | +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. |
| 91 | + |
| 92 | +  |
| 93 | + |
| 94 | +7. Select **Save**. |
| 95 | + |
| 96 | +8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Juno Journey**. |
| 97 | + |
| 98 | +9. Review the user attributes that are synchronized from Azure AD to Juno Journey in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Juno Journey 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 Juno Journey API supports filtering users based on that attribute. Select the **Save** button to commit any changes. |
| 99 | + |
| 100 | + |Variable|Type| |
| 101 | + |---|---| |
| 102 | + |userName|String| |
| 103 | + |externalId|String| |
| 104 | + |displayName|String| |
| 105 | + |title|String| |
| 106 | + |active|Boolean| |
| 107 | + |preferredLanguage|String| |
| 108 | + |emails[type eq "work"].value|String| |
| 109 | + |addresses[type eq "work"].country|String| |
| 110 | + |addresses[type eq "work"].region|String| |
| 111 | + |addresses[type eq "work"].locality|String| |
| 112 | + |addresses[type eq "work"].postalCode|String| |
| 113 | + |addresses[type eq "work"].formatted|String| |
| 114 | + |addresses[type eq "work"].streetAddress|String| |
| 115 | + |name.givenName|String| |
| 116 | + |name.familyName|String| |
| 117 | + |name.middleName|String| |
| 118 | + |name.formatted|String| |
| 119 | + |phoneNumbers[type eq "fax"].value|String| |
| 120 | + |phoneNumbers[type eq "mobile"].value|String| |
| 121 | + |phoneNumbers[type eq "work"].value|String| |
| 122 | + |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department|String| |
| 123 | + |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber|String| |
| 124 | + |urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:costCenter|String| |
| 125 | + urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:division|String| |
| 126 | + urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager|String| |
| 127 | + urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:organization|String| |
| 128 | + |
| 129 | + |
| 130 | +10. 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). |
| 131 | + |
| 132 | +11. To enable the Azure AD provisioning service for Juno Journey, change the **Provisioning Status** to **On** in the **Settings** section. |
| 133 | + |
| 134 | +  |
| 135 | + |
| 136 | +12. Define the users and/or groups that you would like to provision to Juno Journey by choosing the desired values in **Scope** in the **Settings** section. |
| 137 | + |
| 138 | +  |
| 139 | + |
| 140 | +13. When you are ready to provision, click **Save**. |
| 141 | + |
| 142 | +  |
| 143 | + |
| 144 | +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. |
| 145 | + |
| 146 | +## Step 6. Monitor your deployment |
| 147 | +Once you've configured provisioning, use the following resources to monitor your deployment: |
| 148 | + |
| 149 | +* 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 |
| 150 | +* 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 |
| 151 | +* 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). |
| 152 | + |
| 153 | +## Additional resources |
| 154 | + |
| 155 | +* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md) |
| 156 | +* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md) |
| 157 | + |
| 158 | +## Next steps |
| 159 | + |
| 160 | +* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md) |
0 commit comments