The employee directory for Microsoft Teams that finds the right expertise.

Yes — and more than an employee directory. Indeed, it is the employee, department, and office directory for Microsoft 365, running natively inside Microsoft Teams, Microsoft Outlook, and Microsoft 365 Copilot.

Those three are where it runs, while it integrates directly with the rest of your Microsoft 365. Communication: Microsoft Teams chat, group chat, call, video, Meet Now, and channels. Workplace: Microsoft Outlook calendar and email, Microsoft Places, and Microsoft Shifts. Identity and administration: Microsoft Entra ID, Microsoft Entra Agent ID, Microsoft 365 security groups, and the Microsoft 365 Admin Center. Profile and content: Microsoft People, the Microsoft 365 user profile, and Microsoft SharePoint Online.

Microsoft People and Org Explorer show what Microsoft Entra ID holds. TeamConnect AI then adds what an enterprise directory needs on top: skills and certifications with validation, work and project experience, direct and dotted-line org charts across employee, department, and office hierarchies, the Collaboration surface, an AI agent governed by role, and HRIS integration through 50+ connector and import/export templates.

It also works the other way. The bidirectional Microsoft Entra ID sync writes the updated data back, so Microsoft People, Org Explorer, and Microsoft 365 Copilot all read the same current information. So you are not choosing between them — you are keeping them from going stale.

The same agent and the same data serve everyone. However, what differs is what the agent may answer for each person, within their role and scope. For example, an employee asks which colleagues with a given skill are free this afternoon and gets a short list. Meanwhile, a CHRO asks about skills coverage by job role and gets the analytics. 50+ Agent Roles decide what may be returned, compared, and disclosed.

No. It is engineered for the largest Microsoft 365 tenants and built for 500,000-user scale — and the governance model, the matrix org charts, and the data quality controls all come from what organizations that size demand.

However, a 2,000-person company across six countries has the same problems as a 200,000-person one: time zones and languages, dotted-line reporting, availability nobody can see, skills, work and project experience nobody can search, and people data nobody owns. The difference is therefore volume, not structure. Same product, same capabilities, two global admin consents either way.

Often not. Buy through Microsoft Marketplace or the Microsoft Teams Store under the Microsoft Standard Contract. 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. Billing arrives on your existing Microsoft invoice.

Yes. The two are compatible, so each person can be licensed on the edition their work needs, for example TeamConnect for most employees and TeamConnect AI for management, sales, and roles that work across departments. Because TeamConnect AI includes the TeamConnect foundation, nobody needs both.

Initially, it comes from Microsoft Entra ID, where every employee already exists, after the free Microsoft Entra ID Health Check shows how current that data is. Job titles, departments, and managers are HR data held in a system IT owns, so nothing breaks when they go stale.

That is why the Employee Import Hub and the Integration Hub then bring in the current values from your HR systems, manually or on a schedule. Finally, the bidirectional sync writes the fields IT chooses back to Microsoft Entra ID, so Microsoft 365 sees them too.

The Employee Import Hub and the Integration Hub are designed so that a single HRIS source is onboarded and tested in less than a working day, each using a pre-built template from the connector-template library. A twenty-source estate is planned in working days rather than quarters.

TeamConnect AI ships with 50+ connector templates covering HRIS, ITSM, and enterprise architecture platforms. The Integration Hub handles field direction, mapping, and handoff rules explicitly, and every import, export, and sync runs on its own schedule. That last part matters more than it sounds: nobody in HR has spare capacity to refresh a directory by hand, and anything that depends on someone remembering goes stale.

A downloadable PDF report on the people data held in your Microsoft Entra ID — the directory Microsoft People, Org Explorer, and Microsoft 365 Copilot all read from. Specifically, it scores seven categories — identity, job info, managers, departments, department managers, offices, and contacts — and names the specific issues found, with examples from your own tenant. It analyzes every user rather than a sample, and the report is yours to keep, share, and re-run.

The TeamConnect Health Check, under HR Operations, scores every field across the whole population, for example how many records carry a job title, a cost center, a manager, or a photo. Below the scores, it lists who is missing what, with a completion percentage for each person, so the gap goes to whoever maintains it instead of staying in a dashboard.

It is a different check from the Microsoft Entra ID Health Check, because that one scores Microsoft Entra ID, while this one scores TeamConnect AI.

Your people and organization records are stored in SharePoint Online within your own Microsoft 365 tenant. TeamConnect accesses those records directly through Microsoft Graph, with no intermediary Cubeet database. TeamConnect AI also adds processing hosted in Microsoft Azure for the AI agent and automated imports, exports, synchronization, and API integrations, under the permissions you grant.