You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/visitly-provisioning-tutorial.md
+50-52Lines changed: 50 additions & 52 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: 'Tutorial: Configure Visitly for automatic user provisioning with Azure Active Directory | Microsoft Docs'
3
-
description: Learn how to configure Azure Active Directory to automatically provision and de-provision user accounts to Visitly.
2
+
title: 'Tutorial: Configure Visitly for automatic user provisioning with Azure Active Directory | Microsoft Docs'
3
+
description: Learn how to configure Azure Active Directory to automatically provision and deprovision user accounts to Visitly.
4
4
services: active-directory
5
5
documentationcenter: ''
6
6
author: zchia
@@ -20,58 +20,58 @@ ms.author: Zhchia
20
20
21
21
# Tutorial: Configure Visitly for automatic user provisioning
22
22
23
-
The objective of this tutorial is to demonstrate the steps to be performed in Visitly and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and de-provision users and/or groups to Visitly.
23
+
The objective of this tutorial is to demonstrate the steps you perform in Visitly and Azure Active Directory (Azure AD) to configure Azure AD to automatically provision and deprovision users or groups to Visitly.
24
24
25
25
> [!NOTE]
26
-
> This tutorial describes a connector built on top of the Azure AD User 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).
26
+
> This tutorial describes a connector built on top of the Azure AD user provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to software-as-a-service (SaaS) applications with Azure Active Directory](../manage-apps/user-provisioning.md).
27
27
>
28
-
> This connector is currently in Public Preview. For more information on the general Microsoft Azure terms of use for Preview features, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
28
+
> This connector is currently in Public Preview. For more information on the general Microsoft Azure terms of use for preview features, see [Supplemental terms of use for Microsoft Azure previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
29
29
30
30
## Prerequisites
31
31
32
32
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
* A user account in Visitly with Admin permissions.
36
+
* A user account in Visitly with admin permissions
37
37
38
-
## Assigning users to Visitly
38
+
## Assign users to Visitly
39
39
40
-
Azure Active Directory uses a concept called *assignments* to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users and/or groups that have been assigned to an application in Azure AD are synchronized.
40
+
Azure Active Directory uses a concept called *assignments* to determine which users should receive access to selected apps. In the context of automatic user provisioning, only the users or groups that were assigned to an application in Azure AD are synchronized.
41
41
42
-
Before configuring and enabling automatic user provisioning, you should decide which users and/or groups in Azure AD need access to Visitly. Once decided, you can assign these users and/or groups to Visitly by following the instructions here:
42
+
Before you configure and enable automatic user provisioning, decide which users or groups in Azure AD need access to Visitly. Then assign these users or groups to Visitly by following the instructions here:
43
43
*[Assign a user or group to an enterprise app](../manage-apps/assign-user-or-group-access-portal.md)
44
44
45
45
## Important tips for assigning users to Visitly
46
46
47
-
*It is recommended that a single Azure AD user is assigned to Visitly to test the automatic user provisioning configuration. Additional users and/or groups may be assigned later.
47
+
*We recommend that you assign a single Azure AD user to Visitly to test the automatic user provisioning configuration. Additional users or groups can be assigned later.
48
48
49
-
* When assigning a user to Visitly, you must select any valid application-specific role (if available) in the assignment dialog. Users with the **Default Access** role are excluded from provisioning.
49
+
* When you assign a user to Visitly, you must select any valid application-specific role (if available) in the assignment dialog box. Users with the Default Access role are excluded from provisioning.
50
50
51
-
## Setup Visitly for provisioning
51
+
## Set up Visitly for provisioning
52
52
53
-
Before configuring Visitly for automatic user provisioning with Azure AD, you will need to enable SCIM provisioning on Visitly.
53
+
Before you configure Visitly for automatic user provisioning with Azure AD, you need to enable System for Cross-domain Identity Management (SCIM) provisioning on Visitly.
54
54
55
-
1.Log in into[Visitly](https://app.visitly.io/login). Click on**Integrations** > **Host Synchronization**.
55
+
1.Sign in to[Visitly](https://app.visitly.io/login). Select**Integrations** > **Host Synchronization**.
62
62
63
-
3. Copy the **API Key**. These values will be entered in the **Secret Token**field in the Provisioning tab of your Visitly application in the Azure portal.
63
+
3. Copy the **API Key**. These values are entered in the **Secret Token**box on the **Provisioning** tab of your Visitly application in the Azure portal.
To configure Visitly for automatic user provisioning with Azure AD, you need to add Visitly from the Azure AD application gallery to your list of managed SaaS applications.
70
+
To configure Visitly for automatic user provisioning with Azure AD, add Visitly from the Azure AD application gallery to your list of managed SaaS applications.
71
71
72
-
**To add Visitly from the Azure AD application gallery, perform the following steps:**
72
+
To add Visitly from the Azure AD application gallery, follow these steps.
73
73
74
-
1. In the **[Azure portal](https://portal.azure.com)**, in the left navigation panel, select **Azure Active Directory**.
74
+
1. In the [Azure portal](https://portal.azure.com), in the left navigation pane, select **Azure Active Directory**.
75
75
76
76
77
77
@@ -83,80 +83,78 @@ To configure Visitly for automatic user provisioning with Azure AD, you need to
83
83
84
84
85
85
86
-
4. In the search box, enter **Visitly**, select **Visitly** in the results panel, and then click the **Add** button to add the application.
86
+
4. In the search box, enter **Visitly**, select **Visitly** in the results panel, and then select **Add** to add the application.
87
87
88
-
88
+
89
89
90
-
## Configuring automatic user provisioning to Visitly
90
+
## Configure automatic user provisioning to Visitly
91
91
92
-
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Visitly based on user and/or group assignments in Azure AD.
92
+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users or groups in Visitly based on user or group assignments in Azure AD.
93
93
94
94
> [!TIP]
95
-
> You may also choose to enable SAML-based single sign-on for Visitly, following the instructions provided in the [Visitly Single sign-on tutorial](Visitly-tutorial.md). Single sign-on can be configured independently of automatic user provisioning, though these two features compliment each other
95
+
> To enable SAML-based single sign-on for Visitly, follow the instructions in the [Visitly single sign-on tutorial](Visitly-tutorial.md). Single sign-on can be configured independently of automatic user provisioning, although these two features complement each other.
96
96
97
-
### To configure automatic user provisioning for Visitly in Azure AD:
97
+
### Configure automatic user provisioning for Visitly in Azure AD
98
98
99
-
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select**All applications**.
99
+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications** >**All applications**.
114
114
115
-
5. Under the Admin Credentials section, input the `https://api.visitly.io/v1/usersync/SCIM` and **API Key** values retrieved earlier in **Tenant URL** and **Secret Token** respectively. Click**Test Connection** to ensure Azure AD can connect to Visitly. If the connection fails, ensure your Visitly account has Admin permissions and try again.
115
+
5. Under the Admin Credentials section, input the `https://api.visitly.io/v1/usersync/SCIM` and **API Key** values retrieved earlier in **Tenant URL** and **Secret Token**, respectively. Select**Test Connection** to ensure that Azure AD can connect to Visitly. If the connection fails, make sure that your Visitly account has admin permissions and try again.
6. In the **Notification Email**field, enter the email address of a person or group who should receive the provisioning error notifications and check the checkbox - **Send an email notification when a failure occurs**.
119
+
6. In the **Notification Email**box, enter the email address of a person or group who should receive the provisioning error notifications. Select the **Send an email notification when a failure occurs** check box.
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Visitly**.
126
126
127
-
127
+
128
128
129
-
9. Review the user attributes that are synchronized from Azure AD to Visitly in the **Attribute Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Visitly for update operations. Select the **Save** button to commit any changes.
129
+
9. Review the user attributes that are synchronized from Azure AD to Visitly in the **Attribute Mappings** section. The attributes selected as **Matching** properties are used to match the user accounts in Visitly for update operations. Select **Save** to commit any changes.
130
130
131
-
131
+
132
132
133
-
134
-
135
-
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).
133
+
10. To configure scoping filters, follow the instructions in the [Scoping filter tutorial](../manage-apps/define-conditional-rules-for-provisioning-user-accounts.md).
136
134
137
135
11. To enable the Azure AD provisioning service for Visitly, change the **Provisioning Status** to **On** in the **Settings** section.
138
136
139
-
137
+
140
138
141
-
12. Define the users and/or groups that you would like to provision to Visitly by choosing the desired values in **Scope** in the **Settings** section.
139
+
12. Define the users or groups that you want to provision to Visitly by choosing the desired values in **Scope** in the **Settings** section.
This operation starts the initial synchronization of all users and/or groups defined in **Scope** in the **Settings** section. The initial sync takes longer to perform than subsequent syncs. For more information on how long it will take for users and/or groups to provision, see [How long will it take to provision users](../manage-apps/application-provisioning-when-will-provisioning-finish-specific-user.md#how-long-will-it-take-to-provision-users).
147
+
This operation starts the initial synchronization of all users or groups defined in **Scope** in the **Settings** section. The initial sync takes longer to perform than subsequent syncs. For more information on how long it takes for users or groups to provision, see [How long will it take to provision users?](../manage-apps/application-provisioning-when-will-provisioning-finish-specific-user.md#how-long-will-it-take-to-provision-users).
150
148
151
149
You can use the **Current Status** section to monitor progress and follow links to your provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Visitly. For more information, see [Check the status of user provisioning](../manage-apps/application-provisioning-when-will-provisioning-finish-specific-user.md). To read the Azure AD provisioning logs, see [Reporting on automatic user account provisioning](../manage-apps/check-status-user-account-provisioning.md).
152
150
153
-
## Connector Limitations
151
+
## Connector limitations
154
152
155
-
Visitly does not support hard deletes, everything is soft delete only.
153
+
Visitly doesn't support hard deletes. Everything is soft delete only.
156
154
157
155
## Additional resources
158
156
159
-
*[Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
157
+
*[Manage user account provisioning for enterprise apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
160
158
*[What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
0 commit comments