JML automation that proves every leaver is locked out.
Your week today
Why HR changes turn into directory upkeep for IT.
Job title, department, manager, and office are HR data held in a system IT owns. Stale values do not cause an obvious service interruption, so nothing triggers an update, but they still reach search, collaboration, and AI answers, and any workflow that routes on department or manager.
Why is IT editing HR data?
Title, department, and manager changes land on the service desk, although they are HR facts.
Did every access change happen?
Movers and leavers change access across several systems, but nothing confirms each change was made.
Can we prove it to the auditor?
Regulators do not test whether you have a disabling procedure. Instead, they ask you to show that removal was verified, person by person. When that proof sits across tickets, emails, and admin consoles, not being able to produce it is itself the finding.
What changes for IT
Directory upkeep moves out. JML automation comes in clean.
Your team does less work that was never IT’s, and it can also prove the work that is.
Service desk · TeamJML AI
JML automation without building your own.
Approvals, routing, and deadlines configured rather than coded, with each request worked in Microsoft Teams and closed on one lifecycle record.
Movers · TeamJML AI
Only real access changes enter the JML process.
A promotion or department change updates the organization without creating IT work, and licenses follow the job role, so tickets appear only when entitlements actually change.
Directory upkeep · TeamConnect AI
No more directory upkeep tickets for titles and managers.
Titles, departments, and managers stay current in Microsoft Entra ID without your team touching them, in the fields you choose — so Microsoft 365 Copilot, search, and every workflow that routes on manager or department work from current data.
Exposure · Organization Insights
See the offboarding gap before an auditor does.
In Veza’s 2025 identity security research, former employees still holding active credentials made up 3% of all users in the environments it measured. Organization Insights counts leavers whose Microsoft Entra ID accounts are still enabled, without naming anyone, so you know whether offboarding actually works.
Leavers · TeamJML AI
Offboarding you can prove, leaver by leaver.
TeamJML AI confirms every required removal, escalates unresolved work, and verifies completion after the departure date, so the evidence is ready when ISO/IEC 27001, SOC 2, or GDPR auditors ask.
Governed agent · TeamConnect AI
AI that answers only what each role may ask.
One agent in Microsoft Teams, Microsoft Outlook, and Microsoft 365 Copilot, with 550+ capabilities governed by Agent Roles, Microsoft 365 security groups, or both, so each role gets only the answers it may receive.
Subscription analytics
The number you owe the CFO, from your IT spend.
Every license tied to the person and role holding it, so you can show what is used, what sits idle, and what it costs.
Spend you can explain. Monthly and annual cost across every platform, by department, cost center, region, or vendor, so the CFO sees where it goes.
Utilization, measured. The share of purchased licenses with a recorded assignment, with unmeasured contracts named rather than hidden.
Unassigned capacity, priced. The monthly cost of licenses nobody holds, ready to review before the next renewal.
One export, in your currency. The same numbers IT reports, so Finance can sign them off.
What your team gets
What your team gets from JML automation.
New hires, ready on day one
The approved request reaches your team with the start date and everything the role needs, so access is ready before the first day.
Every access change, under IT’s control
Every change that touches access reaches your team as a ticket, so IT stays in control of who gets access and whose access is disabled or deleted. Your team can then run the Microsoft 365 account, license, and group changes straight from that ticket, without opening an admin console. Each task is confirmed in the same ticket, whether Microsoft 365, your ITSM, or your team completed it, and IT closes it when the work is done.
People as complete as your agents
Agents arrive in Microsoft Entra Agent ID with a manager, an owner, a sponsor, and a description of what they can do. Because HR keeps people data current in TeamConnect AI, your employees’ profiles become just as complete, and your team doesn’t have to maintain them.
For IT and security
Two global admin consents per app.
Nothing to host, patch, or scale.
Cubeet hosts and maintains the application, so your team runs nothing and patches nothing.
Your people data stays in your tenant.
SharePoint Online inside your own Microsoft 365 stores the people and organization records, while all Microsoft 365 data access runs through Microsoft Graph.
Not used for AI training.
The agent’s prompts and answers pass through Cubeet’s Microsoft Azure backend to be answered, but neither trains foundation models.
Other leaders
The same data answers different questions.
For Executive leaders
One headcount answer you can put in front of the board.
For Finance leaders
License spend you can prove, and a savings number that survives audit.
For HR leaders
Know what your global workforce can do.
IT questions
What IT leaders ask about JML automation.
The questions that come up when IT and security evaluate TeamConnect AI and TeamJML AI.
Do we need an ITSM to use TeamJML AI?
No. Requests can be worked in Microsoft Teams, and if you run ServiceNow, Jira Service Management, Freshservice, or BMC Helix, the work goes there instead, with completion coming back to the same lifecycle record.
Which fields are written back to Microsoft Entra ID?
The ones your administrators choose, and then only on a manual or scheduled sync.
Does disabling an account 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.
What do auditors ask for at offboarding?
Evidence that removal happened, rather than a policy describing it. Under GDPR Article 32, failing to take appropriate technical and organizational measures to secure personal data carries a maximum of €10 million or 2% of global annual turnover, whichever is higher. European data protection authorities have found against organizations whose former employees retained access after leaving, and have stated that a procedure for disabling access is not sufficient on its own — there must also be a system to follow up and check that access was effectively removed. ISO 27001 Annex A 5.11 sets the same expectation for leavers, where auditors ask for completed evidence rather than a documented policy. TeamJML AI therefore produces that record as part of the lifecycle, with each confirmation and any recorded exceptions kept together.
For IT leaders
See JML automation run end to end.
We’ll walk a joiner, a mover, and a leaver through approval, IT work, and finally the evidence that closes each one. See a sample Microsoft Entra ID Health Check report. Weighing the cost? See the business case first.