Home Power PlatformsCopilot and AI Work IQ Hands-On: An Agent That Reads Your Work

Work IQ Hands-On: An Agent That Reads Your Work

by Mo Faheem
Work IQ Hands-On: An Agent That Reads Your Work

⚙️ Lab note (added September 2026): every agent in this series was built and run in the new Copilot Studio experience. What Microsoft now calls the GitHub Copilot harness (GA August 2026). The classic “standard harness” is a different build experience with different behaviour. My standard-harness rebuild and full harness comparison are scheduled on this blog for late October 2026.

For this test I set a deliberately unfair trap. I created a brand-new SharePoint site, uploaded three policy documents to it, waited about twenty minutes, and then asked my agent a question only those documents could answer: “What is the restocking fee for opened machines, and how long is the Café A-100 warranty?” Unfair, because a site that new is invisible to search indexing, which is exactly the corner your users will back an agent into on day one. What Work IQ (Preview) did next earned my trust more than any polished demo could have.

(What Work IQ actually is, a product delivered through MCP servers, is covered in the plug-and-appliance post. The Microsoft 365 Copilot trial seat it requires is covered in the licensing post.)

Step 1. Connect Work IQ (Preview)

In the agent, choose Tools › + Add tool › Model Context Protocol and select Work IQ (Preview), “supports operations on mail, calendar, files, chats, and more. Availability and capabilities are subject to change.” (They mean it, this is a preview.)

The Select a connection dialog for Work IQ (Preview) with Create new connection
Select a connection › Create new connection. It signs in as you. The agent inherits your M365 view of the world, which is precisely why the M365 Copilot seat is required.

⚠️ Important: the connection runs as its owner. An agent with Work IQ sees what that user can see, mail, files, chats. In a lab that is you. In production, decide very deliberately whose eyes the agent borrows.

Step 2. Ask, and Watch the Consent Cards

Every Work IQ action in the test pane raised its own Permission Required card, ask, fetch, search_paths, fetch_blob, each with Allow/Deny buttons:

A Permission Required card asking to allow Work IQ (Preview) to perform the ask action
The toll booth for every action. Nothing touches your work data without a click. Tedious in a demo, priceless in an audit.

Step 3. The Honest Miss (This Is the Good Part)

The agent searched Microsoft 365 Copilot Search with several phrasings, tried shorter queries, checked web knowledge, and then did the thing I most wanted to see. It did not guess:

The agent lists the searches it ran, reports the new SharePoint site is not in the search index, and asks for the site URL instead of guessing
The full confession. Searches run, results found (unrelated OneDrive files, correctly cited), and the diagnosis: the new site “did not resolve in the search index.” Then one clarifying question instead of one invented number.

It reported that my hours-old site was not in the search index yet, showed exactly which searches it had run, cited the unrelated files it did find, and asked for the direct site URL. A warranty percentage pulled from thin air would have looked identical to a real answer. The refusal is the feature. Plan for index lag: fresh SharePoint sites take hours to become searchable, so either wait, or hand agents the direct URL.

Step 4. Given the URL, It Goes Through the Side Door

I replied with the site address and the file name. Work IQ switched strategies: it resolved the site through Graph paths, enumerated the Documents library, downloaded the actual file with fetch_blob, loaded a docx-analysis skill, and read the policy directly:

The agent answers with the 15% restocking fee and 24-month warranty, citing the exact document in the Copilot Agent Lab site
The payoff. 15% restocking fee, 24-month Café A-100 warranty, service levels, sourced to the exact document, section by section, with a note explaining how it got there.

Both numbers were correct. I wrote the document, so I got to grade the exam. The answer even named the two sibling files in the library and offered details from those. Indexing is a convenience, not a dependency: with a URL in hand, Work IQ reads the file itself.

What I Learned

The retrieval was impressive, but the miss was the moment that mattered. An agent grounded in your work data will constantly face questions the index cannot answer yet, and the difference between a production-ready assistant and a liability is what it does in that gap. Work IQ, at least in this test, showed its work, admitted the gap, and asked one good question. I will take an honest “I could not find it” over a confident invention every day of the week.

Next in this series: publishing the agent into Dynamics 365, where all of these tools finally meet the users.

Related Articles

Leave a Comment