แก้ไข

แชร์ผ่าน

Configure ALVAO for automatic user provisioning with Microsoft Entra ID

This article describes the steps you need to perform in both ALVAO and Microsoft Entra ID to configure automatic user provisioning. When configured, Microsoft Entra ID automatically provisions and de-provisions users and groups to ALVAO using the Microsoft Entra 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 Microsoft Entra ID.

Supported capabilities

  • Create users in ALVAO.
  • Remove users in ALVAO when they don't require access anymore.
  • Keep user attributes synchronized between Microsoft Entra ID and ALVAO.
  • Provision groups and group memberships in ALVAO.

Prerequisites

The scenario outlined in this article assumes that you already have the following prerequisites:

Step 1: Plan your provisioning deployment

  1. Learn about how the provisioning service works.
  2. Determine who is in scope for provisioning.
  3. Determine what data to map between Microsoft Entra ID and ALVAO.

Step 2: Configure ALVAO to support provisioning with Microsoft Entra ID

  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).
  2. Generate a new Secret Token in WebApp - Administration - Settings - Microsoft Entra ID and copy its value.

Add ALVAO from the Microsoft Entra application gallery to start managing provisioning to ALVAO. If you have previously setup ALVAO for SSO you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4: Define who is in scope for provisioning

The Microsoft Entra provisioning service allows you to scope who is provisioned based on assignment to the application, or based on attributes of the user or group. If you choose to scope who is provisioned to your app based on assignment, you can use the steps to assign users and groups to the application. If you choose to scope who is provisioned based solely on attributes of the user or group, you can use a scoping filter.

  • 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.

  • If you need extra roles, you can update the application manifest to add new roles.

Step 5: Configure automatic user provisioning to ALVAO

This section guides you through the steps to configure the Microsoft Entra provisioning service to create, update, and disable users and/or groups in ALVAO based on user and/or group assignments in Microsoft Entra ID.

To configure automatic user provisioning for ALVAO in Microsoft Entra ID:

  1. Sign in to the Microsoft Entra admin center as at least an app owner or Cloud Application Administrator.

  2. Browse to Entra ID > Enterprise apps

    Screenshot of Enterprise applications blade.

  3. In the applications list, select ALVAO.

    Screenshot of the ALVAO link in the Applications list.

  4. Select the Provisioning tab.

    Screenshot of Provisioning tab.

  5. Set + New configuration.

    Screenshot of Provisioning tab automatic.

  6. In the Tenant URL field, input your ALVAO Tenant URL and Secret Token. Select Test Connection to ensure Microsoft Entra ID can connect to ALVAO. If the connection fails, ensure your ALVAO account has the required admin permissions and try again.

    Screenshot of Provisioning test connection.

  7. Select Create to create your configuration.

  8. Select Properties in the Overview page.

  9. Select the pencil to edit the properties. Enable notification emails and provide an email to receive quarantine emails. Enable accidental deletions prevention. Select Apply to save the changes.

    Screenshot of Provisioning properties.

  10. Select Attribute Mapping in the left panel and select users.

  11. 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, you need to ensure that the ALVAO API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by ALVAO
    userName String ✓ ✓
    externalId String ✓ ✓
    active Boolean ✓
    displayName String ✓
    title String
    emails[type eq "work"].value String
    name.givenName String
    name.familyName String
    name.formatted String
    addresses[type eq "work"].formatted String
    addresses[type eq "work"].locality String
    addresses[type eq "work"].region String
    addresses[type eq "work"].country String
    addresses[type eq "work"].postalCode String
    addresses[type eq "work"].streetAddress String
    phoneNumbers[type eq "work"].value String
    phoneNumbers[type eq "mobile"].value String
    phoneNumbers[type eq "fax"].value String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:organization String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:department String
    urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:manager String

  12. Select groups.

  13. 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.

    Attribute Type Supported for filtering Required by ALVAO
    displayName String ✓ ✓
    externalId String
    members Reference

  14. To configure scoping filters, refer to the following instructions provided in the Scoping filter article article.

  15. Use on-demand provisioning to validate sync with a small number of users before deploying more broadly in your organization.

  16. When you're ready to provision, select Start Provisioning from the Overview page.

Step 6: Monitor your deployment

Once you configure provisioning, use the following resources to monitor your deployment:

  1. Use the provisioning logs to determine which users are provisioned successfully or unsuccessfully
  2. Check the progress bar to see the status of the provisioning cycle and how close it's to completion
  3. If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states the application provisioning quarantine status article.

More resources

Related content

  • Last updated on