How I Connected AI to My Company Outlook in 60 Minutes

Every BD manager in manufacturing lives in their inbox. Customer PO acknowledgements, delivery status requests, NCR escalations, price negotiation threads, supplier confirmations — the email volume is constant and the cost of a slow response is real. Missing a customer's delivery enquiry by four hours can mean a complaint. Missing a procurement team's price validity question can mean losing the order to the competitor who replied first.

The standard workflow is to check email manually, draft responses from scratch, and switch between Outlook and whatever tool you're using to pull information. It works. It's also slow, and it breaks down at volume. This case study documents a different approach: connecting Claude directly to a company Microsoft Outlook account using MCP — the Model Context Protocol — so that the AI can read emails, search specific threads, and draft or send replies from the terminal, without ever opening a browser tab.

The setup took sixty minutes. The mistakes made along the way, and the specific fixes for each of them, are documented here so that anyone replicating this on a company Outlook account doesn't have to rediscover them.

What MCP Is and Why It Matters Here

MCP stands for Model Context Protocol. It's the mechanism that lets an AI tool like Claude connect to external systems — email, calendars, files, databases — and interact with them in real time rather than just responding to text you paste into a chat window. Without MCP, you copy an email into Claude, get a reply drafted, and paste it back into Outlook. With MCP, Claude reads the email directly, drafts the response, and sends it — all from a single instruction.

For a BD manager handling thirty to fifty emails a day across multiple customer accounts, the difference is significant. The manual copy-paste workflow adds two to three minutes per email. At forty emails a day, that's over an hour of mechanical work that produces no thinking, no decision-making, and no relationship value. The MCP workflow compresses that to a fraction of the time and lets the BD manager focus on the emails that require judgement rather than the ones that just require a response.

The connection method used in this case study was the Microsoft Graph API — the official interface Microsoft provides for third-party applications to interact with Outlook, Teams, OneDrive, and other Microsoft 365 services. It requires an Azure app registration, which sounds more intimidating than it is. The actual registration process takes about fifteen minutes if you follow the steps below without guessing.

Step 1 — Register an Azure Application

Open the Azure portal at portal.azure.com and navigate to Azure Active Directory, then App Registrations, then New Registration. Name the application something recognisable — "Claude Outlook Connector" works. Set the account type to "Accounts in this organisational directory only" if you're working with a corporate Outlook account on a company tenant. If you're using a personal Microsoft account, choose the multi-tenant option instead.

For the redirect URI, enter http://localhost. This is used during the OAuth authentication flow and won't be a real web address — it's just where the authentication token gets redirected during the initial setup.

Once the app is registered, note the Application (client) ID and the Directory (tenant) ID from the overview page. You'll need both in the configuration step. Then navigate to Certificates & Secrets, create a new client secret, set the expiry to your preference, and copy the secret value immediately — it won't be shown again after you leave the page. This is the first gotcha most people hit: they navigate away before copying the secret, then have to regenerate it and start the configuration over.

Step 2 — Configure API Permissions

Navigate to API Permissions in the app registration and add the following Microsoft Graph permissions: Mail.Read, Mail.Send, Mail.ReadWrite, and User.Read. Set these as Delegated permissions, not Application permissions — delegated means the access operates on behalf of a signed-in user, which is the correct model for this use case.

If your company Outlook account is on a corporate tenant with admin-controlled permissions, you will need an administrator to grant consent for the application. This is the second gotcha. If the company's IT policy requires admin approval for new app registrations, the self-service setup path won't work without either getting IT to whitelist the app or registering it on a personal Microsoft account instead.

For most SEA manufacturing companies, the IT environment is either a managed Microsoft 365 tenant where admin consent is required, or a lighter setup where users have more latitude. If you're unsure which applies to your company, the permission configuration page will tell you — it will show a warning if admin consent is required and not yet granted.

Step 3 — Install and Configure the MCP Server

The MCP server for Microsoft Graph is an open-source package. Install it via npm with npm install -g @modelcontextprotocol/server-microsoft-graph. Once installed, create a configuration file — typically called mcp-config.json — in your home directory or a project folder. The file structure looks like this:

Replace the placeholder values with your actual client ID, client secret, and tenant ID from the Azure registration. Save the file, then point Claude's MCP configuration to this file path. The exact method depends on whether you're running Claude Desktop or the Claude CLI — in both cases, there is a settings interface where you specify the path to your MCP config.

Step 4 — Authenticate and Test

The first time you run Claude with the Outlook MCP server active, it will prompt for authentication. Open the URL it provides in a browser, sign in with your Microsoft account, and grant the permissions the app requests. You'll be redirected to localhost — the page won't load, but the URL bar will contain an authorisation code. Copy that code and paste it back into the terminal when prompted.

This is the third gotcha: the redirect URL needs to be copied exactly, including everything after the code= parameter. Some people copy only the short code and miss the trailing state parameter, which causes the authentication to fail silently. Copy the entire URL from localhost onwards.

Once authentication is complete, test the connection with a simple instruction: "List my five most recent emails from the past 24 hours." If the server is configured correctly, Claude will return a list of email subjects, senders, and timestamps pulled directly from your Outlook inbox. If it returns an error about insufficient permissions, return to the Azure portal and verify that all four API permissions are set to Delegated and that admin consent is granted if your tenant requires it.

What You Can Do Once It's Connected

The practical applications for a manufacturing BD manager are immediate. Search a specific customer's email thread: "Find all emails from procurement@customer.com in the last thirty days and summarise the open action items." Draft a reply to a delivery enquiry: "Read the latest email from [customer name] about the March shipment and draft a reply confirming dispatch with our standard OTD format." Send a follow-up: "Send a follow-up to the quotation email I sent on Tuesday, asking if they need any clarification on the unit price breakdown."

The key discipline is the same as with any AI tool: be specific about what you want. Vague instructions produce vague outputs. Specific instructions — with the customer name, the date range, the email subject, the desired tone — produce responses you can send with minimal editing.

One important boundary: review AI-drafted emails before sending, especially for anything with commercial implications. The AI will write a professional reply, but it doesn't know the relationship nuances that you carry from twelve months of account management. A reply that is technically correct but misses the tone of a sensitive negotiation thread can do more damage than a slow response. Use AI to draft; use your judgement to approve.

The Gotchas, Summarised

For anyone replicating this setup, the four issues most likely to add time are: copying the client secret before navigating away from the secrets page; corporate IT admin consent requirements blocking self-registration; copying the full redirect URL during authentication rather than just the code value; and mismatched permission types — delegated versus application — which causes silent failures that are hard to diagnose without knowing what to look for.

With those four addressed upfront, the setup runs cleanly. Sixty minutes is a realistic estimate for someone who hasn't done Azure app registrations before. For anyone who has, it's closer to twenty minutes. Either way, the productivity return starts on the same day.