Azure AD Provisioning in Happeo

This article aims to provide you with a guide on how to enable Azure Provisioning for Happeo

Table of contents

  1. In short
  2. Create a Happeo enterprise application in Azure
  3. Obtaining the provisioning credentials from Happeo
  4. Enable provisioning for the application
    1. Admin credentials
    2. Mappings
      1. Users
      2. Groups
    3. Specify users and groups to provision
      1. Sync all users and groups
    4. Scoping filters
  5. Start provisioning

In short

To enable Azure AD Provisioning of users and groups:

  • You will need an Azure AD enterprise application, which must be created in your Active Directory
  • You need to be an administrator of your organization in Happeo in order to get provisioning credentials

Create a Happeo enterprise application in Azure

  1. Go to your Azure Portal
  2. Select Azure Active Directory
  3. Under Azure Active Directory, navigate to Enterprise applications

4.   Under the All applications tab, click on New application

5.   You will be taken to Browse Azure AD Gallery. Select Create your own application

6.   Input the name of your app (for example “Happeo Sync”)

7.   Select Integrate any other application you don't find in the gallery

8.   Then click on the Create button

9.  Once the application is created in a few seconds, you will be taken to the Overview

Obtaining the provisioning credentials from Happeo

  1. Log in with your account to app.happeo.com
  2. Go to Admin Settings in the top right corner
  3. Select Integrations and click on the Setup button for Azure Provisioning

   4.   (Optional): A modal will pop up asking for your Azure AD tenant ID if we cannot find it

   5.   A modal will pop up containing two fields: tenant URL and tenant secret. These will need             to be copied to the Azure side into the enterprise application

Enable provisioning for the application

This section has been referenced from this link.

Admin credentials

1.   In the Happeo enterprise application (that you have created), go to the tab Provisioning and        click on the Get started button

2.  Set Provisioning Mode to Automatic

3.  Fill in the Tenant URL and Secret Token that you obtained previously from Happeo

4.  Click on the Test Connection button to verify your Tenant URL and Secret Token

5.  You should receive a success notification. Then click on the Save button to save the                     configuration

Troubleshooting: If the testing is not successful, please retrace your steps. If testing continues to not succeed, please contact our support team.

Mappings

Users

One attribute mapping must be changed for users to provision correctly.

  1. In the Edit provisioning tab, click on Mappings and then click on Provision Azure Active Directory Users
  2. On this page, we need to change the existing mapping for mailNickame (source) to externalId (target). To do that, click on the row showing that mapping to edit it, and change the source attribute to objectId in the “edit attribute” side-panel. Verify that the target attribute is still externalId
  3. Click “Ok” and verify that the mapping now is from objectId (source) to externalId (target)

4.   Save the changes

If for some reason the original mapping does not exist, then you should create a new one, which maps the source attribute objectId to the target attribute externalId.

Groups

Two attribute mappings must be created and added in case groups are used in Azure AD.

1.  In the Provisioning Mapping section, click on Provision Azure Active Directory Groups

2.  Check the box Show advanced options and click on Edit attribute list for customappsso

3.  Create the following two attributes:

Name Type

urn:ietf:params:scim:schemas:extension:happeo:2.0:Group:emailEnabled

Boolean

urn:ietf:params:scim:schemas:extension:happeo:2.0:Group:email

String

4.  Then click on the Save button. You will be taken back to the Attribute Mapping screen for             Groups

5.  Now we need to add two new mappings corresponding to these two newly created attributes.       Click on Add new mapping and set the source attribute to be mailEnabled and the target           attribute to be the newly created attribute urn:ietf:params:scim:schemas:extension:                 happeo:2.0:Group:emailEnabled. Click “Ok”

6.  Repeat this, setting the source attribute this time to be mail and the target attribute urn:ietf:         params:scim:schemas:extension:happeo:2.0:Group:email

7.  After you have added these two mappings, don’t forget to save the changes. The screenshot       shows what you should end up with as mappings

Specify users and groups to provision

This is done by first allowing the enterprise application to sync all users and groups, then adding scoping filters.

Sync all users and groups

1.   In the Provisioning Settings section, choose Sync all users and groups for scope

2.   Click on the Save button to save the changes

Scoping filters

This section has been referenced from this link

1.   In the Provisioning Mappings section, click on Provision Azure Active Directory Groups or        Provision Azure Active Directory Users to manage scoping filters on groups or users

2.  You will be taken to the Attribute Mapping view. Click on Source Object Scope

3.  You will be taken to the Source Object Scope view. Click on Add scoping filter

4.   Specify the Filtering Criteria

5.   Provide a Scoping Filter Title

6.   Click on the Ok button to save the scoping filter

You will see the new scoping filter in Source Object Scope and you can continue adding more scoping filters.

Note: Scoping filters for users and groups are managed separately (entry point from Mappings section in Provisioning).

Start provisioning

1.   Go back to the Provisioning menu. You should see the configured provisioning

2.   Tap on the Start provisioning button to start the automatic provisioning from Azure AD to                Happeo 

Note: The provisioning may take some time. You are able to view the provisioning logs in the Enterprise application in Azure if you are unsure if the provisioning is working or not.