{"id":2592,"date":"2026-07-10T15:26:32","date_gmt":"2026-07-10T05:26:32","guid":{"rendered":"https:\/\/www.dynamicwebtraining.com.au\/blog\/?p=2592"},"modified":"2026-07-10T16:00:14","modified_gmt":"2026-07-10T06:00:14","slug":"work-iq-intelligence-upgrade-control-plane","status":"publish","type":"post","link":"https:\/\/www.dynamicwebtraining.com.au\/blog\/work-iq-intelligence-upgrade-control-plane","title":{"rendered":"Work IQ Isn\u2019t an Intelligence Upgrade. It\u2019s a Control Plane."},"content":{"rendered":"\n

When Work IQ was introduced, most people focused on one idea: Copilot was becoming smarter because it could understand more about how an organisation works. But if you look past the keynote and read the architecture details, the bigger story is not just intelligence. It is control. Microsoft designed Work IQ to manage who can use that intelligence, what they are allowed to do with it, and how every action is recorded and checked. In simple terms, Work IQ makes governance something organisations need to actively manage, not something that stays hidden in the background.<\/p>\n\n\n\n\n\n\n\n

What is Work IQ? (The Three-layer Version)<\/h2>\n\n\n\n

Architecturally, Work IQ is three layers stacked on top of Microsoft Graph.<\/a><\/p>\n\n\n\n

Data:<\/code><\/strong> It unifies signals from files, email, meetings, chats and line-of-business systems into one model of how work happens in your tenant. Not the documents themselves. It works on the patterns indicating who works with whom, how approvals flow, what\u2019s connected to what.<\/p>\n\n\n\n

Memory:<\/code><\/strong> It builds persistent understanding of how people and teams operate, so an agent stays aligned to priorities and consistent across tasks, apps and sessions. This is what turns a stateless chatbot into something that behaves like it has institutional knowledge.<\/p>\n\n\n\n

Inference:<\/code><\/strong> It reasons over the first two layers to produce agent-ready context on demand, so an agent doesn\u2019t have to stitch together raw signals or run its own retrieval pipeline.<\/p>\n\n\n\n

The reason this matters for governance: It must attach to all three layers, not just the data. It isn\u2019t enough to control which files an agent can read. It must control what they can infer and what they can remember. Most security models were built for the data layer only. Work IQ forces the conversation up a level.<\/p>\n\n\n\n

\"Diagram
Figure 1.<\/strong> Work IQ is three layers on top of Microsoft Graph and governance is a column that touches every one of them, not a box at the bottom.<\/figcaption><\/figure>\n\n\n\n

The One Distinction That Changes Everything: Discoverable Vs. Extractable<\/h2>\n\n\n\n

Work IQ helps an agent understand how information is connected without showing protected content it should not access. For example, an agent may know that a contract exists, that it is linked to a deal, that certain people worked on it, and that it connects to a budget item. But if the user does not have permission to view the contract, the agent cannot pull or reveal the confidential text inside it.
This is the difference between discoverable<\/strong> and extractable<\/strong>. Discoverable means the agent can understand that information exists and how it connects to other things. Extractable means the agent can actually open, retrieve, and use the content.<\/p>\n\n\n\n

Work IQ does not create new access. It inherits the exact permissions, sensitivity labels and data-protection policies that already govern your Microsoft 365 data. An agent can only extract what the user it\u2019s acting for could already extract. Work IQ changes how existing access functions; it doesn\u2019t widen it.<\/p>\n\n\n\n

Work IQ surfaces your governance gaps instead of hiding them. If a document has a misapplied sensitivity label or an over-broad permission, Work IQ will faithfully expose it. The fix isn\u2019t to restrict the intelligence. It\u2019s to fix the data at the source.<\/strong><\/p>\n\n\n\n

\"Conceptual
Figure 2.<\/strong> An agent can reason over what exists and how it connects but can only retrieve content the calling user already has rights to. Work IQ inherits your permissions. It doesn\u2019t expand them.<\/figcaption><\/figure>\n\n\n\n

Implicit Vs. Explicit: The Moment Governance Becomes Your Job<\/h2>\n\n\n\n

Microsoft draws a hard line here, and it\u2019s worth making the centre of your thinking.<\/p>\n\n\n\n

Inside Copilot<\/a>, when you ask it to draft an email or summarise a meeting; Work IQ runs implicitly. You never see it. Microsoft owns the security underneath, access is honoured automatically, and you simply get answers that understand your business. There\u2019s nothing for you to govern because the boundary is the Copilot product itself.<\/p>\n\n\n\n

The moment you build a custom agent that uses Work IQ through an MCP server, which is simply a standard way for an AI agent to connect to another system, that intelligence becomes explicit. You\u2019ve made a clear decision: you want your agent to understand your organisation\u2019s work patterns and act on them. From that point on, you own a new responsibility because the agent can do more than answer questions. It can update systems, change files, and approve requests.<\/p>\n\n\n\n

That transition, implicit to explicit, is the exact point where governance stops being Microsoft\u2019s problem and becomes yours.<\/p>\n\n\n\n

\"Comparison
Figure 3.<\/strong> Same intelligence, two modes. Implicit inside Copilot is Microsoft\u2019s to govern; the moment a custom agent consumes it explicitly; the governance surface is yours.<\/figcaption><\/figure>\n\n\n\n

MCP: Ten Tools Instead of a Thousand Integrations<\/h2>\n\n\n\n

MCP server acts as a universal adapter. Instead of every agent needing its own custom-built integration for each application, MCP server gives them one common way to discover and connect with a system. It is fast becoming the default way agents talk to tools, and Microsoft has adopted it as the connection layer for Work IQ.<\/p>\n\n\n\n

The Work IQ MCP collapses hundreds of underlying Microsoft 365 operations into just ten generic tools<\/strong>. They’re ten verbs that act on resource paths, in three groups:<\/p>\n\n\n\n