Pro User
  • All of Microsoft
  • My Role
    • All in My Role
    • Pro User
    • Administrator
  • Focus
    • All in Focus
    • Microsoft Ignite 2026
    • Microsoft Copilot
    • All about AI
    • M365 Admin
    • What's Hot
    • M365 Release
Timespan
explore our new search
Work IQ adds people and org context to Copilot
Microsoft Copilot

Work IQ adds people and org context to Copilot

Work IQ helps Copilot answer workforce questions using organizational data and company-specific definitions, with controls that respect existing permissions.

Key insights

  • Work IQ people and org context grounds Copilot answers in organizational data and company-specific terms.
  • People connectors can import authoritative HR data; Microsoft lists this connection step as generally available.
  • Configuring and validating organizational context is described as Frontier public preview.
  • A Workforce Intelligence plugin in Frontier adds conversational organizational analysis in Cowork.
  • Skills questions currently use public data; a phased private preview is starting for access-controlled data.

Work IQ adds people and organizational context to Microsoft Copilot, helping it answer workforce questions using organizational data, business definitions, and reporting relationships. It matters to employees asking about colleagues and teams, as well as leaders and HR teams analyzing staffing, skills, and organizational structure. Microsoft Events demonstrates Copilot and Cowork scenarios and the configuration ideas behind them in a Microsoft Ignite session.

What's new

Work IQ is Microsoft’s intelligence layer for Copilot and agents. The people and org context capability gives Copilot structured information about people and teams, alongside customer-defined terms and rules that explain how the organization works. That context can help resolve ambiguity that ordinary document search cannot: for example, an organization’s definition of “headcount” may include regular employees but exclude vendors.

The capability is presented around three qualities: intelligent, governed, and contextualized. It can analyze organizational data to answer questions and perform calculations; its answers are intended to respect existing permissions and rely on authoritative data; and responses can reflect company-specific terminology and metrics. The practical value is that users can ask questions in natural language without first exporting data or reconciling different definitions by hand.

Examples include finding managers in someone’s reporting chain, calculating a team’s headcount, comparing team sizes, or calculating the ratio of engineers to product managers. Skills questions can also break down where particular skills appear by discipline and work location. For leaders, the more involved analysis can compare an organization’s structure with its own guidelines, such as expected manager spans or team sizes.

Who it is for and what you need

Employees can use organizational context to find colleagues by skill or understand reporting relationships. Leaders and HR teams can use it to explore staffing patterns, team structures, and skills distribution. These answers depend on organization data being available and on definitions being supplied where a company needs a consistent meaning for terms such as headcount.

Administrators and people-data owners have a role in connecting authoritative HR data and improving the context Copilot uses. Microsoft describes importing workforce data through people connectors, including Microsoft 365 organizational data service or Copilot connectors, as generally available. The separate configuration and validation experience—defining terms, reviewing context, and testing responses—is described as Frontier public preview.

The Workforce Intelligence plugin for Cowork is also described as being in Frontier. Research on the feature identifies the Workforce Insights Agent as requiring a paid Microsoft 365 Copilot license and tenant enrollment in Frontier. Access-controlled workforce data is at an earlier stage: a phased private preview is starting for permission-restricted information, while the skills examples described use public data.

How it works

There are three practical parts: provide reliable organizational data, explain how the organization interprets it, and test whether Copilot applies that context correctly. The data supplies facts such as employees, teams, roles, and reporting lines. The context layer adds business definitions and guidelines, so that calculations and descriptions match the organization’s rules rather than an assumed default.

  1. Connect the data. Import authoritative HR information using people connectors, such as Microsoft 365 organizational data service or Copilot connectors.
  2. Configure organizational context. Define terms and business rules, and provide existing organizational context documents. The Workforce Insights Agent can help analyze, review, and validate this context.
  3. Validate with test questions. Use natural-language queries to check how Copilot applies the definitions and guidelines. Review the responses and refine the context where they do not match the intended interpretation.
  4. Ask workforce questions. Users can query Copilot about reporting chains, headcount, team averages, or skills. In Cowork, the Workforce Intelligence plugin supports broader conversational analysis, such as assessing structure against organizational guidelines.

A key detail is that definitions affect the answer, not just the wording. If the default headcount rule counts regular employees, Copilot can use that rule consistently; a user can still ask a more specific question, such as headcount including vendors. Likewise, a skills analysis depends on the skill profiles and workforce data available to the organization.

Limitations and alternatives

Data quality and context quality are central to the approach. If organizational records are incomplete or a definition is unclear, an answer may not reflect the organization’s intended view. Administrators should therefore test representative questions and check whether the data and rules support the decisions leaders plan to make.

Availability differs by component. Connecting people data is described as generally available, while configuring and validating context and using the Workforce Intelligence plugin are associated with Frontier. Access-controlled workforce information is in a phased private preview, so the skills examples based on public data should not be treated as proof that every permission-restricted scenario is available.

Copilot can already answer from business content and collaboration context, but questions about reporting lines, standardized workforce metrics, or org-wide patterns need suitable people data and definitions. For organizations that do not have that context configured, existing reports and data exports remain a way to examine workforce information; the session positions natural-language analysis as an additional way to explore it.

Sources

Frequently asked questions

What does Work IQ people and org context do?

It grounds Copilot responses in organizational data, people and team relationships, and company-specific definitions. This supports questions about reporting lines, headcount, team size, and skills.

Is Work IQ organizational context generally available?

The people-data connection step is described as generally available. Configuring and validating organizational context is described as Frontier public preview, and the Workforce Intelligence plugin is in Frontier.

What is needed to configure organizational context?

Organizations connect authoritative HR data through people connectors, define terms and business rules, and test responses with natural-language queries. The configuration and validation experience is in Frontier public preview.

Can Copilot analyze access-controlled workforce data?

A phased private preview is starting to bring in permission-restricted workforce data. The skills examples described use public data.