IT onboarding and offboarding automation with clear ownership and completion records.
What it is
One accountable lifecycle for every joiner, mover, and leaver.
TeamJML AI brings onboarding and offboarding work onto a lifecycle record. Focused workspaces and a governed agent connect the request, decisions, required actions, and reported outcomes, reducing the effort of coordinating changes across HR and IT.
Joiner · My Requests
Onboarding starts before the account does.
Capture the start date, accountable manager, access, and equipment requirements before the account exists. The approved request coordinates account creation and the required IT work. HR, managers, and IT can track readiness against the start date; with TeamConnect AI, the configured workflow also supplies the new employee’s directory context.
Mover · Requirements
A new title isn’t always new access.
Compare the new requirements with the employee’s recorded entitlements. Create the required assignment or removal work without repeating tasks for unchanged access. Preserve access justified by another valid responsibility and send unknown states for verification rather than treating them as confirmed absence.
How requirements are evaluated →
Leaver · Completion
Follow required removals through to completion.
Assign owners to the account, application, subscription, and equipment tasks in the departure workflow. Record how each required action was completed, escalate unresolved work, and review outstanding tasks after departure. IT remains responsible for access changes and any systems outside the configured workflow.
HR Center
Every effective date deserves a clear view.
See upcoming starters, role changes, and leavers within your permitted scope, with approval progress, missing decisions, and readiness against each effective date. Focus HR attention on the changes that need follow-up.
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 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
Track license changes inside and outside Microsoft 365.
Keep required assignments, removals, and their reported outcomes on the lifecycle record. The confirmation method remains visible, whether a supported Microsoft 365 action, a connected ITSM, or an operator supplied it. IT can use these records when reporting license capacity and renewal recommendations to Finance.
Completion recorded. Review the outcome and confirmation method for each tracked assignment and removal, with unknown or unresolved states kept distinct.
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, renewal, or billing outcome reduces expenditure—not when an assignment is merely removed.
Unnecessary IT tickets avoided. No duplicate license work for unchanged entitlements; estimated labor value stays separate from cash savings.
One combined case. Include the selected products’ quoted subscriptions, applicable AI usage, and rollout costs. Count each benefit once.
By role: JML automation for IT leaders · SaaS license spend for finance leaders
Audit & compliance evidence
Keep access decisions and completion evidence together.
Reduce the effort of preparing access reviews by keeping requests, decisions, owners, reported outcomes, and exceptions on the lifecycle record. Your organization and auditors assess coverage and evidence sufficiency; a completed workflow does not guarantee that every possible access path has been removed.
Evidence trail
From approval to recorded completion, on one record.
Review who requested and approved the change, when they decided, the required actions, how completion was confirmed, and any escalations or recorded exceptions. Keep automated results distinct from operator confirmation.
Accountable approvals for every joiner, mover, and leaver
TeamJML AI records each decision with the decision-maker, the reason, and the time.
Confirmed assignments
Review assignment outcomes and their confirmation method rather than assuming that a requested action has been completed.
Confirmed revocations
Track required removals to a recorded outcome, with unresolved tasks and exceptions visible for follow-up.
Exceptions on record
Unfinished work stays on the record with its owner, instead of closing silently.
The first question IT asks
Set up onboarding and offboarding automation for your process.
TeamJML AI provides default policies and service targets as starting points. Confirm licensing, permissions, access bundles, responsible people, and execution routes, then test representative requests before production use. Standalone deployment does not require an HRIS replacement.
Where it happens
- Microsoft Marketplace
- Microsoft 365 Admin Center
- Microsoft Teams
- 01
Choose your subscription
Talk to sales for TeamJML AI pricing, licensed quantities, trial arrangements, and applicable AI usage terms.
- 02
Assign licenses
Assign the purchased licenses through the route confirmed for your subscription.
- 03
Open the app
Open TeamJML AI in Microsoft Teams and follow the setup steps for your tenant.
- 04
Review, configure, and test
Review the consent prompts, configure the default policies and access responsibilities, and test the required workflows before rollout.
Your existing environment remains
- No HRIS replacement
- No additional application servers
- Your service-desk process
Configuration
Onboarding and offboarding workflows, SLAs, and forms that fit your process.
Use the defaults to reduce setup work, then confirm the requirements, responsibilities, and service targets that fit your organization.
Approval routing and SLAs
Set approval routes and service targets before requests arrive. For example, route critical access to the CIO and Security and set a shorter target for an urgent departure. The deadlines reflect your configured policy, not a universal service guarantee.
Who carries out each task
IT can run supported Microsoft 365 account, license, and group actions from the ticket, route work through a connected ITSM, or confirm work completed by the service desk. Completion and its confirmation method remain on the 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.
TeamJML AI works independently with Microsoft Entra ID information, configured access bundles, and operational roles. With TeamConnect AI, it reuses the relevant managers, departments, offices, job roles, and license requirements, reducing duplicate setup. Completed work updates the relevant records through configured workflows.
Organization and role context
Use current responsibilities and role requirements to inform requests and approval routing.
Subscription and ownership context
Recorded assignments and removals help IT explain capacity and renewal requirements to Finance.
A shared employee directory
Reflect completed identity and organizational changes in the relevant directory records through configured synchronization.
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. Begin with a request before the account exists, then coordinate approved account creation, access, and equipment work. IT executes the supported actions or uses its connected service desk. With TeamConnect AI, the configured workflow also supplies the new hire’s directory context.
Does every promotion or department change create IT work?
No. Create assignment or removal tasks where requirements differ from recorded entitlements, and verification tasks for unknown states. TeamConnect AI adds job-role and related organizational context; standalone TeamJML AI uses configured access bundles. Unchanged access does not need duplicate work.
How do we know offboarding is complete?
Review the required tasks, recorded outcomes, confirmation methods, and any exceptions. TeamJML AI escalates unresolved work and supports checks after departure. Completion covers the configured workflow; IT must also assess systems and access paths outside that scope.
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?
Keep reused capacity, purchases avoided, and spending reductions separate. A confirmed license removal does not automatically reduce an invoice. Include quoted subscriptions for the selected products, applicable AI usage, and rollout effort; count each benefit once and keep time savings separate from cash outcomes.
What does TeamJML AI cost?
Talk to sales. Confirm the subscription price, licensed population, applicable AI usage terms, and any optional setup services in your quote. No fixed TeamJML AI price or credit allowance is published here.
Your other systems
Can we use TeamJML AI without TeamConnect AI?
Yes. Standalone TeamJML AI uses Microsoft Entra ID information, configured access bundles, and operational roles. Adding TeamConnect AI reuses a richer people, role, and catalog context, reducing duplicate maintenance without making it a requirement for standalone workflows.
Does TeamJML AI replace our service desk or HR system?
No. Each HR system remains the system of record for its own employee records. Ongoing imports and connectors, along with employee-contributed skills and career details in TeamConnect AI, remain relevant. TeamJML AI coordinates employee IT work while IT controls execution through supported actions, a connected ITSM, or its service-desk process.
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.