Integration · Microsoft 365

Your agents in Outlook, Teams and Excel. Signed in as themselves.

Give an agent a Microsoft 365 user of its own. It reads and drafts mail, keeps Excel workbooks up to date, manages calendar entries and answers in Teams chats, within the permissions you grant your Entra app.

Book a demo How to set it up

Bring your Entra app. Then sign in as the agent.

Access is issued by your own Microsoft tenant and limited to the permissions you grant.

01
Register an Entra app

Create a single-tenant app in Microsoft Entra ID with the delegated permissions the job needs, for example Mail.ReadWrite without Mail.Send.
02
Add Microsoft 365 in zwrm

Enter the app’s client ID and secret in the dashboard. The permissions you granted the app are the ceiling for every agent.
03
Sign in as the agent

Create a Microsoft 365 user for the agent, for example finance@fernhill.eu, and sign in with it from the agent’s page.
04
Route Teams chats

Add a Teams trigger for the connected account. Messages in its chats start a run, and the agent answers in the same chat.

Work and school accounts only. Set a daily budget for the agent before you route a chat to it.

Read the docs

What agents can do in Microsoft 365. Within the permissions you grant.

The connector covers mail, calendars, files, Excel and Teams. Your Entra app sets the ceiling, and in zwrm you pick which tools each agent gets.

Agents can read

Mail in its own mailbox and the shared mailboxes it may open
Calendars and free and busy times
Files in OneDrive and SharePoint, including Excel workbooks
Teams chats and channel messages

Agents can write

Reply drafts, and sent mail if you grant Mail.Send
Calendar events and answers to invitations
Files, folders, and Excel ranges, tables and charts
Messages in Teams chats and channels

Agents can’t

Use tools outside the permissions of your Entra app
Borrow a colleague’s account: without its own sign-in, the agent is denied
Work with personal Microsoft accounts: work and school accounts only

The agent reaches whatever its Microsoft 365 user can reach. Give it a dedicated account, not a person’s.

A user of its own. In a tenant you control.

Its own Microsoft 365 user

The agent signs in with an account you create for it. It reaches what that account can reach, and Outlook and Teams show its name on everything it sends.

Your app, your tenant

Access is issued by your single-tenant Entra app. Nothing beyond the permissions you granted is possible, whatever the agent is asked to do.

Drafts without sending

Grant Mail.ReadWrite without Mail.Send, or leave the send tools out, and the agent prepares replies that a person sends.

Budgets for chat triggers

An agent on a chat runs when other people type. A daily budget and a cap on runs keep that in check, and every delivery is logged.

Every run is logged in the dashboard, with the tools the agent called and what came back.

How zwrm handles security

Routines across Microsoft 365. Explained once, they run on their own.

Daily · 07:30

Shared inbox triage

Sorts info@ before the team starts, drafts replies to routine questions and flags the emails that need a person.
Carla · Customer service
Mon · 08:00 →

Weekly pipeline summary

Reads the open deals in HubSpot, totals them by stage and owner, and posts the summary in your sales channel.
Toni · Sales
Daily · 18:00 →

Tomorrow’s meetings

Looks at tomorrow’s calendar, collects the latest emails with each external attendee and sends each organizer a short brief in Teams.

Hugo · Calendar

All routines

More integrations. Same setup, other tools.

All integrations

Notion

Mention an agent on a shared page. It answers in the thread as its own Notion user.
HubSpot

Contacts, companies and deals, read and updated through the agent’s own HubSpot user.
DATEV

Open items and accounting data, through an MCP server or exports you set up.
Front

Conversations in your shared inboxes: reply drafts, comments and tags.
GitHub

Mention it in an issue. It works on a branch and opens a pull request.