> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/microsoft-work-iq.md).

# Microsoft Work IQ

Microsoft Work IQ is the intelligence layer over Microsoft 365. Connect to read and act on mail, calendar, files, Teams, and SharePoint, and to ask Microsoft 365 Copilot questions grounded in your organization's work.

* MCP connection

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector               | Authentication |
| ----------------------- | -------------- |
| Microsoft Work IQ (MCP) | MCP with OAuth |

#### Microsoft Work IQ (MCP)

Connect to Microsoft Work IQ's MCP server for AI-powered access to Microsoft 365 mail, calendar, files, Teams, SharePoint, and Copilot. Signs in with Microsoft Entra ID and acts as the signed-in user.

**Set up in Microsoft Work IQ**

1. Obtain access to the Microsoft Work IQ MCP server and the tools that your workflow will use. Use the server URL supplied by the provider or your administrator.
2. If your organization restricts application access or user consent, have its administrator approve the connection before you sign in.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Microsoft Work IQ (MCP)**.
2. Select **Connect**, sign in to the provider account, and review the requested access. Complete authorization to return to StackAI.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field          | Required                 | What to enter                                                                                                                                                                                                         |
| ---------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Client Secret          | Optional / as applicable | The OAuth client secret (e.g., 1234567890). You may not need to set this, the OAuth flow will try to set it with Dynamic Client Registration, but some MCP Servers don't support it, so they require a Client Secret. |
| Custom Headers         | Optional / as applicable | Enter the custom headers issued for the account or service you are connecting.                                                                                                                                        |
| MCP Server URL         | Yes                      | The MCP server URL (e.g., <https://mcp.example.com>).                                                                                                                                                                 |
| Client ID              | Optional / as applicable | The OAuth client ID (e.g., 1234567890). You may not need to set this, the OAuth flow will try to set it with Dynamic Client Registration, but some MCP Servers don't support it, so they require a Client ID.         |
| Authorization Endpoint | Optional / as applicable | The OAuth endpoint URL (e.g., <https://mcp.example.com/oauth2/authorize>). You probably don't have to set this, the OAuth flow will try to discover it on its own.                                                    |
| Description            | Optional / as applicable | Optional description for this MCP server connection.                                                                                                                                                                  |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Important behavior

If an operation is denied, check the connection’s granted permissions and the account’s access in the provider. Reauthorize the connection when it needs additional permissions.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/microsoft-work-iq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
