AI agents for Microsoft 365
Outlook, Teams and Office — the other half of many stacks. AGNT connects to Microsoft 365 so agents can read what happens there, reason about it, and act — with a receipt for every run.
Inbox Triage is a ready-made agent that works in Microsoft 365 — free, and it runs on your machine.
Microsoft 365 and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in Microsoft 365. |
|---|---|
| Connects with | Bearer — held in the local vault |
| AGNT node | custom-api, or the zapier-action bridge |
| Runs when | An email arrives |
| Typical build time | Ten minutes |
| Where data goes | Nowhere by default — AGNT runs on your machine and credentials never leave it. |
What you can automate
Reacts when…
- an email arrives
- a file changes
- a meeting is scheduled
Agents can…
- send mail and messages
- read and file documents
- update calendars
Teams use it for
- triage across Outlook like Gmail
- documents summarised on arrival
- meetings prepped and followed up
The Microsoft 365 workflow, to configure
Design goal for Microsoft 365: triage across Outlook like Gmail; documents summarised on arrival; meetings prepped and followed up. The template below supplies configurable nodes, not the complete logic for those goals.
Use this Microsoft 365 setup template to arrange the schedule, input review and API operation. Configure the account-specific fields and add your own decision and approval controls before activation.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "09c5bd2f-e236-4120-a113-2f93942a9510",
"name": "Microsoft 365 — read, decide, act",
"nodes": [
{
"id": "66476341-898c-424d-ad3c-3a3a1c316d7e",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "clock",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "f270f139-bbf3-4976-ac70-9ff59771ebb4",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Decide what needs to happen in Microsoft 365. Explain your reasoning.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "8c334a4d-64a6-4f6f-a906-bf32b353fabe",
"text": "Call the Microsoft 365 API",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://graph.microsoft.com/v1.0/me/messages",
"method": "GET",
"authType": "None",
"headers": "{}",
"query": ""
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "8375f193-ec42-4c7c-adb5-7399042480b4",
"start": {
"id": "66476341-898c-424d-ad3c-3a3a1c316d7e",
"type": "output"
},
"end": {
"id": "f270f139-bbf3-4976-ac70-9ff59771ebb4",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "f2933580-90ef-454b-a18c-c0b90d3a9252",
"start": {
"id": "f270f139-bbf3-4976-ac70-9ff59771ebb4",
"type": "output"
},
"end": {
"id": "8c334a4d-64a6-4f6f-a906-bf32b353fabe",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
https://graph.microsoft.com/v1.0/me/messages. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Install Inbox Triage — it runs on Microsoft 365
Inbox Triage is a working agent that uses Microsoft 365. Installing it drops the whole workflow onto your canvas — connected, editable, and yours to change.
Runs on your own machine · See what it does
The other half of the stack
Outlook, Teams and Office cover the same ground as the Google tools for a large share of organisations, and everything that works against Gmail and Drive applies here: triage, document summarisation, meeting preparation and follow-up.
One runtime across both worlds
Plenty of companies run both. Because workflows are built against capabilities rather than a single vendor, the same triage or reporting process can operate across Microsoft and Google without being written twice.
Microsoft 365 without a first-party node
Reaching Microsoft 365 means one custom-api node rather than a purpose-built one. The endpoint and its bearer credentials are all it needs, and the zapier-action bridge covers it too if you would rather not hand-roll the request.
| What you need | Value |
|---|---|
| Endpoint | https://graph.microsoft.com/v1.0/me/messages |
| Method | GET |
| Authentication | Bearer |
| Header | Authorization: Bearer {aadToken} |
| Reference | Microsoft 365 API documentation |
Worth knowing: Graph covers Outlook, Teams, OneDrive and Entra behind one host; the scope you granted decides what the same URL returns.
One thing to know before you build
Graph covers Outlook, Teams, OneDrive and Entra behind one host; the scope you granted decides what the same URL returns.
It is worth getting right first, because the failure is quiet rather than loud — you get a response, it just is not the one you wanted. Once past it, Microsoft 365 is a straightforward API to automate against.
Connect Microsoft 365 in two minutes
- Download AGNT Community Core — free, local-first, no account needed to run.
- Connect with one OAuth sign-in from AGNT’s vault — tokens are stored encrypted on your machine and never leave it.
- Drop the Microsoft 365 node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
Microsoft 365 + AGNT — common questions
Does email triage work with Outlook?
Yes — the same classify, draft and escalate pattern applies.
Can it handle documents in OneDrive and SharePoint?
Yes, reading, summarising and filing as with any document source.
Do I need admin consent?
Connecting requires the permissions your organisation grants; tokens are stored encrypted on your machine.
