Microsoft Work IQ and the Work IQ MCP Server: The Complete Guide for Agentic AI Architects (2026)

An enterprise sales manager asks Copilot a straightforward question: “Which of my renewals are at risk?” The CRM shows green across the board — every deal is on track. But behind that clean dashboard, a service ticket has been open for three weeks, the customer’s last two emails carried a frustrated tone, and a custom equipment app logged a failed deployment. The CRM never saw any of that. Copilot, grounded only in the CRM, gives a confidently wrong answer.

This is the context gap that kills enterprise agent projects before they deliver value. According to Microsoft, it’s also the exact problem that Work IQ — the intelligence layer beneath Copilot and AI agents — was built to solve. With its public preview rolling out through October 2026 and ERP support landing in late October, Work IQ represents Microsoft’s most consequential bet on what separates toy agents from production agents: not better models, but better business context.

This guide breaks down the architecture, the MCP server, the governance model, and the practical implications for RPA and automation teams evaluating whether to build their next generation of agents on the Microsoft stack.

What Is Microsoft Work IQ?

Work IQ is the shared business-context layer that grounds Microsoft Copilot and AI agents in an organization’s actual data — email, calendar, Teams conversations, Dynamics 365 records, Power Platform apps, files, and people. Rather than forcing each agent to build its own retrieval pipeline, Work IQ provides a single semantic model that every agent in the organization can share.

It sits within the broader Microsoft IQ umbrella, announced at Build 2026 on June 2. That umbrella includes four engines that compose together:

Work IQ reached general availability on June 16, 2026, with its core APIs, A2A (agent-to-agent) protocol support, and redesigned remote MCP server. The October 2026 milestone extends its grounding to Dynamics 365 Sales and Customer Service, Power Apps, and third-party line-of-business applications — and late October adds Dynamics 365 Finance and Operations, bringing ERP data into the same context layer.

For teams that have been building agents around the A2A and MCP protocols, Work IQ is significant because it’s not just another API — it’s Microsoft’s answer to the question of how agents understand a business well enough to take action on its behalf.

The Architecture: How Work IQ Grounds Agents in Business Data

Work IQ’s architecture has four layers, each solving a distinct piece of the “make agents actually useful in enterprise” problem:

More Read

ServiceNow AI Control Tower & Action Fabric: Complete Guide (2026)

Agent Harness vs. Context Engineering: The Next Evolution of AI Agent Architecture with LangGraph

Claude Sonnet 5 vs GPT-5.6 vs Grok 4.5 vs Muse Spark 1.1: The July 2026 Agentic AI Model Showdown

1. The Chat Layer

The top layer supports two integration patterns: A2A (agent-to-agent protocol) for agent delegation and REST for web application interactions. Responses are fully processed and carry the same quality as Copilot’s own answers. This means a third-party agent built on LangChain or CrewAI can call Work IQ through A2A and get back contextually grounded responses — not raw data that the agent has to interpret from scratch.

2. The Context Layer

This is where Work IQ does its heaviest lifting. It assembles and grounds context internally, so agents never need to build their own retrieval pipelines. The context layer draws from:

• A semantic model derived from existing Dynamics 365 and Power Apps artifacts — views, forms, entity relationships, and a business glossary for company-specific terminology
• Microsoft 365 signals — email threads, Teams conversations, calendar events, shared files, and collaboration patterns
• Third-party LOB applications connected through the platform

Critically, every agent using the semantic model shares the same interpretation of entities like accounts, contracts, and service cases. This eliminates the “agent A thinks ‘customer’ means a CRM contact while agent B thinks it means an Azure AD identity” problem that plagues multi-agent deployments.

3. The Tools Layer

A compact set of generic tools and business skills for reasoning, retrieval, and actions across Microsoft 365. More on this in the MCP server section below.

4. The Workspaces Layer

SharePoint Embedded working storage within the Microsoft 365 tenant boundary. Agents use these workspaces for intermediate data, outputs, and handoffs between agents. This is governed by existing information protection policies — Purview sensitivity labels, Conditional Access, and DLP rules all apply to agent working storage the same way they apply to human document libraries.

The Work IQ MCP Server: 12 Tools Instead of Hundreds

The Work IQ MCP server is where the architecture meets the developer experience — and it’s the component that matters most to automation architects deciding between building agents on Microsoft’s stack versus alternatives like Salesforce Agentforce or Google’s Gemini Enterprise Agent Platform.

