Microsoft 365 and Teams Are Now Live: Outlook, Calendar, OneDrive, and Teams for Your AI Agents

Microsoft 365 and Microsoft Teams are now connected in AgentTeams. Your AI agents can read and send email from Outlook, manage Calendar events, work with files in OneDrive and SharePoint, and send and receive messages in Teams channels and DMs. This is the same shape of integration we already shipped for Google Workspace and Slack, now mapped to the Microsoft side of the world.

If your business runs on Microsoft 365 and Microsoft Teams, you no longer have to pick between "use AgentTeams" and "keep working where we work." You get both. This article walks through what is live, how to connect it, what to do if your tenant is locked down by IT, and a few real use cases to copy from.

What is live

Four surfaces, four sets of dedicated tools plus a generic passthrough so your agents can call anything the Microsoft Graph API supports:

• Outlook (email). Read inbox threads, draft and send replies, file messages to folders, set follow-up flags, search the mailbox. Works for personal Microsoft accounts and tenant-managed work mailboxes alike.
• Calendar. Create events, RSVP, find free/busy slots across attendees, reschedule, send meeting invitations with Teams links auto-attached. Time zones are handled correctly because we read each user's tenant time zone on connect.
• OneDrive and SharePoint. Search across files, read document content, create new files, share links with specific people or with the whole org under your existing sharing policy. Permissions stay scoped to the connecting user, so no agent can quietly read a folder its operator could not.
• Microsoft Teams. Send and receive messages in channels and DMs, post replies in existing threads, upload files into a channel, list channels and members for an agent to discover. Inbound webhooks fire in real time, so your agents respond to a Teams ping the same way they respond to Slack.

Every one of these surfaces ships with a generic microsoft_api passthrough tool alongside the dedicated tools above. So if your agent needs to do something we have not wrapped explicitly (set an out-of-office, manage a distribution list, create a Planner task), it can call Microsoft Graph directly without you having to wait for us to ship the dedicated wrapper. This is the same pattern we use for Slack and GitHub.

How to connect: personal Microsoft account

If you sign in to Outlook with an @outlook.com, @hotmail.com, or @live.com address, or if you are the admin of your own small-business Microsoft 365 tenant, the connect flow is two clicks.

1. Open your agent in AgentTeams and go to the Tools tab.
2. Find Microsoft 365 and click Connect.
3. Sign in to the Microsoft account you want the agent to act as, and approve the listed permissions (Mail.Send, Calendars.ReadWrite, Files.ReadWrite, Chat.ReadWrite, ChannelMessage.Send, and a few more).
4. You are returned to the agent page and the integration shows as Connected. The agent can now read and write across all four surfaces above.

The connection is scoped per agent, not per organization. So your support agent can be connected to one mailbox and your sales agent to another, with no overlap. Tokens are encrypted at rest and refresh automatically; you do not need to reconnect every few weeks.

How to connect: managed Microsoft 365 tenant

This is the path most mid-sized businesses end up on. If your IT team controls who can grant consent to third-party apps, the personal-account flow above will return an AADSTS90094 error after sign-in: "The grant requires admin permission." That is Microsoft doing exactly what your IT team configured it to do. You have not done anything wrong. Here is the path that works:

1. In the connect wizard, click I need admin approval. AgentTeams generates a tenant-wide admin-consent URL specific to your Microsoft tenant.
2. Copy the admin-consent URL and send it to your IT admin (or open it yourself if you are the admin). One click in that URL grants AgentTeams the listed permissions for everyone in your tenant. It does not give us access to anyone's data; it only allows individual users to authorize their own agent connections.
3. Once the admin has clicked through, return to the wizard and click Try again. Sign in, approve the user-level consent, and the connection completes.

You only have to do the admin-consent step once per tenant. After that, every user in your company can connect their own agent to their own Microsoft 365 surfaces without going back to IT. The total time, end to end, is usually under an hour, most of which is the IT admin getting around to clicking the link.

Real use cases, copy these

The integration is most valuable when agents combine several Microsoft surfaces with a third-party tool. A few that customers are already running:

• Support agent that lives in Teams. Customer asks a question in a Teams channel. The agent searches your knowledge base, drafts an answer in the thread, and if the question needs human input, escalates to a named teammate via DM with the conversation context attached.
• Sales follow-up that closes the loop in Outlook. When a deal stalls in your CRM, the agent drafts a follow-up email in Outlook (in your voice, with the deal's actual context), sets a reminder for three days out, and pings you on Teams if the prospect replies.
• Operations agent that handles meeting prep from OneDrive. Before every external meeting on your Calendar, the agent pulls the latest deck from OneDrive, summarizes the last touchpoint email from Outlook, and posts a pre-read into the meeting's Teams channel. No more walking into a meeting cold.
• Recruiting agent that schedules without the back-and-forth. When a candidate replies to your sourcing email, the agent checks your Calendar free/busy, proposes three slots, and once the candidate picks one, sends the Teams meeting invite with the interview brief pre-attached.

The pattern that makes these work is the same pattern that makes our multi-agent setups work in general: one agent, multiple tools, one outcome. Microsoft 365 just removes a major category of "the agent can do this but only on the Google side" gaps.

Common gotchas

A few patterns we have seen in the first weeks of customer rollouts:

• Inbound Teams webhooks need a tenant admin to install the AgentTeams app in your tenant. Outbound (the agent posting to Teams) works as soon as the user-level connection is complete. Inbound (the agent listening for new messages in a channel) requires the app to be approved in your tenant's app catalog. The connect wizard will walk you through it.
• Conditional Access policies that block legacy authentication can also block the OAuth refresh path. If your tenant has Conditional Access on "non-modern auth blocked" with a strict location policy, refresh tokens from non-tenant IP ranges may be rejected. The fix is on the IT side: allow AgentTeams in your Conditional Access exclusion list, or run the agent from a known IP.
• Formatting in Teams uses HTML, not Markdown. Agents emit CommonMark Markdown by default; we convert to Teams HTML for you, so headings, bold, lists, and links render correctly. If your agent emits raw HTML on purpose, that also works. Slack-style mrkdwn does not.
• Calendar invitations sent from an agent show the agent as the organizer, not the user. This is a Microsoft Graph constraint, not ours. If the user needs to be the organizer (for example, for legal signature visibility), the agent can draft the invitation as a Calendar event for the user to send, rather than sending it directly.

Where this fits

Microsoft 365 is one of the heaviest-used integrations in the AgentTeams catalog now, alongside Google Workspace, Slack, GitHub, and Help Scout. If you were waiting to roll out AI agents because half your team lives in Teams and Outlook, that wait is over. Setup runs through a guided wizard, the admin-consent path is handled for managed tenants, and the same agent that handles your Slack channel can now handle your Teams channel without any prompt rewriting.

If you are evaluating AgentTeams against other AI agent platforms, Microsoft 365 parity is one of the questions we hear most often. The answer, as of this week, is yes.

Ready to connect your first agent to Microsoft 365? Open your agent's Tools tab and click Connect Microsoft 365. Or, if you are new to AgentTeams, start with the first-agent onboarding guide.