Forum Discussion

LeonelB's avatar
LeonelB
Copper Contributor
Nov 17, 2026

Work IQ or individual M365 tools for a company-wide agent: cost vs. future-proofing?

I'm Head of Project Management at Contica, a Swedish integration consultancy. I've built a task organizer agent in Copilot Studio that reads my Outlook, Teams chats and calendar, finds real commitments (things I promised, questions waiting for my answer) and organizes them in Microsoft To Do. It works well for me, and colleagues are asking for it. Before a broader rollout I'm stuck on an architecture choice.

 

One run consumes roughly 300-400 Copilot Credits, about 3.5 USD at pay-as-you-go rates. Run daily, that’s around 70 USD per user per month.

 

Here's how I understand the billing from the docs:

- Work IQ runs on the Microsoft Copilot harness and is billed in Copilot Credits, including for users with an M365 Copilot license when it's used in a custom agent.

- The workload-specific tools (Mail, Teams, Calendar etc.) run on the standard harness. For a standalone Copilot Studio agent in Teams, usage by M365 Copilot licensed users isn't billed.

- But Microsoft describes those tools as legacy, kept for testing and backward compatibility, and recommends not choosing them over Work IQ.

 

So the trade-off as I see it:

1. Stay on Work IQ: simpler and future-proof, but every run costs credits for every user.

2. Rebuild with the individual tools: potentially much cheaper for licensed users and more control over exactly what's read, but built on something Microsoft calls legacy.

 

My questions:

1. Has anyone made this choice for a broad rollout? Which way did you go, and why?

2. What has worked for bringing Work IQ cost down - fewer workloads, narrower time windows, reading metadata first?

3. Have I got the billing model right? The licensing pages aren't the easiest read.

 

Thanks!

No RepliesBe the first to reply