TNJ Case Study

CORE Solutions · Identity & Access

Automated Identity Provisioning with Active Directory

Taking the manual work out of onboarding for the help desk, so new hires can sign in on day one.

100s
of disconnected applications in the enterprise rollout
20
applications I integrated using REST APIs and SSO
Hours
of help desk time saved per onboarding
Day 1
new hires sign in with only a password reset

The company ran hundreds of applications that each managed their own users, and the enterprise Azure Active Directory rollout set out to bring them under a single SSO and access governance model. The hard part was making onboarding easier on the help desk. When someone was hired, their Active Directory account was created, and a form went to the hiring manager listing the access the new hire would need and for which applications. Depending on the manager's schedule, that form could sit for days.

The old onboarding process
  1. 1New hireHire confirmed
  2. 2AD account createdDone quickly
  3. 3Access form to managerWaiting on manager's schedule: days
  4. 4IT visits every appConnect username to organization: hours
  5. 5Day oneLogin issues possible

Even with the AD account ready, IT then had to go into each application by hand and connect the user's username to the organization. It took hours per hire, it landed on the help desk, and it left room for login problems on a new employee's first day. Offboarding had the same weakness: removing access depended on someone visiting every app.

I took on the first wave of that rollout: integrating 20 third-party applications with Active Directory so that the manual app-by-app setup happened automatically from the AD account. The work combined two approaches:

Before
20 apps20 separate logins20 manual steps

Every application was its own island. IT visited each one to connect a new hire's username to the organization.

After
ActiveDirectory

Active Directory became the hub. REST APIs connect each user to the organization and SSO handles sign-in for all 20.

REST APIs handled the account lifecycle, so connecting a user to the organization in each app no longer required IT to log in and do it by hand. Single sign-on meant users authenticated through Active Directory rather than holding separate credentials in every system.

Onboarding
  1. Account created in AD
  2. REST APIs connect the user to each app
  3. Day one: reset password and sign in
Offboarding
  1. AD account disabled
  2. REST APIs remove app accounts
  3. Access ends across the integrated apps
Phase 01Understanding where the time went.

On paper, onboarding looked simple: create the user in Active Directory and they're set. In practice, the AD account was only the first step. A form went to the hiring manager listing the apps the new hire needed, and once it came back, IT had to log in to each application and connect the user's username to the organization.

The process depended on a manager's calendar and on the help desk's time. Every hire cost IT hours, and a new employee's first day could start with login problems.

Phase 02Taking stock of the applications.

I worked through the third-party applications to see how each could be connected: which exposed a REST API for managing users, which supported SSO, and which needed both.

That review became the list of 20 applications for the first wave, and a single pattern that could be applied across the rest of the hundreds.

Phase 03Connecting the apps to Active Directory.

For each application, I used its REST API so a user created in Active Directory is linked to the organization automatically, and set up SSO so that sign-in runs through AD.

Repeating the same pattern across all 20 kept the build consistent and gave the rollout a template to scale, and it meant the help desk had one process to understand instead of twenty.

Phase 04Making day one uneventful.

The goal was simple: a new hire sits down on their first day, resets their password and signs in. I tested the flow end to end against the integrated applications and made sure the help desk knew what the new process covered.

Offboarding followed the same path. Disabling the account in Active Directory became the way access ended.

Each onboarding saved the help desk multiple hours. Because the connection to every application was handled automatically from Active Directory, a new hire's first day no longer started with login troubleshooting. The only thing they needed to do was reset their password.

Offboarding benefited the same way: when someone left, access ended through Active Directory instead of depending on a manual visit to each application.

Those 20 applications were the first wave of a rollout built to reach hundreds. The integration pattern was designed so that each additional application could follow it.

← Back to experience