Connecting Outlook to BotTrottr: Exactly What We Request — and Why We Keep It Minimal
When you connect Microsoft 365 (Outlook) to BotTrottr, Microsoft shows a consent screen listing the permissions the connection will carry. That screen is worth reading — and we want it to be short. This post lays out the exact scopes we request, what each one is for, and the deliberate decisions we’ve made to look out for your safety.
Least privilege by default
BotTrottr agents do real work on your behalf — reading mail, drafting replies, checking your calendar, pulling a file from OneDrive. But an agent only needs the narrow slice of access that matches its task. So we request the smallest set that covers the Outlook tools we support, and nothing more. We don’t ask for broad, account-level control, and we never add a permission speculatively “just in case.”
The exact permissions we request
When you approve a BotTrottr Outlook connection, you’re granting exactly these application permissions:
- User.Read — read your basic profile (name and email address), so the connection can identify your account.
- Mail.Read — read messages in your mailbox, so an agent can triage, summarize, or draft replies.
- Mail.Send — send mail as you, so an agent can deliver the reply it drafted.
- Calendars.Read — read events in your calendar, so an agent can check availability and report what’s coming up. Read-only: agents can tell you about your schedule, but cannot create, change, or delete events.
- Files.Read.All — open OneDrive files, including files shared with you, when an agent needs document context. Read-only: agents can read your files but cannot modify, move, or delete them.
Alongside those, the connection uses a small set of standard identity scopes that handle sign-in and persistence:
- openid, profile, email — basic identity, so Microsoft knows who is connecting.
- offline_access — lets the connection refresh its own access token in the background, so your agent keeps working without asking you to re-authorize on every run.
That’s the entire list: nine scopes, each mapped to a specific capability your agents actually use.
What we deliberately don’t ask for
Just as important as what we request is what we leave out. BotTrottr’s Outlook connection does not request:
- Write access to your calendar. Agents can read your schedule, but cannot create, move, or delete events — so a busy agent can never send an invite to a colleague on your behalf.
- Write access to your files. Agents can open OneDrive documents for context, but cannot edit, move, or delete them.
- Write access to your profile — we only read it (
User.Read, neverUser.ReadWrite). - Your activity feed.
- Contacts, tasks, or any data beyond mail, calendar, and OneDrive files.
- Admin, directory, or tenant-level permissions.
The one capability we do enable that acts on your behalf is sending mail — and that’s a deliberate, narrow choice: an agent that drafts a reply needs to be able to deliver it. If you’d rather review before anything leaves your account, you can leave mail sending out of an agent’s toolset and have it deliver drafts to you instead.
If the consent screen ever shows a permission that isn’t in the list above, stop and check — it shouldn’t be there, and we’d want to know about it.
How the access stays scoped
The permission you grant is tied to a single Microsoft 365 connection, stored securely, and used only to run the Outlook tools your agents are configured for. There’s no standing admin access, no background access beyond what those scopes allow, and you can revoke the connection at any time from the MCP Credentials page — which invalidates the token immediately.
Your control, your data
Security on a consent screen is a two-way street. We hold the request to a minimum; you hold the final say. Read the list, grant only what you’re comfortable with, and remember you can disconnect whenever you like.
Questions about a specific permission, or ready to connect Outlook to your agents? Follow along via the RSS feed, and reach out any time.