Skip to main content
Connect your Microsoft account once and let an agent work across your Microsoft 365 as you: read and draft Outlook mail, manage your calendar, browse, read, upload and organize files in OneDrive and every SharePoint site you can see, read your own Teams chats and, if you allow it, read your Teams meeting transcripts. This is the simplest way to give an agent Microsoft 365 access. If you need finer control — for example an agent that only touches SharePoint, or one that runs on its own identity rather than yours — the separate Outlook, Outlook Calendar and SharePoint capabilities are still available and keep working as before.
This is a personal connection. The agent acts as you in Microsoft 365, and anyone who can use the agent acts through your connection. Use it on agents only you have access to, and keep sending and deleting off unless the agent genuinely needs them.

​
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 anyone can complete the connection. If you see an “Almost There” message after sign-in, that page carries an approval link and a ready-to-send message — forward it to a Microsoft tenant admin. Once they approve, come back and connect again. Approval is a one-time step for the whole organization.

​
Sensitive actions

Three 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.
  • Allow reading meeting transcripts — lets the agent read the transcripts of Teams meetings you organized or were invited to. It needs a token created after the setting is on, and a one-time approval from a Microsoft admin. See Meeting transcripts.
Workspace admins can lock any of these settings for all agents.

​
Teams is read only

The agent can list your Teams chats (1:1, group and meeting chats) and read their messages. Every Teams meeting on your calendar has a meeting chat, so you can ask about a meeting by name — for example “what was said in the chat for yesterday’s project sync?” — and the agent goes from the calendar event straight to its chat. The chat also shows whether a meeting was recorded or transcribed. It cannot post to Teams, and it does not see team channel posts — that needs 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.

​
Meeting transcripts

With Allow reading meeting transcripts on, the agent can read the transcript of a Teams meeting and save it as a document in the chat. Ask for it the same way as for the chat — for example “summarize the transcript of this morning’s steering group and list the action items”. What you need
  1. Turn on the setting — on the capability card, turn on Allow reading meeting transcripts. It appears when Teams chats is on.
  2. Create a new token — click Create new on the capability card. Tokens created before the setting was on do not include transcript access, and the card warns you when the selected token lacks it.
  3. A Microsoft admin approves transcript access — Microsoft always requires an admin for this permission, even when your organization already approved the Microsoft 365 Assistant. If you are not an admin, you get the “Almost There” page with an approval link to forward. Once they approve, create the token again.
  4. A Teams admin allows apps to read transcripts — in the Teams admin center go to Meetings → Meeting settings → Transcript API access, turn Microsoft Graph access on, and under Configure allow speaker attribution so the transcript keeps speaker names. Microsoft turned this off for every tenant in 2026; the change can take up to 30 minutes to apply.
Which meetings work
  • Scheduled Teams meetings that you organized or were invited to, recurring meetings included. This covers channel meetings too, as long as you were on the invite.
  • The meeting must have been transcribed: someone started transcription during the meeting, or the meeting options start it automatically. The transcript appears a few minutes after the meeting ends.
  • Ad-hoc calls (Meet now) are not supported.
  • Microsoft keeps transcripts readable only while the meeting has not expired, which for a scheduled meeting is 60 days after it ends.
The Microsoft Teams capability can also read transcripts, as its own bot rather than as you. It reaches only private meetings the bot was added to, but it can act on its own when the meeting ends.

​
Working with OneDrive

The file tools are shared with SharePoint. To reach your own OneDrive, the agent first calls get_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 four 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?”
  • Meeting follow-up — “Read the transcript of today’s customer call and draft a recap email with the agreed next steps”