Microsoft 365 connector
Your mail is in Microsoft 365 or Exchange Online.
Free and open source. Your agent works in your on-premises Exchange mailbox as you, with no more rights than you have.
Works with these parts of an Exchange mailbox, through Exchange Web Services.
Your mail is in Microsoft 365 or Exchange Online.
Your mail is on Exchange Server in your own data centre: 2016, 2019 or Subscription Edition.
Sign in
The assistant “Agent” asks to use your mailbox. After you sign in, you return to https://agent.example.com/callback.
Connected
You are signed in as user@example.com with AD FS. The assistant has no rights beyond yours.
What is in my inbox today?
Agent
Checked your mailbox
Two new messages today. The newest is from your manager, marked important and still unread.
Want a short summary?
Find an hour next week when my manager and I are both free.
Agent
Compared both calendars
Tuesday 24 November, from 10:00 to 11:00 works for both of you. Two more open slots:
Shall I book Tuesday and invite your manager?
Draft a note to my manager confirming the meeting. Don’t send it.
Agent
Saved a draft
The draft is in your Drafts folder and nothing was sent.
Illustrations with made-up data, shortened.
If your mail runs on your own Exchange Server, the connector for it should run there too. This one talks to Exchange Web Services. Microsoft is turning them off in Exchange Online between October 2026 and April 2027, and keeps them in Exchange Server.
“Write to my manager that Tuesday works, and send it.”
It saves a draft in the person’s Drafts folder. Nothing has been sent.
Only then is the draft sent, to at most 20 recipients. No more than 10 outward actions go out a minute.
Finds people in the address book, personal contacts and rooms, and finds meeting times.
Sends only after the person confirms. At most 20 recipients. Deleted items go to Deleted Items. Text from mail is marked as someone else’s data.
No database. Tokens are sealed with AES-256-GCM, and the key comes from Vault, OpenBao or a Kubernetes Secret, never from an environment variable.
A person signs in with AD FS or with a password. We recommend AD FS.
Swipe the table sideways to see all three columns.
| Capability | AD FS (recommended) | Password |
|---|---|---|
| Needs | Exchange 2019 CU13 or later, or Subscription Edition, and AD FS set up by administrators | Any Exchange with Exchange Web Services |
| The password | The server never sees it | Sealed inside the person’s own tokens |
| Checked on a live server | Not yet, only unit tests against a fake AD FS | Yes, Exchange Server 2016 CU23 |
Password mode has no second factor. Its risks, and what holds each, are in the sign-in guide on GitHub.
A name for the server, a certificate and a route to Exchange Web Services. AD FS mode also needs AD FS set up.
One container, from a public image.
Any MCP client can register itself, and each person signs in once.
Yes. Apache-2.0: use it, change it, run it commercially.
The connector runs on your servers and talks to your Exchange, and to AD FS if you use it. It has no database.
It writes a draft. It sends only after the person confirms, to at most 20 recipients.
Only the signed-in person’s own mailbox, with no more rights than that person has. Other mailboxes, shared mailboxes and impersonation do not exist in it.
Inbox rules, forwarding, delegates, other mailboxes, impersonation, export and permanent deletion do not exist in it.
Exchange Server 2016, 2019 and Subscription Edition. We tested it live against Exchange Server 2016 CU23.
Not yet against a live AD FS, only against a fake one in unit tests. Password mode has been tested against a live server. Try AD FS with one person first.
There is no second factor, and the person’s password is held sealed inside their own tokens. That is why AD FS is the preferred mode.
Use the Microsoft 365 connector. Microsoft is turning Exchange Web Services off in Exchange Online.
No. Wide Moat builds it. It is not affiliated with or endorsed by Microsoft.
Who made it
Wide Moat runs AI inside your company: chat, coding workspaces, a model gateway with a key for each person, and connectors like this one.
Microsoft, Exchange Server, Exchange Online and Active Directory Federation Services are trademarks of the Microsoft group of companies. This connector is not affiliated with or endorsed by Microsoft.