Skip to main content

HRIS Integration - Microsoft Teams

Keep learner metadata current from Microsoft Entra by granting consent, mapping directory properties, and checking the synced values.

Platform access level: Org Admins


Syncing Microsoft Teams metadata keeps selected learner profile fields current from your Microsoft Entra directory, so you can group learners and target training without updating those values by hand. You choose which properties Arist receives and the metadata field each one updates. This guide is written for the Org Admin and Microsoft Entra Global Administrator who can grant admin consent.

Metadata sync can be enabled for your organization through your Arist Customer Success contact.


1. Understand the metadata connection

Your Microsoft Entra directory holds employee information. Arist maps selected values onto the learners included in your configured Teams sync population. That population can be your whole tenant or specific Microsoft Entra groups.

Arist reads those properties through Microsoft Graph using the Arist User Sync app, the same background service that builds your Teams learner list. This gives you an HRIS-style source of profile data from the directory you already maintain, without setting up a separate brokered HRIS connection.

The property picker includes supported profile fields such as department, job title, employee ID, company name, and office location. It also includes Extension Attributes 1 to 15. These extension attributes can hold organization-specific values, such as division or business unit, when your directory contains that data. You can map any profile property the picker offers through User.Read.All, including fields from a learner's manager.


2. Confirm what you need before you begin

Confirm the items below before selecting fields, since the sync can only copy values your directory holds and your Microsoft permissions allow Arist to read.

Item

What to confirm

Metadata sync turned on

Your Arist contact has turned on metadata sync for your organization. Synced user properties appears in the Microsoft Teams settings only after that, and only once learner sync is on and Microsoft consent has been granted.

Teams learner sync

You either plan to link or have already linked your Microsoft Tenant to Arist with the automatic user synchronization enabled.

Learner population

Whether the sync includes your whole tenant or specific Microsoft Entra groups, and whether that population is the one you want to update.

Global Administrator

The Microsoft Entra Global Administrator for the tenant is available to grant consent. Confirm the exact address they use for that role.

Global Administrator's Arist account

That administrator has an Arist account with Org Admin access to your organization. If they use a dedicated Global Administrator address, their Arist account must use that address too. Confirm they can sign in before your setup session.

Source values

Each property you want to use is populated and kept current in Microsoft Entra. Confirm what any extension attribute means in your directory (these do not come over with human-readable names).

Field ownership

Agree whether Teams or another integration maintains each destination field, especially if that field already contains learner values.

The Arist User Sync app needs the User.Read.All application permission to sync selected metadata properties. Ordinary learner synchronization can run without this additional permission.

If you have not set up the Teams integration, first follow Setting Up Arist for Microsoft Teams.


3. Sign in with the Global Administrator's Arist account

Complete these steps before enabling learner sync or granting additional consent. Your Global Administrator may use a dedicated administrator address that differs from their everyday work address, so confirm which account they will use before starting.

  1. Confirm the Global Administrator's Microsoft sign-in address for the tenant you are connecting.

  2. Have an existing Org Admin or your Arist contact arrange an Arist account with Org Admin access for that address in your organization. If the account already exists, confirm its organization access.

  3. Sign in to Arist with that account. If another account is signed in, open the user menu at the bottom left, select Logout, and sign in with the Global Administrator's address.

  4. Check the address shown at the bottom left. It should be the Global Administrator's address before you start the Microsoft consent flow.

  5. Open the organization menu at the top left, select Organization settings, then Delivery methods. Expand Microsoft Teams and confirm that Microsoft Teams tenant ID identifies the intended tenant.

Important: Start consent while signed into the Global Administrator's Arist account, then use that administrator's Microsoft account when Microsoft asks you to sign in. If Microsoft selects an everyday work account automatically, choose the Global Administrator account for the intended tenant before granting consent.


4. Enable metadata sync and grant consent

Start from User synchronization in the expanded Microsoft Teams panel. The step that opens consent depends on whether your organization already syncs learners.

If Teams learner sync is already set up

  1. In the expanded Microsoft Teams panel, look for a banner that says your Microsoft tenant has not granted User.Read.All. It can appear above the core learner fields or above Synced user properties.

  2. If no permission banner appears, User.Read.All is already granted. Go to section 5. If Arist says it could not verify your tenant's permissions, select Check again before continuing.

  3. If you see it, select Re-consent on the banner. This opens the Additional permissions required dialog.

Important: Do not uncheck and recheck Enable automatic user synchronization to re-consent. That clears your sync population. Re-consent keeps your population and settings as they are.

If you are setting up Teams learner sync for the first time

  1. Confirm the tenant is linked and you are signed into the Global Administrator's Arist account.

  2. Check Enable automatic user synchronization once. This opens the Additional permissions required dialog.