The core design principle: fewer tools, more paths. Instead of exposing hundreds of granular Microsoft Graph operations as individual tools (a design that overwhelms LLMs during tool selection and burns tokens on schema loading), Work IQ consolidates everything into 12 generic tools organized in three categories:

Entity Tools (7)

Copilot Tools (3)

Schema Tools (2)

The path-based model means that adding new workloads to Work IQ adds paths, not tools. When Dynamics 365 Finance and Operations joins the preview in late October, agents don’t need new tools — they get new resource paths accessible through the same fetch, create_entity, and update_entity verbs they already know.

All requests flow through a single MCP endpoint: https://workiq.svc.cloud.microsoft/mcp.

Developer Setup

The CLI and VS Code integration make setup lightweight:

# Install the CLI
npm install -g @microsoft/workiq

# Or run directly with npx
npx -y @microsoft/workiq mcp

# Accept the EULA (required before first use)
workiq accept-eula

VS Code MCP configuration:

{
  "workiq": {
    "command": "npx",
    "args": ["-y", "@microsoft/workiq", "mcp"],
    "tools": ["*"]
  }
}

Authentication uses Microsoft Entra ID with delegated permissions. MCP clients discover the auth configuration automatically via /.well-known/oauth-protected-resource. One important constraint: application-only authentication is not supported — every request runs as a signed-in user, which is a deliberate governance choice rather than a technical limitation.

Business Skills: Codified Playbooks for Agents

If the MCP server gives agents access to data, business skills give agents access to process knowledge. A business skill pairs step-by-step instructions with the context an agent needs to execute a specific company procedure — renewal readiness, escalation protocols, onboarding workflows, compliance checks.

The key architectural decisions:

• Define once, reuse everywhere. A skill defined by the sales operations team is accessible to any agent connected through the Work IQ MCP server, including agents built in Copilot Studio, third-party agents connected via A2A, and coding agents using the Work IQ plugin.
• Skills travel with the semantic model. When an agent invokes a business skill, it executes within the context of the organization’s semantic model — so a “renewal readiness” skill automatically understands what an “account,” “opportunity,” and “service case” mean in that organization.
• Skills replace scattered prompts. Instead of every agent builder copy-pasting the same “check for open service cases before recommending a renewal” instruction into their prompts, the skill encodes it once and keeps it current in one place.

For RPA teams, this pattern will feel familiar — it’s the digital equivalent of a process definition document (PDD), but one that agents can actually execute rather than merely reference. Teams that have invested years in documenting SOPs for procure-to-pay or order-to-cash processes now have a path to expose those SOPs directly to agents.

Governed Actions: How Agents Write Back Without Going Rogue

The gap between an agent that can read business data and one that can act on it is where most enterprise agent projects stall. Work IQ addresses this with governed actions — a mechanism for agents to propose changes, route them through required approvals, and write updates back to source records.

The guardrails are layered:

• User-scoped execution: Every action runs with the delegating user’s permissions, not the agent’s service credentials. An agent cannot escalate a service case if the user who invoked it doesn’t have permission to escalate cases.
• Approval routing: Changes that require sign-off are routed through the organization’s existing approval workflows. The agent proposes; the human approves; the system of record updates.
• System of record authority: The underlying system (Dynamics 365, a Power App, a third-party LOB app) remains authoritative. Agents don’t maintain their own copy of the data — they read from and write back to the same records everyone else uses.

Examples of governed actions include escalating a case, reassigning opportunity ownership, updating a contract status, or creating a follow-up task — all without the user leaving their current workflow.

The Rego Policy Engine: Enterprise Governance at the Tool Level

This is the component that separates Work IQ from simpler “give the agent an API key and hope for the best” approaches. Every MCP tool invocation passes through a Rego-based policy engine — the same language used in the Cloud Native Computing Foundation’s Open Policy Agent (OPA) project.

The policy engine evaluates each request against four dimensions:

1. Resource path: Which data is the agent trying to access?
2. Request method: Is it a read or a write?
3. User identity: Who delegated this action to the agent?
4. Data content: What sensitivity labels or classifications apply to the target data?

Administrators manage policies through the Microsoft 365 admin center → Agents → Tools interface. The default posture is conservative:

This means agents are read-only by default. An administrator must explicitly enable write actions before agents can send emails, create calendar events, or update records — a design choice that’s cautious to the point of friction, but defensible given the always-on nature of Copilot Autopilot agents that never stop running.

