How C1 connects to Microsoft Work IQ
C1 connects to Microsoft’s hosted Work IQ MCP server athttps://workiq.svc.cloud.microsoft/mcp. When an AI client calls an approved tool through C1, C1 forwards the call with a Microsoft Entra access token and returns the result. You don’t need to install the local Work IQ CLI or create a Microsoft Foundry project for this connection.
Work IQ enforces the signed-in user’s Microsoft 365 permissions and tenant policies. Application-only authentication through the OAuth client credentials grant isn’t supported. See Microsoft’s Work IQ authentication guidance.
Before you begin
- Enable AI access management for your C1 tenant. See Enable AI access management.
- Have a Microsoft Entra work tenant and permission to register an application in it.
- Arrange for a Global Administrator to complete the one-time Work IQ tenant setup and grant admin consent.
- Configure Work IQ billing and user access as described below. Microsoft’s Work IQ connection quickstart also lists a Microsoft 365 Copilot license for each calling user; confirm your users meet Microsoft’s current licensing requirements.
If you don’t see Microsoft Work IQ in your MCP server catalog, contact the C1 support team to enable it for your tenant.
Enable Work IQ in Microsoft 365
Before configuring C1, set up usage-based billing for Copilot Credits and include the intended users in the billing policy. Then have a Global Administrator provision the Work IQ service principal, if it doesn’t already exist, using either method:1
Azure CLI: While signed in to the intended tenant, run:This is Microsoft’s Work IQ resource application ID, not the client ID you’ll create for C1.
2
Microsoft Graph: Follow the Graph Explorer steps in Microsoft’s Enable your tenant for Work IQ.
Set up per-user OAuth (recommended)
Use per-user OAuth for most deployments. Each user signs in with their own Microsoft account, so every tool call runs under that user’s Microsoft 365 identity and permissions, and C1 refreshes tokens automatically. Register one confidential web application in Microsoft Entra, then give C1 its client ID and secret. Each user authorizes separately.Register a Microsoft Entra application
Follow Microsoft’s app registration guide to create the app in your intended tenant.1
Open the Microsoft Entra admin center, then go to Entra ID > App registrations > New registration.
2
Enter a recognizable name, such as
C1 Work IQ.3
Choose the supported account type. Use a multitenant organizational app if you will keep C1’s prefilled
organizations endpoints. For an app restricted to one tenant, choose the single-tenant option and use that tenant’s ID in all the OAuth URLs below. See Microsoft’s authority configuration.4
Select Register.
5
Copy the Application (client) ID and Directory (tenant) ID from the app overview.
6
Under Authentication > Add a platform > Web, add the C1 redirect URI that matches your C1 tenant’s domain:
- Default instance:
https://accounts.conductor.one/auth/callback - EU data residency instance:
https://accounts.c1eu.ai/auth/callback
7
Under Certificates & secrets > Client secrets > New client secret, create a secret with an expiration that meets your organization’s policy. Copy its Value, not its secret ID. The value is shown only once. See Add and manage application credentials.
Grant the Work IQ delegated permission
Add the permission to the app you just registered. Microsoft’s Work IQ permissions reference documents the required delegated scope and admin consent.1
Open API permissions > Add a permission > APIs my organization uses, and search for Work IQ. If it doesn’t appear, provision the Work IQ service principal in this tenant using the steps in Enable Work IQ in Microsoft 365.
2
Select Delegated permissions, add WorkIQAgent.Ask, and select Add permissions.
3
Have a Global Administrator select Grant admin consent for the tenant and confirm that consent is granted.
Which Work IQ permissions to add
The Work IQ API lists several delegated permissions. C1 requests onlyWorkIQAgent.Ask, so add only that one.
WorkIQAgent.Ask is the only permission that grants access to Microsoft 365 data, and it covers both reads and writes. The WorkIQSettings permissions manage Work IQ configuration, not user data, so adding them doesn’t give users more tool access. Leaving them consented only widens what the app could change in your tenant.
Allow Work IQ operations in Microsoft, then govern them in C1
Microsoft blocks create, update, delete, and action requests, such as sending mail, by default. To make the full Work IQ tool set available through C1, have a Microsoft 365 administrator allow those operations in Agents > Tools > Work IQ MCP > Policy in the Microsoft 365 admin center. The setting applies to the whole tenant and can take up to 24 hours. See Policy governance for Work IQ MCP. With Microsoft open, C1 is where you decide who can use which tools. For example, give most users a read-only toolset (retrieve, ask, fetch, get_schema, and similar) and bind the write tools (create_entity, update_entity, delete_entity, do_action) only to the users who need them. You can change these assignments in C1 at any time without changing Microsoft tenant settings. See Discover and govern tools.
Work IQ still enforces each signed-in user’s own Microsoft 365 permissions. C1 can’t grant access beyond them.
Register the server in C1
With Microsoft setup complete, register the server and configure its OAuth connection.1
Follow Register an MCP server and select Microsoft Work IQ from the catalog. The Microsoft endpoint is
https://workiq.svc.cloud.microsoft/mcp.2
When you configure authentication, choose OAuth2 — per-user passthrough. Enter the Application (client) ID and client secret Value you copied from your Entra app registration.
3
Confirm the following OAuth settings. These organizational URLs match the authority advertised by Microsoft’s hosted server metadata.
Optional. For a single-tenant app, replace
organizations with your Directory (tenant) ID in the issuer, authorization, token, and refresh URLs. Keep all URLs on the same authority. In a parent/child multitenant organization, Microsoft requires tokens issued by the user’s home tenant; see the multitenant authentication guidance.The catalog configuration uses PKCE S256 and sends client credentials in the token request body. Keep those settings if you edit the OAuth configuration. The offline_access scope enables refresh tokens; see Microsoft’s offline access scope.4
Save your changes. Each user sees a Connect prompt when they first call a Work IQ tool and completes Microsoft sign-in before using it.
Optional: Use a delegated access token
Use a manually supplied token when you already have a delegated Work IQ access token and can manage its expiry. Obtain it through your registered app’s user authorization flow forapi://workiq.svc.cloud.microsoft/WorkIQAgent.Ask. Use an access token issued for Work IQ, rather than an ID token, Microsoft Graph token, or application-only token.
Follow Register an MCP server, select Microsoft Work IQ, and choose Bearer token when configuring authentication. Paste the access token without the Bearer prefix. C1 adds the authorization header.
This mode doesn’t refresh the supplied token. Replace it before the token response’s expires_in lifetime elapses. Use per-user OAuth for automatic refresh.
How Microsoft Work IQ credentials are shared
- Per-user OAuth: The app’s client ID and secret identify the C1 connection, but every user has their own delegated Microsoft tokens. Work IQ receives calls as that signed-in user.
- Bearer token: Everyone using the server shares the supplied token and its Microsoft identity and permissions. C1 records the calling C1 user in the AI tool usage audit log, while Microsoft receives the token owner’s identity.
Discover and govern tools
After registration, C1 discovers the server’s tools and lists them on the Tools tab. The catalog includes search and reasoning tools (retrieve, ask, list_agents), reading tools (fetch, fetch_blob, call_function), schema discovery (get_schema, search_paths), and mutation tools (create_entity, update_entity, delete_entity, do_action). See Microsoft’s Work IQ MCP tool reference.
Tools start as Pending review or automatically Approved, depending on the server configuration and your tenant’s defaults. See Require tool approval and Default tool classification.
Before users can call a tool, approve it, add it to a toolset, and bind an access profile. Follow Govern tools and toolsets.
If write tools return a policy-denied error, confirm that Work IQ MCP policy in Microsoft allows writes. See Allow Work IQ operations in Microsoft, then govern them in C1.
Discovered tools don’t prove that Microsoft authorization is complete or that every operation is allowed. Verify the connection by having an approved user sign in and call a read tool against Microsoft 365 data they already have access to.
Manage your Microsoft Work IQ credentials
- Rotate the app secret: Create a new client secret in Entra, update the server’s authentication settings in C1, and verify a user can connect before removing the old secret. Schedule rotation before its expiration.
- Renew a manually supplied token: Obtain a new delegated Work IQ access token and update the bearer token in C1 before it expires.
- Change access: Review app consent and user access in Entra, Work IQ policy in Microsoft 365, and toolsets and access profiles in C1. Users may need to reconnect after consent or authentication settings change.
Troubleshoot Microsoft Work IQ setup
Use these checks to distinguish Microsoft tenant setup from C1 tool governance.Fix denied write operations
Reads such asfetch or retrieve can work while writes such as create_entity or do_action fail. A write must be allowed by C1, by Work IQ MCP policy in Microsoft, and by the user’s own Microsoft 365 permissions. Check each layer in order.
1
Confirm the write tool is available in C1. On the server’s Tools tab, check that the write tool is Approved, is in a toolset, and that the toolset is bound to an access profile the user has. If the AI client doesn’t list the tool at all, the issue is in C1. See Govern tools and toolsets.
2
Confirm Microsoft allows writes. Microsoft blocks create, update, delete, and action requests by default, so this is the most common cause. If C1 forwards the call and Work IQ returns a policy-denied error, have a Microsoft 365 administrator open Agents > Tools > Work IQ MCP > Policy in the Microsoft 365 admin center and allow the operation. Changes can take up to 24 hours to apply, so retry the next day before investigating further. See Policy governance for Work IQ MCP.
3
Confirm the user can make the change in Microsoft 365. Work IQ only allows changes the user could make themselves. For example, the user needs edit access to a file, or send-as rights for a shared mailbox. Test the same action directly in Outlook, Teams, or SharePoint as that user. If it fails there, adjust the user’s Microsoft 365 permissions.
4
Check which identity made the call. With a bearer token, every call runs as the token owner, not the calling C1 user. Confirm the token owner has the required Microsoft 365 permissions, or switch to per-user OAuth.