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
Microsoft IQ connects business context to agents
All about AI

Microsoft IQ connects business context to agents

Microsoft IQ brings organizational knowledge and data together so agents can use relevant context across business workflows.

Key insights

  • Work IQ makes Microsoft 365 chats, email, documents and SharePoint files available as agent context.
  • Fabric IQ exposes metrics and KPIs defined in Power BI semantic models to agents.
  • Foundry IQ brings organizational knowledge from content such as contracts and technical manuals into agent workflows.
  • IT can review plugins in a shared registry and approve them for groups or block them.
  • A business plugin can combine process rules, data, knowledge and connections for reuse by agents.

Microsoft IQ brings organizational knowledge, business data and collaboration context together so AI agents can use relevant information across workflows. It matters to IT teams, developers and business experts who want agents to work with company-specific context and remain governed. Microsoft Events demonstrates the approach with a supply-chain scenario that connects a reusable skill, business context and IT-approved plugins.

What's new

Microsoft IQ is presented as an enterprise context management platform: a shared way to make organizational context available to agents rather than rebuilding separate knowledge connections for each one. The context can include collaboration data, business data, unstructured content and selected information from the web, alongside connections to enterprise systems.

Its named components serve different context needs. Work IQ provides collaboration context from Microsoft 365, including chats, email, documents and SharePoint files. Fabric IQ makes metrics and KPIs in Power BI semantic models available to agents, while Foundry IQ provides knowledge bases that can bring together material such as contracts, precedents and technical manuals. Web IQ is described as a way to selectively bring web context into the system.

The aim is not to give every agent access to everything. Instead, an agent can draw on context suited to its task, with permissions and governance kept in view. The session also describes an open, extensible platform: organizations can use a Microsoft-provided harness or bring their own, and can supply their own tools.

Who it is for and what you need

The platform is aimed at organizations that want to reuse business knowledge across multiple agents and workflows. Business experts can contribute process knowledge; engineering can connect skills to business systems; and IT can review and govern plugins before they reach those systems.

The demonstrated scenario starts with Microsoft 365 work data and a Power BI semantic model. In the example, Work IQ finds relevant collaboration information, while Fabric IQ supplies supply-chain metrics. Foundry IQ contributes a knowledge base, and a business plugin combines these with process rules, approval information and a custom plugin.

The session also describes more than 350 connectors to third-party business systems and says Microsoft IQ can work with Copilot, Foundry, and assistants such as ChatGPT and Claude. These are platform capabilities described in the presentation, not a checklist of prerequisites for every organization.

How it works

The supply-chain example shows how a one-off investigation can become reusable, governed context. A planner first asks Copilot about a supplier delay. Work IQ checks relevant Microsoft 365 information, but the initial investigation cannot identify all affected orders, costs or supplier commitments because those details are in other business systems.

  1. Turn the investigation into a skill. The planner asks Copilot to make the investigation reusable. The demonstration shows a background task that asks for approval before touching a file, then documents the skill in plain language for the team to review and change.
  2. Connect the skill to business systems. Engineering turns it into a plugin connected to procurement, inventory, production and sales through MCP, an open standard for connecting AI to business systems.
  3. Review and approve the plugin. In the Microsoft 365 admin center's Tools area, IT can view plugins in a registry, inspect what they connect to and approve them for a group. The demonstration also shows IT blocking or unblocking a plugin.
  4. Assemble the business context. A business expert creates a business plugin that combines process rules, a Fabric IQ semantic model, a Foundry IQ knowledge base, relevant team context and the custom supply-chain plugin. The expert adds guidance about when it applies and certifies it.
  5. Ask the question again. Copilot uses the business plugin to select relevant context and call supporting plugins. In the scenario, it identifies retailer penalties, the supplier's responsibility for expediting costs and the manager who approves expedite requests.

The practical distinction is between an isolated skill and a business plugin that packages process knowledge and context for reuse. The demonstration says that agents in Copilot and Foundry can use the resulting context.

Limitations and alternatives

The example makes clear that collaboration data alone may not answer operational questions. The first investigation finds the delay notice but not the affected orders, cost or supplier agreement; those details require business data and process context from other places. Connecting and organizing that context is therefore part of making an agent useful for real work.

Governance also remains a distinct step. In the demonstration, plugins that connect to company systems are reviewed through IT, and access can be approved for a group or blocked. The business expert certifies the business plugin after adding its process context. This illustrates a division of work: subject-matter experts contribute process knowledge, while IT controls access to system-connected plugins.

For teams considering the approach, the scenario offers a useful starting point: identify a recurring task, locate the data and expertise it depends on, and decide who should approve the resulting workflow. The platform's value in the example comes from combining those inputs selectively rather than loading all company context into every request.

Sources

Frequently asked questions

What does Microsoft IQ do?

Microsoft IQ is described as an enterprise context management platform that brings organizational context together for use across agents. Its components include Work IQ, Fabric IQ, Foundry IQ and Web IQ.

How does Microsoft IQ use Microsoft 365 data?

Work IQ makes collaboration data such as chats, email, documents and SharePoint files available as context. The session says it respects existing Microsoft 365 permissions.

How can IT govern plugins in the Microsoft IQ example?

The demonstration shows plugins in a registry in the Microsoft 365 admin center's Tools area. IT can inspect connections, approve a plugin for a group, or block and unblock it.

Can Microsoft IQ use data from Power BI?

Fabric IQ makes metrics and KPIs defined in Power BI semantic models available to agents, with security and permissions intact.