Every BD manager in manufacturing lives in their inbox, full of customer PO acknowledgements, delivery status requests, and price negotiation threads. Missing a customer's delivery enquiry by four hours can mean a complaint, and missing a price validity question can mean losing the order to a faster competitor.

This case study documents connecting Claude directly to a company Microsoft Outlook account using MCP (Model Context Protocol). MCP lets AI act on external systems directly, so you don't copy text back and forth. The AI reads emails, drafts replies, and sends them from the terminal. Setup took sixty minutes.

I packaged this entire system. Build Your AI Back-Office: download it, and in your first sitting your agent builds a real document from your real files. The same team that drafts my work nightly, generalized for your business — or your clients'. USD 18.99 founding. And you are not left alone with a folder: every update free, step-by-step tutorials as they land, and me — the person who runs this exact system daily — one reply away when you're stuck.

See the kit →

Setting it up

Step 1: Register an Azure app

Go to portal.azure.com, open Azure Active Directory, then App Registrations, then New Registration. Name it, set the redirect URI to http://localhost, then note the Client ID and Tenant ID. Create a client secret under Certificates & Secrets and copy it immediately, because it won't be shown again.

Step 2: Set permissions

Add these Microsoft Graph permissions as Delegated: Mail.Read, Mail.Send, Mail.ReadWrite, User.Read. On a corporate tenant, an admin may need to approve the app before it works.

Step 3: Configure the MCP server

Install the Microsoft Graph MCP server, then create a config file with your credentials:

MCP Configuration File
{ "mcpServers": { "microsoft-graph": { "command": "npx", "args": ["@modelcontextprotocol/server-microsoft-graph"], "env": { "MICROSOFT_CLIENT_ID": "your-application-client-id", "MICROSOFT_CLIENT_SECRET": "your-client-secret-value", "MICROSOFT_TENANT_ID": "your-directory-tenant-id" } } } }

Point Claude's MCP settings to this file, and you're connected.

Step 4: Authenticate

The first run opens a browser sign-in. Copy the entire redirect URL after localhost, not just the short code, and paste it back into the terminal. Test with: "List my five most recent emails." If it returns real inbox data, it's working.

What you can do once connected

Ask it to summarise a customer's email thread, draft a reply confirming a shipment, or send a follow-up on a quote. Be specific: the customer name, date range, and tone you want. Always review AI-drafted emails before sending anything with commercial implications; the AI doesn't know the relationship nuance you've built over months.

The gotchas

Four things eat time: forgetting to copy the client secret before leaving the page, corporate IT blocking self-registration, copying only the short code instead of the full redirect URL, and mixing up Delegated versus Application permissions. Fix these upfront and the setup runs in about twenty minutes.

Outlook MCP Setup Checklist

  • Azure app registration complete: note client ID and tenant ID
  • Client secret created and copied immediately before navigating away
  • API permissions set: Mail.Read, Mail.Send, Mail.ReadWrite, User.Read (Delegated)
  • Admin consent granted if required by company tenant
  • MCP config file created with correct credentials
  • Authentication flow completed: full redirect URL copied during auth
  • Test query run successfully: email list returned from inbox