Use cases by system26 use cases

AI agents for Outlook and Microsoft 365, with or without Copilot

In most European mid-sized companies the work arrives in Exchange Online: customer orders in orders@, supplier invoices in invoices@, RFQs, delivery confirmations and tender documents in shared mailboxes that three people watch. 'ai agent for outlook' returns a full autocomplete list, the German 'ki agent für outlook' shows up too, and the questions behind them are about acting on email, not writing it.

Microsoft's own route is strong. Copilot Studio supports MCP tools, Microsoft publishes official Work IQ MCP servers for Teams, SharePoint and OneDrive, Calendar, Word and Copilot search, and computer use became generally available in May 2026 at 5 Copilot Credits per step. The catch is licensing: Microsoft 365 Copilot is priced per user per month, which works for office staff and falls apart for forty warehouse workers, drivers or external customers.

So most builds here run on Microsoft Graph with one app registration: order entry from email and PDF, supplier invoice processing, a company knowledge assistant over SharePoint and, where a system has no API at all, automation with a person approving the last click.

What to build around Outlook and Microsoft 365

Building on Microsoft Graph, and what your admin will ask

  • Change notifications, plus a safety net

    Graph pushes a notification when mail arrives, but subscriptions expire within days and a missed notification is silent. A delta query sweeps each folder on a schedule, so nothing depends on every push arriving.

  • Limit the app to the mailboxes it needs

    Application permissions such as Mail.Read cover every mailbox in the tenant by default. Exchange Online lets the admin restrict the app to named mailboxes, with application access policies or RBAC for Applications, and I set that up before the first test.

  • Throttling is per app and per mailbox

    Graph throttles each app against each mailbox, so a backfill of two years of orders@ runs slowly in the background while live mail keeps priority. Every call honors Retry-After instead of retrying blindly.

  • Shared mailboxes are the natural home

    A shared mailbox needs no license of its own, keeps its history when staff change, and is where the team already works. The agent files, categorizes and drafts there, so people see its work in Outlook.

  • Teams for the human step

    Approvals and exceptions go to Teams as Adaptive Cards with approve, edit and reject. The decision is written back to the system of record together with who made it and when.

Copilot or custom: who the users are decides it

  • Copilot for people who live in Outlook

    If the need is summarizing threads and drafting replies for office staff, license Copilot and stop there. A custom build makes sense only where the per-person model does not fit the work.

  • Copilot Studio when IT will own it

    A Microsoft-first company with an internal team can build agents in Copilot Studio that call MCP servers, and use computer use for desktop apps without APIs. I would rather support that team than replace it.

  • Frontline and external users break per-seat pricing

    Licensing every picker, driver or customer to ask a few questions a week rarely adds up. A custom app uses one app registration and pays per use, and customers never need a Microsoft account.

  • Pipelines are not chats

    An order email becoming a sales order in SAP Business One or NetSuite needs validation, idempotent creation and a review queue. That is a pipeline with a model in one step, not an assistant someone has to prompt.

Frequently asked questions

Can I build an AI agent for Outlook without Copilot licenses?

Yes. The agent is an Entra ID app registration with Graph permissions, restricted to the mailboxes it needs, and does not require Copilot seats for the people whose mail it processes. Staff see its work in Outlook as categories, folders and drafts. Copilot stays useful for individual drafting, and the two do not conflict.

Should we use Copilot Studio or a custom-built agent?

Use Copilot Studio if your company is Microsoft-first, the users already have licenses, and someone in IT will own the agent. Choose a custom build when the users are frontline staff or customers, when the workflow spans non-Microsoft systems such as your ERP or TMS, or when you need deterministic validation, tests and version control around the model.

Can Claude or ChatGPT connect to Outlook?

Yes, both connect to Microsoft 365 for individual users, and Claude's connector directory lists Microsoft 365. For a shared mailbox or a company process I would rather expose a scoped MCP server or build a Graph integration with its own permissions and audit log, so the assistant sees only what the process needs and every action is recorded.

How do I automate order emails from Outlook into our ERP?

Subscribe to the shared mailbox through Graph, pull the body and any PDF or Excel attachment, and hand the extracted lines to code that checks items, prices and duplicates against the ERP. The email gets an Outlook category such as Entered or Needs review, the confirmation is drafted as a reply in the same thread, and anything uncertain waits for a person.

Also browse: Operations and logistics · Document processing · SAP Business One · Gmail and Google Workspace · all use cases