Messaging
AI agents that use Microsoft Outlook
UtilitySpaces gives an AI agent scoped access to Microsoft Outlook through its own encrypted connection, not your password. The agent can call 3 named Microsoft Outlook tools, and the one that writes waits for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.
What an agent can do in Microsoft Outlook
Read and send email through the connected Microsoft 365 mailbox. An agent calls these by name, and matching is exact.
| Tool | What it does | Waits for approval by default |
|---|---|---|
| List messages | List messages in the mailbox. | No — read only |
| Get message | Get a single message by id. | No — read only |
| Send mail | Send an email from the mailbox. | Yes — it writes |
2 read tools, 1 write tool. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.
What teams hand an agent in Microsoft Outlook
Teams hand an agent the mailbox reading in Microsoft 365: listing recent messages with List messages, opening one with Get message, and turning what matters into inbox items or summaries. Send mail is the only write, and it waits for approval unless an admin has set this connection to run without asking.
- Summarise the morning's mail into the inbox by listing recent messages and flagging the ones that ask for a decision or reply.
- Pull a specific email when someone in chat asks what a client or vendor said, by reading the message and quoting the relevant part.
- Send a drafted reply or a status update to a named recipient when a flow completes or a deadline approaches (after a person approves it)
What waits for a person
Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toMicrosoft Outlook, approved, rejected or unattended, is logged.
- Send mail POST
What connecting Microsoft Outlook takes
Microsoft Outlook uses OAuth, so you authorise in Microsoft Outlook’s own screen and no secret is ever typed into UtilitySpaces. The connection asks for 3 scopes, fixed in the catalogue and shown to you by Microsoft Outlook before you agree:
- offline_access
- Mail.ReadWrite
- Mail.Send
Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.
Where Microsoft Outlook fits
Give an agent Microsoft Outlook work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.
Other messaging integrations: Chatwoot, Discord, Gmail. Or see every application agents can connect to.
See it doing your actual work
Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.
We reply to every message within one business day.