One critical caveat that Microsoft’s partners have flagged: Rego policies can’t fix pre-existing overbroad permissions. If SharePoint permissions are already too loose, Work IQ inherits that looseness. The recommended pre-deployment checklist includes a permissions audit, Purview sensitivity label review, Entra Conditional Access review, and sharing-settings lockdown before enabling agents on production data.

Agent 365: The Governance Umbrella

Work IQ agents operate under Microsoft Agent 365, which reached GA on May 1, 2026. Agent 365 provides the organizational controls that IT teams need before they’ll approve agents in production:

• Agent registry — a central inventory of every agent running in the organization
• Visual topology map — see which agents connect to which data sources and tools
• Unmanaged agent discovery — detect local agents running outside the governed platform
• Security integration — Defender, Entra, Intune, and Purview protections extend to agents
• Agent identity — each Copilot Autopilot agent gets its own Entra identity, so actions are traceable to the specific agent that performed them

For teams building on the Microsoft Agent Framework 1.0 and Foundry Agent Service, Agent 365 is the governance wrapper that makes those agents enterprise-acceptable.

Copilot Studio Integration: Connecting Custom Agents to Work IQ

For low-code builders and RPA teams already invested in the Power Platform, the Copilot Studio integration is the most practical entry point. The integration works through Work IQ MCP servers that can be enabled directly within a Copilot Studio agent configuration.

The available MCP servers within Copilot Studio include:

A practical demo from ForwardForever showed a Major Incident Assist Agent built entirely with Work IQ MCP servers and no custom topics or knowledge sources. The agent could summarize an email thread to extract an incident number and SLA, find a 30-minute slot for an on-call team and create a Teams meeting with the incident link, and search Microsoft 365 for documents on the relevant issue type — all in a single conversational turn. Adding a ServiceNow MCP server to the same agent let it pull incident status, priority, and assignee from the ITSM system alongside the M365 context.

Licensing and Cost Model

Work IQ uses usage-based billing through Copilot Credits, which represents a significant shift from seat-based licensing:

• Copilot-licensed users get Work IQ in all Copilot experiences and agents at no additional per-call cost
• Custom and third-party agents are billed consumptively — you pay for what agents use
• Users without a Copilot license can still use Work IQ through agents, billed consumptively
• Tools APIs have fixed costs; Chat and Context APIs are variable

The consumption model means adoption isn’t gated by buying seats, but it also means high-frequency agents need careful unit-economics modeling. A customer service agent that processes thousands of tickets per day will generate a meaningful bill through cumulative tool invocations — the token savings from Work IQ’s pre-grounding (Microsoft claims approximately 80% reduction in token usage versus conventional retrieval) only offset costs when prompts would otherwise be very large.

Cost management controls are available in the Microsoft 365 admin center, and a usage-based billing plan in Copilot Studio with an Azure subscription and resource group is required for setup.

How Work IQ Compares to Alternative Agent Platforms

The enterprise agent platform market is consolidating around a few major stacks. Here’s how Work IQ’s approach compares:

Microsoft’s structural advantage is that it owns both the productivity layer (Outlook, Teams, SharePoint) and the business applications layer (Dynamics 365, Power Platform). An agent that can reason across a customer’s email history, their CRM record, their service tickets, and their ERP data — all under one permission model — has a context advantage that competitors need partnerships and integrations to match.

The Forrester Wave for Adaptive Process Orchestration (Q3 2026) reflects this shift: the analysts now evaluate vendors on how well they connect agent reasoning to live business data, not just how well they execute predefined workflows.

What This Means for RPA and Automation Teams

If you’re running an RPA Center of Excellence on the Microsoft stack, Work IQ changes the calculation for what should be a bot versus what should be an agent:

When to keep your existing RPA bots

Deterministic processes that follow fixed rules — invoice processing with known templates, data entry between systems with rigid field mappings, scheduled report generation — are still better served by traditional RPA. Work IQ adds nothing to a bot that doesn’t need to understand business context.

When to build Work IQ agents

Processes that require judgment, context across multiple systems, or interaction with unstructured data are where Work IQ agents outperform bots. Sales renewal assessments that need CRM + service + email context. Employee onboarding coordination across HR, IT, and facilities. Procurement decisions that need to weigh contract terms against supplier communication history. These are the use cases where a bot would need hundreds of rules to approximate what a Work IQ-grounded agent handles natively.

The hybrid architecture

The pragmatic path for most teams is hybrid: Work IQ agents handle the judgment-heavy orchestration layer, and existing RPA bots handle the deterministic execution underneath. An agent decides what needs to happen based on context; a bot executes the specific system transactions. The Power Platform’s existing connectors and Power Automate desktop flows bridge the two worlds.

