How to enable
Can’t find Microsoft 365 Assistant in the capability list? It is only offered when Microsoft OAuth is configured for your deployment. The standard Abundly cloud has this in place, but a dedicated or self-hosted deployment might not — ask your Abundly contact.
1
Enable the capability
Go to Settings → Capabilities and enable Microsoft 365 Assistant.
2
Connect your Microsoft account
Click Create new to sign in with your Microsoft account and create a personal access token. One sign-in covers mail, calendar, OneDrive and SharePoint. The token belongs to you and can be managed in your profile settings.If you already have a Microsoft 365 Assistant token from another agent, select it from the dropdown instead.
3
Choose what the agent can reach
On the capability card, turn Mail, Calendar, Files and Teams chats on or off. All four are on by default. Turning off what an agent doesn’t need keeps it focused on the right tools.
In many organizations, a Microsoft admin must approve the Abundly app before the connection can be completed. If you see an “Almost There” message after sign-in, ask your admin to grant approval in Microsoft Entra, then try connecting again. Approval is a one-time step for the whole organization.
Sensitive actions
Two actions are off by default and must be enabled explicitly in the capability settings:- Allow sending email — turns the draft tool into a send tool: the agent sends immediately, unless it chooses to save a draft instead. It works on any Microsoft 365 Assistant token, no reconnect needed. When on, a Who can the agent email? section appears with the same recipient guardrails as the Send Email capability: an allowed list of addresses and domains, and rules for whether the agent sends, asks for your approval, or is blocked for recipients inside and outside the list. Sending starts out restricted to your own address with approval required for anyone else.
- Allow deleting calendar events — lets the agent delete events and cancel meetings you organized. Cancelling a meeting notifies every attendee.
Teams is read only
The agent can list your Teams chats (1:1, group and meeting chats) and read their messages. It cannot post to Teams, and it does not see channel messages or meeting transcripts — those need permissions only a Microsoft admin can grant, and they are deliberately left out of a personal connection. For an agent that participates in Teams conversations, use the Microsoft Teams capability, which runs as its own bot.Working with OneDrive
The file tools are shared with SharePoint. To reach your own OneDrive, the agent first callsget_my_onedrive to get the drive id and then uses the document tools with that drive — you don’t need to do anything, just ask for a file in your OneDrive.
If your account has no OneDrive (some licences don’t include one, and organizations can disable it), the agent is told so plainly. Mail, calendar and SharePoint sites keep working.
Technical details
This section describes exactly what the integration requests and how access is scoped. Useful when a Microsoft admin needs to review the app before granting consent.
What the agent connects to
Microsoft 365 runs against Microsoft Graph (graph.microsoft.com/v1.0) using delegated OAuth 2.0 through the Microsoft identity platform. The integration is registered as a multitenant app against the organizations endpoint, so work and school accounts are supported and personal Microsoft accounts are not.
Everything the agent does is scoped to the connected account. It sees the mailbox, calendars, OneDrive and SharePoint sites that you can see, and nothing more.
Permissions requested
All permissions are delegated — the agent acts as the connected user and can never do more in Microsoft 365 than that user can.
Tools exposed to the agent
The capability reuses the tools from the Outlook, Outlook Calendar and SharePoint capabilities, gated by the Mail, Calendar and Files toggles, plus three additions:Tokens and access
- The connection is stored as a personal token that belongs to you, not to the workspace or the agent. Manage it under Profile settings → Personal Tokens, where you can see which agents use it and disconnect it.
- Access tokens are refreshed automatically shortly before they expire, using the refresh token from
offline_access. See Credentials for how Abundly handles credentials generally. - The agent never sees the token. Authentication is attached when the platform calls Microsoft Graph, after the model has decided what to do.
- Every tool call is recorded in the agent’s activity log.
Admin-side controls
Your Microsoft admins keep full control independently of Abundly:- Admin consent — many tenants require an admin to approve the Abundly app in Microsoft Entra before any user can connect.
- Conditional Access — your existing policies apply to the delegated token.
- Revocation — removing the enterprise application in Entra, or revoking the user’s sessions, cuts off every agent using it immediately.
Example use cases
- Morning briefing — “Every weekday at 8, summarize my unread mail and today’s meetings”
- Meeting prep — “Before my 2 pm with Acme, find the latest proposal in my OneDrive and the last three emails from them”
- Filing — “Save the attachments from this week’s invoices to the Finance library on the Operations site”
- Scheduling — “Find an hour next week when I’m free and draft an invite to the project team”
- Catch-up — “What did the team decide in our group chat while I was out yesterday?”

