A laptop displays a connected workforce management dashboard with organizational charts, analytics, user profiles, and security controls.
Ask Copilot "what's the headcount in Priya's org?" and today you might get a polite guess, a stale org chart, or an answer that counts contractors, interns, and that vendor who left in 2023. At Ignite 2026, Microsoft announced what it says is the fix. "People and org context" is a new layer in Work IQ that brings HR data, company-specific definitions, and analytical reasoning into Microsoft 365 Copilot and Cowork.

The pitch is easy to like. The details explain who can actually use it, and when. Some parts are generally available and some are limited to Microsoft's Frontier early-access program. Admins also have setup work to do before Copilot can tell a direct report from a dotted line.

A laptop displays a connected workforce management dashboard with organizational charts, analytics, user profiles, and security controls. What Work IQ is​

Microsoft's product page calls Work IQ the intelligence layer that connects Copilot and agents to your organization's knowledge, context, people, and work. Work IQ was announced at Ignite 2025. It has since become the base for Copilot's grounding, and Microsoft says it gives developers grounded, permission‑aware access to live work context across Microsoft 365 and connected business systems through MCP, A2A, and REST.

Until now, much of that context came from collaboration signals: mail, meetings, files, and chats. This release adds structured people and HR data. The announcement describes two pieces. Microsoft 365 Organizational Data Service connects people and org data to Copilot, and Workforce Insights Agent adds context to this data, while also providing a configuration and ongoing validation workspace.

In short: Work IQ already knew who you email. Now it can also know who reports to whom, what a "job family" means at your company, and whether a particular "contingent worker" counts toward headcount.

What Microsoft announced​

Microsoft built the feature around three principles:

  • Governed: answers come from authoritative people data and follow existing Copilot permissions.
  • Intelligent: natural-language analysis can produce counts, ratios, percentages, rankings, and averages across teams without anyone building a report.
  • Contextualized: answers use the organization's own terminology, attribute definitions, metrics, and guidelines.

Example prompts in the announcement:

  • What is the headcount in [leader]'s org?
  • What is the manager-to-individual-contributor ratio in [leader]'s org, and how does it compare to company guidelines?
  • Who in my org has experience with machine learning?

Custom attributes such as job families and business units can ground answers, and Copilot can answer questions about how skills are spread across teams.

The Cowork plugin for leaders​

Leaders get a Workforce Intelligence plugin for Cowork, available only in Frontier. It ships with three skills:

  1. Organizational snapshot: headcount, team makeup, layers, spans, and manager-to-IC ratios.
  2. People skills landscape: which skills exist across teams, to guide upskilling or reskilling.
  3. Organizational dashboard: reusable, customizable, shareable dashboards for leadership reviews.

Microsoft's sample prompt asks Cowork to build a dashboard app with headcount, org depth, average span, manager percentage, senior-and-above percentage, hire rate, and engineer-to-PM ratio, broken down by sub-org. Whether your tenant can produce every one of those metrics depends on the data you've imported. Cowork can't compute a hire rate from data you never gave it.

The admin side: Workforce Insights Agent​

Microsoft calls Workforce Insights Agent the agentic configuration and validation workspace where admins and HR specialists curate and adjust the organizational context for richer Copilot experiences. Admins can add attribute descriptions, set organizational context, and test how changes affect answers. Microsoft's sample configuration prompts include asking the agent to explain how it calculated a headcount that looks wrong, and asking it to use an attached workforce glossary.

On access, Microsoft says Workforce Insights Agent continues to be accessed in Frontier to organizations with Microsoft 365 Copilot licenses.

What's GA and what's Frontier​

This is where the announcement and real deployment can differ, so check it before you promise anything to your CHRO. Microsoft's table, with rollout described as continuing through December:

CapabilityWhat it doesStatus
Authoritative people and org data (standard and custom attributes)Answers grounded in HR data brought into Microsoft 365GA
Analytical reasoningCounts, ratios, percentages, averagesGA
Organizational skills insightsHow skills are distributed across teamsGA
Organizational contextAnswers that use company terminology and definitionsFrontier
Context and attribute configuration (in agent)Curating descriptions and context in Workforce Insights AgentFrontier
Domain-grounded skills via Cowork pluginRepeatable leader workflowsFrontier

There's a wrinkle. Microsoft Learn's configuration guide for Workforce Insights Agent says attribute descriptions and access policies already apply to organizational queries in Microsoft 365 Copilot. It describes support for organizational context in Microsoft 365 Copilot as planned. Taken together, the blog and Learn suggest the "your company's own language" feature will reach the main Copilot experience in stages. Don't assume it works in every surface on day one.

The blog gives no per-tenant dates, so "through December" is a window, not a promise.

What admins need to do​

The announcement focuses on the user experience. Microsoft Learn documents the setup work, and that's where IT spends its time.

1. Check licensing and enrollment​

According to Microsoft Learn, Workforce Insights Agent (Frontier) requires a paid Microsoft 365 Copilot license and tenant enrollment in the Frontier program. Skills questions also require People Skills to be enabled and licensed. Learn also says the agent is optimized for English while in Frontier. Chat works in all Copilot languages, but delegation, reports, and admin experiences are English-only.

2. Assign least-privilege roles​

The Organizational Data Service getting-started guide says only Global Administrators and Organizational Data Source Administrators can upload data. Provisioning happens in the Microsoft 365 admin center under Setup > Migration and imports > Organizational Data in Microsoft 365.

