Communication
Connecting Outlook to an Autonomous AI Agent
Outlook is where professional email and calendars concentrate. An Atako agent can sort messages, prepare replies, and organize appointments, without ever seeing your Microsoft password.
Coming soon — create your account and we'll notify you as soon as this integration is ready.
Possible workflows
Sorting and reply drafts for the shared inbox
A support@ or contact@ inbox receives dozens of messages a day. The agent lists unread messages with list_messages, sorts them by category with add_category_to_message (billing, bug, general question), then drafts a reply with create_draft for every clear request. A human reviews and sends it with send_draft. The agent only uses send_email if it's been given that specific grant.
Automatic appointment scheduling from an incoming email request
A customer asks for a meeting by email. The agent retrieves the request with get_message, checks free slots with check_availability, creates the event with create_event once a slot is chosen, then prepares a confirmation reply with create_draft. The appointment only appears on the calendar once the create_event grant has been given, and the reply only goes out after human review, unless send_draft or send_email has been explicitly authorized.
Calendar cleanup and conflict alerts
The agent lists upcoming events with list_events, spots overlaps between two meetings or an appointment left unconfirmed, and prepares a cancellation with cancel_event only if that grant has been given. Without it, it simply flags the conflict in a draft addressed to the organizer with create_draft, so a human can decide.
Connector actions
list_messages
Read. List message IDs from a folder, filterable by category.
search_messages
Read. Search messages with an Outlook query.
get_message
Read. Retrieve a full message, headers and body included.
get_thread
Read. Retrieve an entire conversation grouping several messages.
list_events
Read. List calendar events over a given period.
check_availability
Read. Check free and busy slots for a connected mailbox.
create_draft
Write. Create a reply draft without sending it.
send_draft
Write. Send an existing draft.
send_email
Write. Send an email directly from the connected account.
move_message
Write. Move a message to another folder.
create_event
Write. Create a calendar event, with its attendees.
cancel_event
Write. Cancel an existing calendar event.
Prerequisites
- Admin role on the Atako company to connect the integration.
- A personal Microsoft account or a Microsoft 365 work account whose mailbox and calendar need to be connected.
- Microsoft OAuth consent, scopes Mail.ReadWrite, Mail.Send, and Calendars.ReadWrite.
- An explicit grant per agent, especially for the send_email and create_event actions.
How to connect
- 1
Open Settings, Integrations
An admin selects Outlook from the list of available connectors.
- 2
Review the exposed actions
The window shows every mail and calendar action, read and write, before authorization.
- 3
Authenticate through the Microsoft screen
Redirect to Microsoft consent, no password sent to Atako.
- 4
Grant access to an agent
You choose the precise actions per agent, for example create_draft and check_availability alone to stay cautious.
Why Connect an Autonomous Agent to Outlook
Outlook is where both email and the calendar concentrate for a large share of companies, especially those on Microsoft 365. An autonomous agent connected to it doesn't just respond to a single command: it runs continuously and decides, depending on the instruction it receives, to search for a message, check a free slot, or prepare an appointment, through tool calling.
The connection uses OAuth 2.0 and the Microsoft Graph scopes Mail.ReadWrite, Mail.Send, and Calendars.ReadWrite (Microsoft Graph permissions reference). These scopes allow reading, composing, and sending emails, and managing calendar events, never deleting an account or changing security settings.
That's what makes a workflow like scheduling an appointment from an incoming email useful, close to what a support triage or support automation agent does: it receives a request and prepares the next step (a slot, a confirmation draft) without waiting for a human to open their calendar to check availability. Outlook is one of the integrations covered by the Standard plan, with no separate billing line per connector.
Limits and Best Practices
The connector's most sensitive actions are send_email and create_event: once granted with write scope, the agent sends an email or books an appointment without checking back with you. The safest practice is to grant only create_draft and check_availability: the agent prepares, a human validates.
The Mail.ReadWrite and Calendars.ReadWrite scopes cover the entire connected mailbox and calendar, not one specific folder or calendar. The real limit therefore comes from the grant: list the exact actions the agent needs rather than granting everything at once when you connect.
The documentation doesn't mention a rate limit specific to the Outlook connector. Every call, whether sent or refused, stays visible in the agent page's audit log. And as with any OAuth account, if the token expires or is revoked on the Microsoft side, the connection switches to error status until it's reconnected.
Related use cases
Related integrations
Frequently asked questions
Can the agent send an email or create an appointment without validation?
Yes, if the grant includes send_email or create_event with write scope, the agent then acts directly. Most companies prefer to grant only create_draft and check_availability: the agent prepares, a human reviews and triggers the send or confirms the proposed appointment.
Do you need a paid plan to connect Outlook?
Yes, an active Atako plan is required, but Outlook is one of the integrations already included in the Standard plan, with no extra cost per connector.
How do you revoke Atako's access to my Outlook mailbox and calendar?
From Settings, Integrations, click Revoke on the Outlook connection. The encrypted token is deleted immediately, and every agent that was using it loses access right away.
Does the Calendars.ReadWrite scope let the agent see colleagues' calendars?
No, this scope only covers the connected Microsoft account. The agent only sees a colleague's calendar if it has been explicitly shared with that account beforehand, independent of the connector.
What to read next
Sources
- Microsoft Graph, permissions reference · accessed on September 7, 2026
- Microsoft Graph, sendMail API guide · accessed on September 7, 2026
CTO at Atako
This content was written by Atako's AI agents, then reviewed, corrected, and approved by Romain Laodicina, CTO of Atako.