Production Readiness Checklist

Before deploying Work IQ agents to production, walk through this pre-flight sequence:

Timeline: What’s Live Now and What’s Coming

Frequently Asked Questions

Do I need a Microsoft 365 Copilot license to use Work IQ?

Not necessarily. Work IQ API access is consumption-based and independent of Copilot licensing. Users without a Copilot license can access Work IQ through agents, billed consumptively via Copilot Credits. However, Copilot-licensed users get Work IQ included in all Copilot experiences at no additional per-call cost, and using Work IQ MCP servers within Copilot Studio requires a Microsoft 365 Copilot license.

Can I connect non-Microsoft agents (LangChain, CrewAI, AutoGen) to Work IQ?

Yes. The Work IQ MCP server follows the Model Context Protocol standard, and the A2A protocol enables agent-to-agent delegation. Any MCP-compatible agent framework can connect to the Work IQ endpoint at https://workiq.svc.cloud.microsoft/mcp using Entra ID delegated authentication. Microsoft’s Foundry Agent Service also supports hosted agents that can call Claude, GPT, Gemini, or other models.

How does Work IQ handle multi-tenant organizations?

For parent/child tenant configurations, register the app as AzureADMultipleOrgs. The token’s iss (issuer) must match the signed-in user’s tenant, or requests fail with a 400 AuthenticationError. Each tenant maintains its own semantic model, business skills, and Rego policies.

What happens when an agent action is blocked by policy?

Denied requests return a policy error, typically 403 Forbidden. Agents should handle these responses gracefully and inform users that governance — not a bug — blocked the action. An operation that works in a dev tenant may fail in a production tenant with different policies configured.

Can Work IQ replace my existing custom RAG pipelines for M365 data?

For Microsoft 365 data, Work IQ is designed to supersede custom RAG pipelines. Microsoft’s stated advantages include permission-aware retrieval without permission drift, real-time data freshness without manual reindexing, and approximately 80% reduction in token usage compared to conventional retrieval approaches. However, for data outside the Microsoft ecosystem, you’ll still need custom retrieval — Work IQ doesn’t index Salesforce records or SAP transactions.

Key Takeaways

• Work IQ is Microsoft’s answer to the agent context gap — the reason most enterprise agent pilots stall is not model capability but business data grounding, and Work IQ provides a shared semantic model across M365, Dynamics 365, and Power Platform.
• The MCP server design (12 tools, path-based routing) is architecturally significant — it reduces tool-selection complexity for LLMs and scales without adding tools as new workloads come online.
• Rego-based governance isn’t optional — the OPA policy engine evaluates every tool invocation, and the default posture is read-only. This is conservative by design and reflects lessons from early agent deployments where agents exceeded intended boundaries.
• Business skills are the enterprise equivalent of process definition documents — define once, reuse across all connected agents, and keep institutional knowledge in one place rather than scattered across prompts.
• The October 2026 preview extending to Dynamics 365 and Power Platform is the real inflection point — Work IQ grounding M365 productivity data was useful; grounding CRM and ERP data makes it transformational for business process automation.
• RPA teams should plan hybrid architectures — Work IQ agents for judgment-heavy orchestration, existing bots for deterministic execution, connected through Power Automate flows.

References

1. Microsoft Dev Blog, “Work IQ: Production-Ready Intelligence for Every Agent,” June 2, 2026 — devblogs.microsoft.com
2. Microsoft Learn, “Work IQ MCP Server Overview,” 2026 — learn.microsoft.com
3. ERP Today, “Microsoft Opens Work IQ Preview for Dynamics 365 and Power Platform Data,” October 2026 — erp.today
4. Cloud Wars, “Microsoft’s Work IQ Gets Down to Business,” September 28, 2026 — cloudwars.com
5. EPC Group, “Microsoft Build 2026: Work IQ, Microsoft IQ, Agent 365 Context Layer,” 2026 — epcgroup.net
6. ForwardForever, “Extending Copilot Studio Agents with Work IQ Mail, Calendar, and Copilot Tools in Action,” 2026 — forwardforever.com
7. Candede, “Integrate Work IQ MCP,” 2026 — candede.com
8. AI Automation Global, “Microsoft IQ Platform: Work IQ APIs, Enterprise Agent Context 2026” — aiautomationglobal.com
9. Microsoft, “Announcing the New Work IQ APIs,” June 2, 2026 — microsoft.com
10. Open Policy Agent documentation — openpolicyagent.org