Microsoft 365 Work IQ
Ask Work IQ about mail, meetings, files and chats, and act where your tenant allows.
A Work IQ connection gives a playbook's functions Microsoft's Work IQ MCP server. You sign in with your work account and allow Work IQ, and the connection asks Work IQ as you: it reads and searches your Outlook mail and calendar events and the rest of your Microsoft 365 data, and sends, moves and changes them where your tenant's Work IQ policy allows, which by default it does not.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Microsoft 365 Work IQ
- Ask about your mail, your meetings, your files and your chats in one place, in a question rather than a query, and read what Work IQ answers.
- Search across them.
- Send, move and change them, only where your tenant's Work IQ policy allows an agent to act, which Microsoft's default does not.
For exact operations on one service, mail folders, a calendar range or a workbook's cells, the Outlook, OneDrive, SharePoint and Excel and Microsoft Teams connections give a function the Graph operations themselves.
Microsoft 365 Work IQ's MCP server lists its own tools when a function runs, and once you connect, your agent lists them with list_connection_tools.
An example workflow
Preparation before a customer meeting. A schedule trigger runs the workflow at 07:00. A lookup function asks Work IQ which external meetings you have today. For each, a reasoning function asks Work IQ, through the connection's tools, what was said in the last mail threads and chats with those people and which files were shared, then writes a one-page brief in the shape your team uses: the last decisions, the open questions, the people in the room. An interaction function posts each brief to you in a Teams chat through a Microsoft Teams connection, an hour before the meeting, which a step of the workflow waits until. Nothing is sent to the customer; the connection reads, and your tenant's policy keeps it so. The run's history in Studio keeps each brief and what it was built from.
How to connect Microsoft 365 Work IQ
- Sign in with your work account and allow Work IQ. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Microsoft 365 Work IQ to Auto, or open Settings, Agents, Connections in Auto Studio and choose Microsoft 365 Work IQ.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
What it needs
- A work or school account in a Microsoft 365 tenant where Work IQ is available to you; Microsoft's documentation says which licenses include it.
- A tenant whose Work IQ policy allows what the playbook does: reading, by default; acting, only where an administrator has allowed it.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, an application registered in Microsoft Entra for the runtime, since Microsoft registers no client itself, as Let people add connections sets out.
Permissions Auto asks for
- Ask Work IQ about Microsoft 365 mail, meetings, files and chats, and act on them where the tenant allows.
- Keep access to Work IQ when nobody is signed in.
Good to know
Work IQ answers in prose and in references to the items it found, which is what a reasoning function reads well and what a computation function cannot sort; pair it with the Outlook or OneDrive connections where a workflow needs exact rows. What Work IQ answers is kept in the run's history, where people with access to the playbook can read it.