Skip to content

Commit a3d173c

Browse files
authored
Merge pull request #1502 from dominikforal/patch-2
Update alvao-provisioning-tutorial.md
2 parents b6abf18 + 8d49384 commit a3d173c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/identity/saas-apps/alvao-provisioning-tutorial.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The scenario outlined in this article assumes that you already have the followin
4444

4545
## Step 2: Configure ALVAO to support provisioning with Microsoft Entra ID
4646
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.
4848

4949
<a name='step-3-add-alvao-from-the-azure-ad-application-gallery'></a>
5050

@@ -91,7 +91,7 @@ This section guides you through the steps to configure the Microsoft Entra provi
9191

9292
1. Select **Save**.
9393

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**.
9595

9696
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.
9797

@@ -122,10 +122,10 @@ This section guides you through the steps to configure the Microsoft Entra provi
122122

123123
> [!NOTE]
124124
>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)
127127
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**.
129129

130130
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.
131131

0 commit comments

Comments
 (0)