IT onboarding and offboarding automation that closes every leaver with proof.
What it is
One accountable lifecycle for every joiner, mover, and leaver.
TeamJML AI brings onboarding and offboarding automation onto one lifecycle record. Four workspaces and a governed agent work from it, from a request made before the account exists to the last confirmed revocation.
Joiner · My Requests
Onboarding starts before the account does.
A future employee needs a start date, an accountable manager, and the right access before day one. The approved request then drives Microsoft Entra ID account creation and the access and equipment work, and with TeamConnect AI the new employee takes their place in the directory. Meanwhile, HR, managers, and IT see readiness against the start date.
Mover · Requirements
A new title isn’t always new access.
A promotion or department change updates the organization, but IT work starts only when the employee’s entitlements actually change. TeamJML AI therefore compares what the new situation requires with what the person already holds and creates assignment or revocation work only for a verified difference — a Consultant becoming a Senior Consultant with the same entitlements needs no ticket.
How requirements are evaluated →
Leaver · Completion
Offboard every leaver. Confirm every removal. Account for the access.
An employee’s last day creates work across identity, applications, subscriptions, and equipment. Every required removal has an owner, TeamJML AI escalates unresolved work, and it verifies completion after the departure date. As a result, every leaver closes on evidence, with each revocation confirmed.
HR Center
Every effective date deserves a clear view.
See upcoming starters, role changes, and leavers across the organization, with approval progress, missing decisions, and readiness against each effective date, so the changes that need HR attention come first.
CIO Executive
Executive approvals with the financial impact in view.
Pending approvals, lifecycle volume, budget impact, and service levels across the organization, and for each high-impact request its annual cost, budget allocation, and approval chain before anyone decides.
Governed agent
Ask the lifecycle question. Get an answer you can act on.
Reachable from Microsoft Teams, Microsoft Outlook, and Microsoft 365 Copilot. Ask which starters need attention before Monday, what is holding up a role change, which leavers still have unresolved access, or which upcoming joiners can be covered by available licenses and which require a purchase. On its own, TeamJML AI governs the agent through the same Role Members as its workspaces, while with TeamConnect AI its lifecycle capabilities join the central agent catalog and follow its controls.
License control
Every license accounted for from onboarding to offboarding, inside and outside Microsoft 365.
Every assignment and revocation is also confirmed in its ticket, whether Microsoft 365, your ITSM, or your service desk completed it. As a result, one lifecycle record covers every license instead of two kinds of evidence, so Finance sees value it can inspect.
Confirmed for every license. TeamJML AI records every assignment and revocation, so you can see whether what someone holds matches what their role requires.
Capacity reused. An existing eligible license satisfies a new requirement.
Purchases avoided. Reuse then removes the need for an additional purchase.
Confirmed spend reduction. Counted only when a purchasing or billing outcome confirms it.
Unnecessary IT tickets avoided. No license work when entitlements stay the same, while the estimated labor value stays separate from cash savings.
One combined case. The case also includes both products’ costs and never counts a benefit twice.
By role: JML automation for IT leaders · SaaS license spend for finance leaders
Audit & compliance evidence
Audit evidence for every access granted at onboarding and revoked at offboarding.
Although their frameworks differ, ISO/IEC 27001, SOC 2, and GDPR audits ask the same question: can you show that access followed each employee’s arrival, change, and exit? TeamJML AI keeps that evidence on the lifecycle record, ready when your auditors ask.
Evidence trail
From approval to verified removal, on one record.
Who requested the change, who approved it, and when; each assignment and revocation with how it was confirmed — by Microsoft 365, your ITSM, or your service desk; escalations of unresolved removals; and verification after the departure date.
Accountable approvals for every joiner, mover, and leaver
TeamJML AI records each decision with the decision-maker, the reason, and the time.
Confirmed assignments
Every access grant for a joiner or mover carries its own confirmation, so nothing rests on an assumption from a ticket.
Confirmed revocations
Access and licenses removed for every leaver, with unresolved removals escalated until verified.
Exceptions on record
Unfinished work stays on the record with its owner, instead of closing silently.
The first question IT asks
Four steps to install onboarding and offboarding automation, with policies ready on day one.
No data to import and nothing to sync first. TeamJML AI seeds default approval policies and SLAs the moment you approve consent, so it works the day you install it.
Where it happens
- Microsoft Marketplace
- Microsoft 365 Admin Center
- Microsoft Teams
- 01
Choose your subscription
TeamJML AI from Microsoft Marketplace or the Microsoft Teams Store. First 30 days free, cancel any time.
- 02
Assign licenses
Then assign the purchased user licenses in your Microsoft 365 Admin Center.
- 03
Open the app
Then find TeamJML AI in the Store inside Microsoft Teams, and open it.
- 04
Approve and start
Finally, approve the Microsoft consent prompts. One click creates the Microsoft SharePoint lists and seeds the default policies and SLAs.
What you never do
- No data import
- No servers
- No agents to deploy
Configuration
Onboarding and offboarding workflows, SLAs, and forms that fit your process.
Every setting of the onboarding and offboarding automation ships with a working default, so none of this has to happen on day one.
Approval routing and SLAs
Decide who approves each request, and how fast, before any request arrives. Conditions route a critical access bundle through the CIO and Security, and give an urgent termination a four-hour target instead of the standard twenty-four.
Who carries out each task
Every IT task reaches your service desk, which then completes it by hand, hands it to your ITSM, or runs Microsoft 365 account, license, and group changes straight from the ticket. Whichever route you choose, completion still lands on the same lifecycle record.
Request forms that ask only what you need
You can set every field on every joiner, mover, and leaver form to shown or hidden, and required or optional, so each request collects exactly what your process needs.
Better together
Your employee directory and IT lifecycle, on the same people data.
On its own, TeamJML AI runs onboarding and offboarding automation from the Microsoft Entra ID user and the selected access bundle. With TeamConnect AI, however, TeamJML AI evaluates every change against the whole organization — managers, departments, offices, job roles, and license roles — and completed changes keep the directory current.
Organization and role context
Approvals and access decisions then reflect each employee’s actual responsibilities.
Subscription and ownership context
Confirmed assignments and revocations build a traceable record of who holds which license, inside and outside Microsoft 365.
A shared employee directory
Completed identity and organization updates also keep people search, collaboration, and agents current.
One agent catalog
TeamJML AI’s lifecycle capabilities also follow the same agent governance as the rest of TeamConnect AI.
Buyer questions
What IT, HR, and Finance ask about onboarding and offboarding automation.
The questions that come up when IT, HR, security, and Finance evaluate TeamJML AI.
Onboarding and offboarding in practice
Can onboarding begin before the employee has a Microsoft Entra ID account?
Yes. TeamJML AI starts with the approved request, drives the Microsoft Entra ID account creation, and coordinates the access and equipment the role needs. With TeamConnect AI, the new employee joins the directory when onboarding completes.
Does every promotion or department change create IT work?
No. Organizational details can change without any IT work. TeamJML AI creates assignment or revocation work only when the employee’s entitlements actually change — with TeamConnect AI, across their primary and additional license roles, including project assignments; on its own, from the selected access bundle.
How do we know offboarding is complete?
The lifecycle record shows every required removal, how it was confirmed, and any exception still open. TeamJML AI also escalates unresolved work and verifies completion after the departure date.
Licenses and financial value
Does disabling an account also remove its licenses?
No. Blocking sign-in and revoking license assignments are separate steps. TeamJML AI records revocation when your IT team or connected ITSM system confirms completion. Released license capacity becomes a cash saving only when a purchasing or billing change reduces expenditure.
How is the financial value counted?
Reused capacity means an existing eligible license met a new requirement. Purchases avoided means that reuse removed the need for an additional purchase. Spend reduction counts only with a purchasing or billing outcome. Finally, the case reports avoided tickets as reduced work, separate from cash savings, and it includes both products’ costs without counting any benefit twice.
Your other systems
Can we use TeamJML AI without TeamConnect AI?
Yes. On its own, TeamJML AI works from the Microsoft Entra ID user, and requirements come from the selected access bundle. TeamConnect AI, however, adds the organization around each person — managers, departments, offices, job roles, and license roles — and a directory that completed changes keep current.
Does TeamJML AI replace our service desk or HR system?
No. Your HR system remains the source of HR records, and HR still runs its imports, because a request carries no contract details, vacation, CVs or skills. Your service desk remains central to IT delivery; TeamJML AI connects the change, the approvals, the execution, and the completion evidence.
Bring your lifecycle
Show us a joiner, a mover, and a leaver. See the difference end to end.
In a thirty-minute demo, see how onboarding and offboarding automation turns the identities, approvals, access changes, and license decisions that matter to you into operational control and a financial case your leadership can evaluate.