Setting Arist up in Microsoft Teams delivers courses inside the tool your learners already use, with no separate login and no new system to learn. Because delivery is push-based, your IT team installs and configures the apps ahead of time so they are waiting when a learner's first course arrives. This guide is written for the Microsoft 365 Global Administrator who completes the setup, and it runs in order because each step depends on the one before it.

Arist registers three apps in your Microsoft 365 tenant, and all three need their permissions approved. Two are installed in Teams, and the third runs in the background without appearing in Teams at all.

Chat is used instead of the Activity Feed because learners check it far more often. Learners sign in with their existing Teams identity, so there is no separate password, and authentication is handled through Microsoft Entra.

Confirm the seven items below in the weeks before your setup session, not on the day itself. Each is a decision, an access grant, or an asset that can take time to track down, and having all seven ready is the difference between a 30-minute setup and a stalled one.

Scope your rollout to a Microsoft Entra security group rather than your whole tenant. Security groups do not notify members when they are added, and editing the group is then the only thing you need to do to widen or narrow access later. Set the group up this way:

Linking your Tenant ID is the foundation of the whole integration, because Arist uses it to identify which Microsoft 365 environment to connect to. You do this in the Arist web app with an Org Admin account.

Making apps available is done in the Teams Admin Center. This step marks the two Teams apps as eligible to install across your tenant.

Enable both apps at this stage. Skipping Arist Comms breaks the Chat notifications learners rely on for reminders.

Admin consent authorizes Arist to call specific Microsoft Graph APIs on behalf of your organization. Without it, the apps cannot authenticate learners or send notifications. Your Global Administrator grants consent for each app separately.

Arist uses three app registrations, each scoped to the least access it needs. You grant consent for Arist and Arist Comms here, in the Teams Admin Center. The User Sync registration's permissions are granted separately when you enable user sync in Arist. The table below is the full list for your security team.

The standard user sync uses User.ReadBasic.All, which reads only the identity fields listed in the table. If you want Arist to use additional Microsoft metadata, including Extension Attributes 1 to 15, your Global Administrator can grant User.Read.All as a separate permission. This second grant is optional, and the standard sync runs without it.

How you grant it depends on where you are in your setup. If you are setting Arist up for the first time, User.Read.All appears alongside the other User Sync permissions when you enable the sync. If your organization is already running Arist, your Global Administrator re-enables the user sync in Arist, which brings the permission prompt back up and shows User.Read.All as an additional permission to grant.

Arist uses that additional metadata in three places.

Applying your own branding is optional. It gives the apps your organization's name, logo, and accent color so Arist appears as a native part of your Teams environment.

Installing is the step that actually pushes Arist into your learners' Teams sidebars. Because Arist is push-based, pre-installing it ensures the app is already there when a learner's first course arrives. The exact path depends on which install system your tenant uses.

To check which system you have, go to Teams Admin Center, then Manage apps, open Arist, and look at the Users and Groups tab. An Installs section means your tenant uses App Centric Management. If there is no Installs section, use App Setup Policy.

Policy changes and installs can take up to one to two days to propagate, and the first notification can take up to 72 hours after that. This is Microsoft-side behavior, so set expectations with your stakeholders accordingly.

Syncing connects your learners' Teams identities to their Arist accounts so courses reach the right learners. The same Teams admin who granted consent runs this, signed in with Org Admin access. If that Org Admin account was created only for this setup, it can be removed once the sync is running.

Before you sync your full population, sync a small pilot security group containing only your project team. That lets you confirm records map correctly and catch any issues while the impact is limited to a handful of learners.

Setup policies do not always propagate consistently across users, even when configured correctly. Validating before go-live prevents a poor first impression for your learners.