Skip to content

Microsoft Teams and Outlook

Integration · Workspace and scheduling

AI agents in Microsoft
Teams and Outlook

An agent reaches Outlook mail and calendars through Microsoft Graph, with an app registered in Microsoft Entra ID and permissions an admin approves. Scope application access to named mailboxes with Exchange RBAC for Applications. In Teams, an agent posts as a bot, because Graph does not let an app post normal channel messages as itself.

Delegated or application permissions?

Every Graph integration starts with an app registration in Microsoft Entra ID (formerly Azure AD), in your own tenant. The app then asks for permissions. Microsoft Graph has two kinds, and the choice decides how much the agent can reach.

Graph permission types (checked 19 Nov 2026)
TypeHow it worksConsentUse it for
DelegatedThe app acts for a signed-in user and can reach no more than that user can.User or admin, depending on the permission.An assistant that works for one person, such as drafting replies in their mailbox.
ApplicationThe app acts as itself, with no signed-in user. Without scoping, it can reach every mailbox in the tenant.Admin only.A background agent on a shared mailbox, such as info@ or accounts@.

Microsoft recommends delegated permissions whenever they meet the need. Common permissions for an agent are Mail.Read, Mail.Send, Calendars.ReadWrite and, in Teams, ChannelMessage.Send (delegated only). Ask for the smallest set, and for read-only versions where you can.

What can an agent do in Outlook?

  • Triage a shared inbox. Read new mail, classify it, file it and draft replies for a person to send. See email triage.
  • Send mail. Mail.Send exists as delegated and application permission. Many teams start with drafts only and add sending later.
  • Manage calendars. Read free and busy times, create events and send invitations with Calendars.ReadWrite.
  • React to new mail. Graph change notifications (webhooks) cover messages and events. An Outlook subscription lasts just under 7 days at most, or under 1 day if it includes the message data. The agent must renew subscriptions on a schedule.

Microsoft also sets a quota of 1,000 active subscriptions per mailbox across all apps. A small business will not reach it, but it explains why a well-built agent cleans up old subscriptions. Our Microsoft 365 page covers OneDrive, SharePoint and Excel.

How does an agent work inside Teams?

Teams is where most people expect to talk to an internal agent. There is one limit that surprises many projects: through Graph, the only application permission for posting channel or chat messages is Teamwork.Migrate.All, and Microsoft states it is for migration only. An app cannot post normal Teams messages as itself through Graph.

Ways to put an agent in Teams
RouteWhat it doesNotes
Teams bot (Microsoft 365 Agents SDK or Teams SDK)The agent appears as an app. People chat with it, and it can post into channels where it is installed.Microsoft has archived the Bot Framework SDK. Support tickets stopped on 31 December 2025. New bots use the Agents SDK or Teams SDK.
Graph with delegated permissionThe agent posts as a signed-in user.Suits a personal assistant. The messages appear as that person.
Change notifications for Teams messagesThe agent hears new messages in a channel or chat.Subscriptions last 3 days at most. Teams APIs have not been metered since 25 August 2025.
Copilot StudioA low-code agent published to Teams and Microsoft 365 Copilot.Billed in Copilot Credits. Good for questions over your documents.

A bot can send proactive messages, such as "your leave request is approved", only after the app is installed for that user or in that team or chat. An admin can install it for everyone with an app setup policy.

Before you connect Microsoft Teams and Outlook: a checklist.

Checklist

Connecting Microsoft Teams and Outlook safely

Copilot Studio or a custom agent?

Microsoft offers Copilot Studio as its no-code route. Since 1 September 2025, it is billed in Copilot Credits, through prepaid packs or pay-as-you-go via Azure.

  • Copilot Studio fits internal questions and answers, simple forms and approvals inside Microsoft 365.
  • A custom agent fits when it must work across systems outside Microsoft (WhatsApp, your CRM, a booking system), follow complex rules, or use a model you choose.
  • Both need the same care on permissions and data. A Copilot Studio agent can still reach more than you expect if its connectors are broad.

For the choice between platforms and custom builds, see chatbot platforms vs custom agent.

How do we set it up safely?

  1. Register the app in your own Entra ID tenant, so you own and can revoke it.
  2. List each action the agent needs, and map it to the smallest Graph permission.
  3. Use delegated permissions for personal assistants and application permissions only for shared mailboxes.
  4. Scope application access to named mailboxes with RBAC for Applications. Test it with Test-ServicePrincipalAuthorization. Changes can take 30 minutes to 2 hours to apply.
  5. Use a certificate, not a client secret, for application authentication, and store it in a key vault.
  6. Log every send and every calendar change the agent makes.

Mail holds personal data of staff, clients and suppliers. Record the agent as a processing activity and keep the model provider in the EU. See AI agent security and AI agents and GDPR.

Which mistakes do we see most often?

  • Tenant-wide mail access. An app with application Mail.Read and no scoping can read the CEO’s mailbox. Scope it.
  • Client secrets in code. Secrets leak and expire. Use certificates or managed identities, and rotate them.
  • Expired subscriptions. Change notifications expire after days. Without a renewal job, the agent goes quiet.
  • Posting as a person. Delegated sending makes the agent’s messages look like a staff member wrote them. Make it clear when an agent wrote a message.
  • Building on the old SDK. New Teams bots on the archived Bot Framework SDK will need to move later. Start on the Microsoft 365 Agents SDK or the Teams SDK.
  • No admin in the loop. The project stalls at consent. Bring your IT admin in at the start.

Common questions

Can an AI agent read only one shared mailbox?

Yes. Give the app the application permission it needs, then use Exchange Online RBAC for Applications to limit it to that mailbox. Remove any tenant-wide grant for the same permission in Entra ID, because the two add together. Microsoft says changes can take 30 minutes to 2 hours to take effect.

Can a bot post messages to a Teams channel?

Yes, as a Teams bot that is installed in that team. Through Microsoft Graph alone, an app cannot post normal channel messages as itself: the only application permission is for migration. New bots should use the Microsoft 365 Agents SDK or the Teams SDK, because the Bot Framework SDK is archived.

Do we need admin consent?

For application permissions, always: only an admin can grant them. For delegated permissions, it depends on the permission and your tenant settings. Many organisations require admin consent for all third-party apps. Plan a short review with your IT admin before the build starts.

Is Copilot Studio cheaper than a custom agent?

For simple internal questions over Microsoft 365 content, often yes, because you build it yourself and pay in Copilot Credits. A custom agent costs more to build but suits work across non-Microsoft systems. Compare the running cost for your own volume before you decide.

Sources

Bring us the task.

Tell us what happens today, which tools are involved and where it goes wrong. On a free 30-minute review, we’ll work out whether an agent, an automation or neither is the right fix, and what a sensible first release would be.

Start a project.

Two people on a sofa with laptops, planning a project beside a whiteboard of sticky notes

Book a call or send us a message. We read everything.

tash@neu.ie
Working with teams in Ireland and worldwide.

Get in touch

Free 30-minute AI review.