Microsoft Just Made "Knows Your Whole Company" an API With a Meter on It. Work IQ Went GA Today — Here's What It Does to Solo AI Consultants.
Today, June 16, Microsoft flipped Work IQ to general availability. If you've been making a living wiring AI agents into companies that run on Microsoft 365 (connecting an agent to their email, their SharePoint, their Teams chats, their calendars so it answers questions like someone who actually works there), the most valuable part of that job just shipped as an API endpoint with a billing meter attached.
That's not a doom headline. It's a repositioning notice. The "context plumbing" half of AI consulting on Microsoft shops is being commoditized in real time, and the work that survives is the half Work IQ structurally can't reach. The trick is knowing which is which before your next proposal.
What Work IQ actually is
Strip the marketing and Work IQ is a semantic understanding layer that sits on top of a company's Microsoft 365 tenant. It continuously processes the stuff that makes a business legible (email, calendar, meetings, chats, files, the org chart, who works with whom, and connected line-of-business systems) and exposes that understanding to agents. Microsoft's pitch is that this is the context an agent needs to be useful instead of generically smart.
You reach it three ways: an A2A (agent-to-agent) interface, a redesigned remote MCP server, and a plain REST API. The MCP server is the tell. Microsoft is meeting agent builders where they already are: if your stack speaks MCP, Work IQ wants to be one of your tools without a rewrite.
It also keeps state. Work IQ "digital workspaces" hold data, files, memory, and intermediate outputs as an agent reasons through a task, and all of it operates inside the customer's M365 tenant boundary. That boundary matters, and I'll come back to it, because it's both the reason enterprises will trust this and the reason it locks them in.
The meter is the whole story
Here's the part that should change how you scope work. Work IQ has no separate subscription, no per-user license, no standalone SKU. It bills through Copilot Credits, Microsoft's consumption currency that also covers Copilot Studio and its other AI services. You pay for what agents consume.
Read that again with a consultant's eyes. The cost isn't a flat line item the client approves once. It scales with how much of the organization's context your agents chew through, and "the organization's context" is the entire firehose of email, meetings, and files. An agent that politely re-reads the relevant corner of the company on every run is an agent that bills on every run. Consumption pricing on a corpus this size is the kind of thing that looks cheap in the demo and surprises the CFO in month two.
If you're the consultant who set it up, that surprise lands on you. Which means part of your new job is cost architecture: scoping which context an agent actually needs, caching what doesn't change, and not pointing a metered semantic engine at the whole tenant because it was easier than thinking. That's real work. It's just different work than the integration you used to sell.
What just got commoditized
Be honest about what evaporated. If your engagement was "I'll connect your agent to your Microsoft data so it understands your business," Microsoft now ships that as a supported, first-party product. You were charging (pick your number) $8K to $20K to build and maintain the connectors, handle auth, normalize the data, and keep it from breaking when someone changed a SharePoint permission. A meaningful slice of that is now a checkbox a competent IT admin can enable.
I don't say that to spook you. I say it because the worst position is selling a thing the platform now gives away while telling yourself it's still bespoke. It isn't. The bespoke integration into a standard Microsoft estate is the part with a target on it, and pretending otherwise just means you find out when a client forwards you Microsoft's announcement and asks why they're paying you for it.
What survives, and it's the better work anyway
Work IQ understands what lives inside the M365 tenant. It does not understand your client's business. Those are different things, and the gap between them is the whole job now.
The durable work is everything the semantic layer can't see or decide. The judgment about which workflows are worth automating and which are theater. The integration with the systems that aren't Microsoft: the industry-specific app, the legacy database, the partner API that holds the data the business actually runs on. The evaluation harness that tells the client whether the agent is right often enough to trust, because Microsoft will sell them the capability but not the confidence that it works for their edge cases. And the cost governance I mentioned, which on a consumption meter is not a nice-to-have.
That's a better business than connector plumbing. It's stickier, it's harder to commoditize, and it's the part clients can't self-serve, because it requires understanding their operation rather than their software. The plumbing was always the least defensible thing you sold. Microsoft just made the case for moving up the stack on your behalf.
What I'd actually do
If you consult into Microsoft shops, spend an afternoon this week actually using Work IQ (the REST API and the MCP server) so you can speak to it from experience instead of from a blog post, because your clients will absolutely read the blog post. Then go reprice. Stop quoting integration as the deliverable. Quote outcomes, governance, and the non-Microsoft half of the stack, and treat the Work IQ connection as a commodity input you configure, not a custom artifact you build.
And rewrite your pitch around the meter. "I'll connect your agent to your data" is a 2025 sentence. "I'll make sure your agents get the context they need without your Copilot Credit bill tripling" is a 2026 sentence, and it's one only someone who's been burned by consumption pricing can say convincingly. That's you, if you do the homework now instead of after the first overage.
The honest counter-take: there's a real chance Work IQ underdelivers at first. GA on day one is not the same as good, and Microsoft's track record on shipping intelligence layers that work as smoothly as the keynote claims is, generously, mixed. If it's flaky, the consultants who can make agents reliable on top of a half-baked platform layer get more valuable, not less, because "Microsoft says this works and it doesn't quite" is a classic, well-paid consulting gig. Either way the conclusion is the same: the connector work is dying and the judgment work is where you want to be standing. The only variable is how fast you move, and the meter started running today.
Author
Lukas
@lukcombinator