Complete consent and confirm the population

  1. In the Additional permissions required dialog, select Continue.

  2. Sign in to Microsoft with the Global Administrator account for the intended tenant. Confirm the account and tenant, then review and grant the requested permissions for Arist User Sync, including User.Read.All for learner metadata.

  3. Return to Delivery methods in Arist and expand Microsoft Teams. Confirm that Enable automatic user synchronization is selected.

  4. For an existing sync, confirm your population is unchanged. For a new sync, choose your pilot groups or whole-tenant population.

  5. Continue to Synced user properties to choose the fields you want to copy.

Important: The Microsoft redirect reloads the page, so re-enter any mapping changes you had not saved before starting consent. When you turn on learner sync for the first time, choose your groups or whole-tenant option after you return.

If a permission banner remains after consent, use the table below.

Banner

What it means

What to do

Your Microsoft tenant has not granted User.Read.All

Consent for User.Read.All was never given or was revoked.

Select Re-consent and approve as the Global Administrator.

Could not verify your tenant's permissions

Arist could not check its Microsoft permissions. This is not missing consent.

Select Check again. If the banner stays, contact your Arist Customer Success contact.


5. Choose the properties and field names

Each mapping pairs a Microsoft Entra property with an Arist metadata field. Choose the properties you need for your learner groups and cohorts, then name the fields so the team using them knows what they mean.

the User synchronization section of the Microsoft Teams panel in Delivery methods: the Sync all Microsoft Teams users and specific-groups population options, the Core learner fields rows for Email, Microsoft user ID, First name and Last name with the Add field control, and Synced user properties with the locked Department row
  1. Under User synchronization, confirm that Enable automatic user synchronization is selected.

  2. Review the learner population. Sync all Microsoft Teams users selects your whole tenant; Or select specific groups to synchronize lets you choose groups. Keep your existing population unless you intend to change who syncs.

  3. Find Synced user properties below Core learner fields.

  4. Select Add property. Use the search box to find a supported property, then select it. Properties already in your list are omitted from the picker.

  5. Review the new row's Arist field name. By default, each property writes to an Arist field with the same name, for example jobTitle writes to job title. Leave the input blank to keep that name, or enter the name you want.

  6. Repeat for each property you need. Review any message beneath a row, including whether it writes into an existing field.

The Entra property column shows the source. The Arist field name column shows where its value goes. Department has a lock because its destination name stays fixed.

Synced user properties with Department, Job title, Office location, Mail nickname, Employee ID and Company name mapped, and a new Extension attribute 10 row circled, its Arist field name input reading division, above the Add property control

For example, if your directory stores division in Extension attribute 10, map it to an Arist field named division. The extension attribute number alone does not tell Arist what the value means, which is why confirming it with your Microsoft 365 team matters.

Two properties cannot use the same Arist field name. The department property keeps the name department because analytics depends on that name. Other properties cannot use department as their field name.

Arist can reuse a matching existing metadata field. The field must have the expected type: supported properties include text, dates, and true/false values. If the screen reports a type conflict, choose a different field name. Resolve a conflict involving department with your Arist Customer Success contact before saving.

Important: Syncing into an existing field can replace values entered manually or supplied by another integration. Agree which system maintains that field before saving the mapping.


6. Save and check the learner values

Saving tells Arist which fields to update. Check a small sample afterward so you can confirm both the source values and the destination names before using them to target training.

  1. Review the selected properties, field names, and sync population.

  2. Scroll to the bottom of the expanded Microsoft Teams panel and select Save.

  3. If prompted to re-sync every user in your tenant, review the scope and select Save and re-sync when you are ready.

  4. After synchronization, open a learner profile included in the sync population and check its metadata values.

  5. Compare those values with Microsoft Entra and repeat the check for a small sample of learners.

How existing learners receive the new values depends on your sync population.

Sync population

What happens after a mapping change

Specific Microsoft Entra groups

The changes apply on the next group sync.

Whole tenant

Adding a property or changing its destination field can trigger a full re-sync, so existing learners receive the new field. Review the confirmation before continuing; large tenants can take a while to complete.

Tip: Start with a small pilot group when setting up a new connection. Confirm the values and field names before widening the population.


7. Maintain the fields after setup

Update source values in Microsoft Entra. Subsequent syncs copy nonblank source values into the selected Arist fields. A blank source value does not clear an existing Arist value.

Removing a property from the mapping stops future updates after you save. Values already on learners remain. Changing a property's destination field also leaves the old field and its values in place.

Metadata changes can change membership in rule-based groups and dynamic cohorts. Review rules that use the mapped fields before changing their source or destination.

Stop metadata sync

Microsoft shows every Arist User Sync permission on one consent screen and doesn't allow approving only some of them. If your organization doesn't want metadata sync, grant the full set, then revoke User.Read.All in the Microsoft Entra admin center under Enterprise applications → Arist User Sync → Permissions.

Learner sync keeps running. Properties that require User.Read.All stop updating within about an hour, and values already stored as metadata stay. Core learner fields using properties available without that permission can keep updating.

Mappings that require it, such as Language mapped from preferred language or an extension attribute, or External user ID mapped from employee ID or an extension attribute, stop updating. To restore the permission, select Re-consent on the permission banner.


Related articles

Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].

Did this answer your question?