Platform access level: Org Admins
Connecting your systems to Arist keeps learner data current without maintaining manual exports. This guide explains the brokered implementation process and where to start if your Microsoft Entra directory supplies learner metadata through Teams sync. It is written for Org Admins and IT stakeholders who sponsor an integration.
1. Choosing your connection
Your setup depends on the system you connect and the data you want to move. For a brokered HRIS or LMS integration, Arist's solutions engineering team builds and maintains the connection through a managed integration platform. Your IT team confirms system access, the required data, and the implementation scope with Arist. Sections 2 to 5 describe that brokered implementation process.
If the learner profile data you need is already in Microsoft Entra, Teams metadata sync can keep it current in Arist through a native Microsoft Graph connection, without a separate brokered HRIS connection. Metadata sync can be enabled for your organization through your Arist Customer Success contact.
For supported properties, Global Administrator account prerequisites, consent, mapping, and validation, follow HRIS Integration - Microsoft Teams. That guide covers both existing and first-time learner sync. For Teams learner synchronization and course delivery setup, follow Setting Up Arist for Microsoft Teams.
Note: Teams metadata sync copies supported directory profile properties for your configured tenant or group population. It does not write course completions to an LMS or synchronize manager relationships.
2. Six phases from SOW to cutover
Brokered HRIS and LMS implementations follow the six-phase process below. The eight-week implementation clock starts when the statement of work (SOW) is signed; pre-sales discovery sits outside that clock.
Phase | Timing | Milestone |
Scoping and planning | Week 0 | SOW signed and systems inventoried |
Kickoff and discovery | Weeks 1 to 3 | Configuration spec signed off |
Build and configure | Weeks 4 to 5 | Configuration working in staging |
UAT and pilot | Weeks 6 to 7 | UAT signed and cutover scheduled |
Cutover and go-live | Week 8 | Production stable |
Steady state | 90+ days | Project closed |
3. Fast track and full track
Two tracks run inside that timeline, depending on which systems you connect.
Fast track: SSO and delivery methods are plug-and-play, so you can begin sending lessons by around week 3.
Full track: Brokered HRIS and LMS integrations run the full schedule and go live together at the week 8 cutover. HRIS brings learners in, and LMS receives completions.
4. Security posture
For brokered integrations, the managed platform handles the connection between your system and Arist. The points below describe that connection.
Brokered connection: The managed integration platform sits between your connected HRIS or LMS and Arist.
One credential per organization: Arist authenticates through a single key scoped to your organization.
Enterprise-grade platform: Monitoring, logging, and reliability run on a vendor-backed integration platform rather than one-off code.
Maintained for the contract term: Schema changes, vendor API updates, and error resolution are included.
Important: Before rollout, confirm your Microsoft permissions and source data using the requirements in HRIS Integration - Microsoft Teams.
5. Ninety-day handoff
After go-live, a brokered integration moves from the implementation team to Customer Success over 90 days.
Milestone | Timing | Focus |
Go-live | Day 0 | Production deploy and cutover |
Hyper-care | Week 1 | Bi-weekly check-ins, IM leads |
Retro | Day 14 | Hyper-care closes, CSM takes lead |
Adoption check | Day 30 | First NPS and Org Admin enablement |
Mid-point review | Day 60 | Friction surfaced early |
Closure | Day 90 | Project closed |
Related articles
Note: Need help at any point? Reach out to your Arist Customer Success contact, or email [email protected].
