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: docs/identity/saas-apps/alvao-provisioning-tutorial.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ The scenario outlined in this article assumes that you already have the followin
44
44
45
45
## Step 2: Configure ALVAO to support provisioning with Microsoft Entra ID
46
46
1. Find your **Tenant SCIM Endpoint URL**, which should have the format `{ALVAO REST API address}/scim` (for example, https://app.contoso.com/alvaorestapi/scim).
47
-
1. Generate a new **Secret Token** in **WebApp - Administration - Settings - [Active Directory and Microsoft Entra ID](https://doc.alvao.com/en/11.2/ui/administration/settings/activedirectory)** and copy its value.
47
+
1. Generate a new **Secret Token** in **WebApp - Administration - Settings - [Microsoft Entra ID](https://doc.alvao.com/en/25/ui/administration/settings/microsoft-entra-id)** and copy its value.
@@ -91,7 +91,7 @@ This section guides you through the steps to configure the Microsoft Entra provi
91
91
92
92
1. Select **Save**.
93
93
94
-
1. Under the **Mappings** section, select **Synchronize Microsoft Entra users to ALVAO**.
94
+
1. Under the **Mappings** section, select **Provision Azure Active Directory Users**.
95
95
96
96
1. Review the user attributes that are synchronized from Microsoft Entra ID to ALVAO in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in ALVAO for update operations. If you choose to change the [matching target attribute](~/identity/app-provisioning/customize-application-attributes.md), you need to ensure that the ALVAO API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
97
97
@@ -122,10 +122,10 @@ This section guides you through the steps to configure the Microsoft Entra provi
122
122
123
123
> [!NOTE]
124
124
>For advanced settings see:
125
-
> *[Mapping SCIM attributes to user fields](https://doc.alvao.com/en/11.2/admin-guide/users/authentication/aad/provisioning/person-attribute-mapping)
126
-
> *[Mapping SCIM attributes to object properties](https://doc.alvao.com/en/11.2/admin-guide/users/authentication/aad/provisioning/object-attribute-mapping)
125
+
> *[Mapping SCIM attributes to user fields](https://doc.alvao.com/en/25/admin-guide/users/authentication/aad/provisioning/person-attribute-mapping)
126
+
> *[Mapping SCIM attributes to object properties](https://doc.alvao.com/en/25/admin-guide/users/authentication/aad/provisioning/object-attribute-mapping)
127
127
128
-
1. Under the **Mappings** section, select **Synchronize Microsoft Entra groups to ALVAO**.
128
+
1. Under the **Mappings** section, select **Provision Azure Active Directory Groups**.
129
129
130
130
1. Review the group attributes that are synchronized from Microsoft Entra ID to ALVAO in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in ALVAO for update operations. Select the **Save** button to commit any changes.
0 commit comments