> For the complete documentation index, see [llms.txt](https://docs.aisuru.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisuru.com/en/advanced-features/integrations/mcp/aisuru-mcp-which-ones-and-how-to-activate/21.-outlook-mcp-server.md).

# 21. Outlook MCP Server

**Outlook MCP Server** connects a Microsoft Outlook / Microsoft 365 mailbox to your agent: read and search emails, read and download attachments, send messages, manage calendar and contacts , always on behalf of the connected user.

## What it can do

* Search and read emails (by sender, subject, date range, folder)
* Read attachments and **extract their text** (PDF, Word, Excel, images via visual recognition)
* Compose and send emails in plain text or HTML
* View and create calendar events

## Examples

*"Find the last 5 emails from Mario Rossi and summarise them."*\
\
\&#xNAN;*"Download the attachment of the latest invoice and tell me amount and due date."*\
\
"*Write an email to* [*client@example.com*](mailto:client@example.com) *confirming tomorrow's 3pm meeting."*

## How access works

Each user connects their own mailbox with a secure Microsoft login (you never share a password with the agent).

It happens in chat: the agent offers a sign-in button, the user logs in with Microsoft and grants the permissions. From then on the agent works **only** on that user's mailbox.

### **Is it safe?**

Absolutely! Your **email account is connected securely** through Microsoft's official login system (OAuth) and the assistant **never stores or sees the user’s password.**

## Configuration parameters

| Parameter          | Required | Description                                                                                                                                                                                                                                    |
| ------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `MS_TENANT_ID`     | Yes      | Microsoft Entra (Azure AD) Directory (Tenant) ID.                                                                                                                                                                                              |
| `MS_CLIENT_ID`     | Yes      | Client ID of the Azure App Registration dedicated to Outlook.                                                                                                                                                                                  |
| `MS_CLIENT_SECRET` | No       | Client Secret of the App Registration. Not required if the app is set up as a "public client" on Azure.                                                                                                                                        |
| `IDENTITY STRICT`  | No       | `true`/`false`. Default: `true`. The connected Outlook account must match the AIsuru user's email in chat (IDENTITY STRICT must be true). If true, actions will be performed only when AIsuru account email matches the Outlook account email. |

### Custom parameters

No additional parameters needed.

### Configuration parameters: register a Microsoft (Azure) app

1. Open the **Azure portal** ([portal.azure.com](http://portal.azure.com/)) and go to **Microsoft Entra ID → App registrations → New registration**
2. Give it a name (e.g. "AIsuru Outlook") and pick the account types that fit your case
3. Under **Authentication** add a *Web* platform with redirect URI `https://mcp.aisuru.ai/oauth/verify` and enable access tokens
4. Under **API permissions → Microsoft Graph (delegated)** add: `Mail.ReadWrite`, `Mail.Send`, `Calendars.ReadWrite`, `offline_access`, `User.Read`, then grant admin consent
5. Copy the **Application (client) ID** and **Directory (tenant) ID** from the Overview page
6. (Optional) Under **Certificates & secrets** create a *new client secret* and copy its value immediately (shown only once) and past it as MS\_CLIENT\_SECRET.

{% hint style="info" %}
**Note:** for most uses you don't need to create anything: the in-chat Microsoft login is enough. This technical setup is only for those who want to use their **own Azure enterprise app** (recommended for companies).
{% endhint %}