Building a Work IQ connector for Power Platform and Copilot Studio

July 07, 2026

“What meetings do I have today?” “What did Dana share about the Q3 budget?” “Who’s working on the Contoso proposal?”

These are the kinds of questions your agents and flows should be able to answer without you wiring up separate connectors for Mail, Calendar, Teams, SharePoint, and People. The Work IQ A2A API reasons across all M365 data automatically — you ask a question in plain English and get a structured answer back. This connector puts that capability into Power Platform.

What it does

The connector exposes two paths:

Both hit the same Work IQ backend at workiq.svc.cloud.microsoft. The MCP endpoint is a passthrough proxy — Copilot Studio detects it and handles tool invocation automatically. The A2A endpoint wraps the JSON-RPC SendMessage method with a typed schema so Power Automate can use it with full IntelliSense.

How it differs from Agent 365 MCP

Work IQ is simpler. You don’t choose which server to call — Work IQ routes to the right data automatically. Agent 365 MCP gives you 11 individual servers with full tool schemas when you need that precision.

Multi-turn conversations

Work IQ supports conversational context via contextId. The first response includes a context ID; pass it back on subsequent requests to ask follow-ups:

1. AskWorkIQ → "What meetings do I have today?"
   → response includes contextId: "ctx-abc123"

2. AskWorkIQ → "Tell me more about the 2 PM call"
   → contextId: "ctx-abc123"
   → Work IQ uses conversation history to resolve "the 2 PM call"

This means a Power Automate flow can have a multi-step conversation with Work IQ — asking progressively more specific questions about the same topic.

Supported data

Work IQ reasons over:

• Email messages
• Meetings and calendar data
• Documents in OneDrive and SharePoint
• Teams messages
• People and organizational context
• Planner plans
• Enterprise search results

All responses are permission-trimmed and policy-enforced. Work IQ only returns data the signed-in user has access to, and it respects sensitivity labels and compliance policies.

The A2A request format

The typed operation wraps the A2A protocol’s JSON-RPC format:

{
  "jsonrpc": "2.0",
  "id": "unique-request-guid",
  "method": "SendMessage",
  "params": {
    "message": {
      "role": "ROLE_USER",
      "messageId": "unique-message-guid",
      "contextId": "optional-context-from-previous-response",
      "parts": [
        { "text": "What did Dana share about the Q3 budget?" }
      ],
      "metadata": {
        "Location": {
          "timeZoneOffset": -300,
          "timeZone": "America/Chicago"
        }
      }
    }
  }
}

Include timeZone and timeZoneOffset for time-sensitive queries — Work IQ uses them to interpret “today,” “this week,” and similar relative references correctly.

Authentication

The connector uses OAuth 2.0 with the https://workiq.svc.cloud.microsoft/.default scope. Delegated only — Work IQ runs in the context of the signed-in user. App-only authentication is not supported.

For multitenant organizations (parent/child tenants), register the app as AzureADMultipleOrgs. The token issuer must match the user’s home tenant.

Deployment

1. Import via Maker portal (Custom connectors > Import OpenAPI) or deploy with PAC CLI:

pac connector create `
    -df apiDefinition.swagger.json `
    -env <environment-id>

1. Configure OAuth in the Security tab with your app registration client ID and the https://workiq.svc.cloud.microsoft/.default scope
2. Create a connection and test with a simple question

Billing

Work IQ API usage is billed via Copilot Credits. Each query consumes credits based on the complexity of reasoning required.

Use cases

Meeting prep agent — Before a customer meeting, ask Work IQ “What have we discussed with Zava in the last 30 days?” and get a summary spanning email, Teams, and shared documents — all from one call.

Automated context injection — A Power Automate flow triggers before weekly standups, asks Work IQ “What did my team accomplish this week?”, and posts the summary to a Teams channel.

Help desk triage — When a support ticket arrives, ask Work IQ “What do we know about this topic?” to surface relevant internal documentation and prior conversations before routing to an agent.

The full source is available in the SharingIsCaring repository.