Azure AD Provisioning in Happeo

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

To learn how to set up the Microsoft integrations inside Happeo, please see this article.

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 to get provisioning credentials

Create a Happeo enterprise application in Azure

Go to your Azure Portal
Select Azure Active Directory
Under Azure Active Directory, navigate to Enterprise applications
Then, under the All applications tab, click New application

You will be taken to Browse Azure AD Gallery. From there:

Select Create your own application
Input the name of your app (for example “Happeo Sync”)
Select Integrate any other application you don't find in the gallery
Then click the Create button

Once the application is created, you will be taken to the Overview.

Obtaining the provisioning credentials from Happeo

Log in with your account to beta.happeo.com
Go to Admin Settings in the top right corner
Select Integrations and click the Setup button for Azure Provisioning
1. Note: A modal will pop up asking for your Azure AD tenant ID if we cannot find it
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

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

Then, you can:

Set Provisioning Mode to Automatic
Fill in the Tenant URL and Secret Token that you obtained previously from Happeo
Click the Test Connection button to verify your Tenant URL and Secret Token
You should receive a success notification. Then click 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.

In the Edit provisioning tab, click Mappings and then click Provision Azure Active Directory Users
On this page, you need to change the existing mapping for mailNickame (source) to externalId (target). To do that, click 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
Click Ok and verify that the mapping now is from objectId (source) to externalId (target)
Save the changes

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

Groups

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

In the Provisioning Mapping section, click Provision Azure Active Directory Groups
Check the box Show advanced options and click Edit attribute list for customappsso

Then, 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

You can then:

Click the Save button. You will be taken back to the Attribute Mapping screen for Groups
You will need to add two new mappings corresponding to these two newly created attributes:
1. Click Add new mapping and set the source attribute to be mailEnabled
2. And the target attribute to be the newly created attribute urn:ietf:params:scim:schemas:extension:happeo:2.0:Group:emailEnabled
Click Ok
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
After you have added these two mappings, don’t forget to save the changes. The screenshot below 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

In the Provisioning Settings section, choose Sync all users and groups for scope
Click the Save button to save the changes

Note: External users invited to Azure AD cannot log in to Happeo even if they are provisioned successfully. These users must be invited from the Happeo Admin Settings page.

Scoping filters

This section has been referenced from this link.

In the Provisioning Mappings section, click Provision Azure Active Directory Groups or Provision Azure Active Directory Users to manage scoping filters on groups or users
You will be taken to the Attribute Mapping view. Click Source Object Scope

You will be taken to the Source Object Scope view:

Click Add scoping filter
Specify the Filtering Criteria
Provide a Scoping Filter Title
Click 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.

Start provisioning

Go back to the Provisioning menu. You should see the configured provisioning
Tap on the Start provisioning button to start the automatic provisioning from Azure AD to Happeo

Setting up user and sync group

Once you've followed all the steps in this article, you should see two applications for Happeo in the Azure AD > Enterprise Applications list:

One that you have created (named something like Happeo sync and the icon will be the first letter on a colored background)
And one called Happeo, which has the Happeo logo as the icon

Considerations for user and group sync

There are two options for selecting users and groups to provision and sync:

Assigning users and groups to the application
Or syncing all users

How these work are described in the accordions below, including recommendations on when and how to use each case.

Key considerations for syncing groups, which apply to both options:

Permissions to create Pages and Channels are based on Groups
By default, the permission is set to True, so all members of all Groups have permission to create Pages and Channels
If a user belongs to even one group that has permission to create Pages and Channels, they will have that permission
Our recommendation is that not everyone should have permission to create Pages and Channels, so these would need to be unchecked. Currently, it is a manual process that needs to be done individually for each group, so we recommend not syncing (all) groups until it has been well defined which ones are necessary
Group's member count in Happeo will only show users that have been synced. So if a group in Azure AD has 50 members, but only 40 of them are considered users of Happeo, the member count in Happeo will show as 40

Group types in Microsoft

Security groups
- Security groups are usually used more for assigning permissions or access
- Security groups do not have an email address within Microsoft, but when a security group is synced to Happeo, an email address is generated within Happeo for it
Microsoft 365 groups
- Each Azure Active Directory auto-creates a Microsoft 365 group that contains all users in the environment and is also visible to everyone in Teams. Out of these options (when creating a new Teams group), it's an org-wide group
  - Microsoft 365 groups have an email address

Teams groups
- When creating a new team, it's possible to create it from an existing Microsoft 365 group or create an entirely new group
- Creating a Team automatically creates a Microsoft 365 group, but you can create Microsoft 365 groups without creating a Team
- There isn't a way to determine in Azure if a Microsoft 365 group has a Team linked to it, or whether it's private or open to join
- For Teams that are public (anyone in your org can join), note that anyone who joins that group is able to gain access to content shared with that group (within Happeo)

Table of contents