The Workforce Insights configuration guide is direct about roles:

  • Use Organizational Data Source Administrator for importing and maintaining HR data.
  • Use AI Administrator for managing Copilot and agents.
  • Reserve Global Administrator for rare tasks such as assigning roles, not routine work.

3. Choose an ingestion path​

Microsoft Learn lists these connector options for Organizational Data Service:

  • CSV import: suited to pilots and one-time imports.
  • Workday connector: pulls data through Workday's SOAP APIs.
  • SAP SuccessFactors connector: pulls through SuccessFactors APIs, with an optional middleware path.
  • Azure Blob Storage connector: for multiple HR systems or a data lake, with PGP encryption support.
  • API-based connector (public preview): for custom HR systems, including Workday EIB flows.

The direct Workday and SAP connectors only suit you if your required attributes are exposed through those APIs and need nothing more than simple attribute mapping. If your data needs transformation first, Learn recommends the Blob or API route.

4. Map and share custom attributes deliberately​

Learn says public attributes such as name, title, department, and location flow to Microsoft 365 Profile automatically. Custom attributes do not. An admin has to choose to send each one. The guide adds that every attribute needs a description, and without one, users might not be able to ask about it. If Copilot "can't see" your business-unit field, check that first.

5. Watch the SupervisorIndicator migration​

This one can quietly break existing setups. Learn says that starting October 1, 2026, SupervisorIndicator and WeeklyBadgeDays are no longer sent to Workforce Insights Agent as reserved fields. Existing customers who use them should copy each field under a new name (Microsoft's examples are SupervisorIndicator2 and WeeklyBadgeDays2), map it to Microsoft 365 Profile as a custom field, and point Workforce Insights at the new field. SupervisorIndicator overrides the default rule that anyone with a direct report counts as a manager. If your manager-to-IC ratios changed sometime after October, this migration is a likely suspect.

6. Treat org context as visible to everyone​

Learn warns admins to assume everyone in the company can see what goes into org context, because it can appear in answers. Keep personal and sensitive employee details out. Learn also notes that AI answers can vary even with the same context, and that org context doesn't add to or change the underlying workforce data.

In short: this is an HR data project with an AI interface on top. Licensing, roles, connectors, attribute mapping, and descriptions all need to be done before Copilot gives a reliable headcount.

Analysis: promise vs. practice​

Credit where it's due. Most enterprise AI disappointment comes from missing context, not weak models. A model can't know that your "FTE" excludes interns in Germany unless someone tells it. Making that context an admin-curated setting is the right design, and the SupervisorIndicator override shows Microsoft has thought about how org data gets messy in practice.

Some caution is also warranted:

  • There's no accuracy data. The announcement claims "accurate" and "trusted" answers but publishes no benchmarks or error rates. Microsoft's own documentation says answers can vary. If a leader's dashboard shows an engineer-to-PM ratio, check it against your HR BI system before it goes into a board deck.
  • Permissions control access, not interpretation. Respecting existing Copilot permissions is the minimum. The harder question is what a manager does with a span-of-control chart. Microsoft says the feature is not for monitoring employee performance, and Learn says the agent isn't built to make employment decisions. Learn also tells admins to follow data protection laws and Works Council guidance, which European tenants will take seriously.
  • Restricted-data handling isn't here yet. Microsoft lists support for restricted data, meaning analysis limited to the people data each user is permitted to see, as something it is exploring. The same goes for more guided leader workflows and response tuning. Treat these as roadmap items, not launch features.
  • Frontier is a moving target. Learn says Frontier features are subject to change, and the most distinctive parts of this launch, organizational context and the Cowork plugin, are in Frontier.

Is this better than asking HR? For quick questions like "who knows ML on my team?", probably yes. For anything that feeds a reorganization, use it as a starting point for analysis, not the final answer.

Ignite sessions​

Microsoft listed these sessions for people who want more detail:

  • THR853: Tue Nov 17, 2:35–3:00 PM PT. Build AI-ready teams with Work IQ people and organizational context.
  • BRK210: Wed Nov 18, 1:45–2:30 PM PT. Engineering the Frontier Firm: How Work IQ Powers Copilot.
  • TT1658: Wed Nov 18, 2:25–3:10 PM PT. Transform HR workflows with Microsoft Copilot.
  • TT1659: Thu Nov 19, 2:25–3:10 PM PT. Work IQ in Copilot: Turning Work Context into Outcomes.

Bottom line​

People and org context brings Copilot closer to correctly answering one of the most common workplace questions: who does what here? The GA parts (grounding in standard and custom attributes, analytical reasoning, and skills insights) are worth piloting now if your HR data is already in Organizational Data Service. The parts that would make it feel tailored to your company (organizational context, admin curation in Workforce Insights Agent, and the Cowork leader plugin) require Frontier enrollment and some patience.

Before you start, admins should:

  • Confirm Copilot licensing, Frontier enrollment, and People Skills status.
  • Assign Organizational Data Source Administrator and AI Administrator roles instead of using Global Admin.
  • Pick the right connector for your HR system.
  • Explicitly share custom attributes and write a description for every one.
  • Migrate SupervisorIndicator and WeeklyBadgeDays to custom fields if you use them.
  • Keep sensitive details out of org context, and check answers against your HR BI system before anyone acts on them.

The answers will only be as good as the HR data and definitions you feed in.

 

References

  1. Copilot that understands your organization: Introducing people and org context in Work IQ Microsoft Copilot Community 2026-11-16T16:30:00+00:00
  2. Work IQ: Agentic AI Solutions microsoft.com
  3. Copilot that understands your organization: Introducing people and org context in Work IQ | Microsoft Community Hub techcommunity.microsoft.com