Employee directory and JML automation that keep each other current.
Why both
Each product solves its own problem. Together, the employee directory and JML automation stay aligned.
People data can go stale even though no service visibly stops. The effects reach search, collaboration, and AI answers, and then extend into business applications and workflows across Microsoft 365, Microsoft Power Platform, and Microsoft Dynamics 365. Especially where department, job title, or manager fields determine access or approval routing, stale values can leave access assigned to someone who has changed roles or send an approval to the wrong manager.
TeamConnect AI on its own
Find people and expertise, understand the organization, and then connect colleagues inside Microsoft 365. TeamConnect AI also provides a current organization and subscription baseline for leadership decisions.
Explore TeamConnect AI →TeamJML AI on its own
Approved, confirmed IT work for every joiner, mover, and leaver. It works from the Microsoft Entra ID user and the selected access bundle: the person exists, but not the organization around them.
Explore TeamJML AI →Better together
With the employee directory and JML automation connected, TeamJML AI uses TeamConnect AI’s people and role context to evaluate each lifecycle change. It also governs the approvals and fulfillment evidence, so completed changes keep the shared picture current.
What only the combination does
Five connected workflows when your employee directory and lifecycle share data.
Each one starts in one app and then finishes in the other.
Joiners
A new employee appears where people look.
The approved request in TeamJML AI drives the Microsoft Entra ID account, and the new employee takes their place in TeamConnect AI: findable in search, placed in the organization, and reachable in Microsoft Teams when onboarding completes.
Licenses
Licenses follow the role, not the ticket.
TeamConnect AI shows every person’s licenses as compliant, missing, extra, or unverified against their roles, groups, and bundles. TeamJML AI then turns each difference into assignment or revocation work and records it once confirmed, including every license outside Microsoft 365.
Catalog
One catalog, and every seat accounted for.
Platforms, subscriptions, and devices live in one catalog, managed in TeamConnect AI while TeamJML AI’s access bundles use it. Purchased, assigned, and available seats sit in one view, and seats freed by confirmed revocations can cover the next joiner before anyone buys another.
Leavers
Every leaver closes with evidence, and the employee directory follows.
Organization Insights in TeamConnect AI counts departed people who still have enabled Microsoft Entra ID accounts, while TeamJML AI closes each leaver with evidence. It confirms every required removal, escalates unresolved work, and verifies completion after the departure date. When the offboarding closes, TeamConnect AI and Microsoft Entra ID update, so the directory no longer shows someone who has gone.
Agent
One governed agent across both apps.
TeamJML AI’s lifecycle capabilities also join TeamConnect AI’s agent catalog: 550+ governed capabilities reachable from Microsoft Teams, Microsoft Outlook, and Microsoft 365 Copilot, each governed by Agent Roles, Microsoft 365 security groups, or both. Ask who has the skills you need, then which leavers still have unresolved access, in the same conversation.
The closed loop
How a change moves between the employee directory and JML automation.
TeamConnect AI knows the organization, TeamJML AI runs the change, while your service desk keeps doing the work in the tools it already uses.
Who contributes
- TeamConnect AI
- TeamJML AI
- Your service desk
- Microsoft Entra ID
- 01
Start with directory context
A manager or HR starts the change in TeamJML AI, while TeamConnect AI supplies the manager, department, office, and job role.
- 02
Entitle and approve
The shared catalog sets out what the role requires, and each decision then goes to its accountable owner.
- 03
Execute the difference
Only verified differences become work, which your service desk then runs from the ticket: Microsoft 365 changes directly, and everything else through your ITSM or by hand.
- 04
Confirm and update
Each line closes with its confirmation, TeamJML AI escalates unresolved work, and the change then updates TeamConnect AI and Microsoft Entra ID.
Works with
- ServiceNow
- Jira Service Management
- Freshservice
- BMC Helix
Who gains
Four leaders. One shared record.
With the employee directory and JML automation connected, the same lifecycle record answers the CIO, the CFO, the CHRO, and the CISO, each from their own angle.
For the CIO
Complete, approved requests reach the tools IT already runs, and license work arises only from verified differences, so IT avoids unnecessary tickets.
For IT leaders →For the CFO
Confirmed license changes inside and outside Microsoft 365, reused licenses, purchases avoided, and confirmed spend reduction, all in one combined case that also counts both products’ costs and no benefit twice.
For finance leaders →For the CHRO
A consolidated organization that stays current as joiners, movers, and leavers complete, while HR keeps its imports for contract details, CVs, and skills.
For HR leaders →For the CISO
Approvals with decision-makers and times, confirmed assignments and revocations, and escalated removals, ready when ISO/IEC 27001, SOC 2, or GDPR auditors ask.
See the audit evidence →Buying and rollout
Buy TeamConnect AI and TeamJML AI through Microsoft Marketplace, and start with either.
TeamConnect AI and TeamJML AI are both billed through your existing Microsoft account, and the second can follow whenever you’re ready.
Bought through Microsoft
Buy through Microsoft Marketplace or the Microsoft Teams Store under the Microsoft Standard Contract, with licensing and billing in your Microsoft 365 Admin Center and Microsoft Azure subscription. No Cubeet amendments and no separate contract to negotiate. Choose your plan and user count, then complete your purchase through Microsoft. Eligible Marketplace purchases can count toward your Microsoft Azure consumption commitment, subject to your agreement and purchase route.
Buying both? Start with TeamConnect AI.
Each app delivers value on its own, so either can come first. If you plan to use both, start with TeamConnect AI: approval policies, access bundles, and role-based license assignments are then built on real job roles, managers, departments, and offices from day one, instead of setting them up once and rebuilding them when the employee directory arrives.
Your stack stays yours
Your HR systems remain the source of HR records, your service desk keeps executing, and both apps also run inside Microsoft Teams, Microsoft Outlook, and Microsoft 365 Copilot.
Buyer questions
What buyers ask about the employee directory and JML automation together.
The questions that come up when IT, HR, Finance, and security evaluate the two apps together.
Do we need both apps?
No. Each works on its own: TeamConnect AI as the consolidated employee directory and governed agent, and TeamJML AI as the JML automation for every joiner, mover, and leaver. Together, TeamJML AI evaluates every change against the whole organization, and completed changes keep the directory current.
Is there a bundle price?
No. Microsoft Marketplace sells each app on its own, so you buy each one separately through Microsoft Marketplace or the Microsoft Teams Store. Licensing and billing then run in your Microsoft 365 Admin Center and Microsoft Azure subscription.
Which app is the master for the catalog?
In fact, there is one catalog of platforms, subscriptions, and devices. With both apps, TeamConnect AI is the master and maps subscriptions to job and license roles; TeamJML AI’s access bundles then use the same catalog.
Does TeamJML AI replace HR imports into TeamConnect AI?
No. A request carries no contract details, vacation, CVs, bios, or skills, so HR keeps running file imports and connectors in TeamConnect AI, and a person must exist in Microsoft Entra ID before HR can import them.
Does either app replace our service desk or HR systems?
No. Your HR systems remain the source of HR records, while your service desk remains central to IT delivery. The two apps connect the change, the organization, the approvals, and the confirmed outcome.
Can we start with one app and add the other later?
Yes. Both apps run on the same backend and share one catalog, so the second app connects to what is already in place.
Bring your organization
See the employee directory and JML automation on your own people and licenses.
Bring a joiner, a mover, and a leaver, and we then walk them through both apps inside your Microsoft 365. Or start with the Microsoft Entra ID Health Check instead, and see what Microsoft Entra ID holds today.