Claude Can Now Send Your Email and Book Your Meetings: What Microsoft 365 Write Tools Mean for Your Team

TL;DR

Anthropic just flipped an important switch on the Microsoft 365 connector — the link that lets Claude reach into your company's Outlook, Calendar, OneDrive, and SharePoint. Until now that connection was read-only: Claude could look through your email and files and tell you things, but it couldn't touch anything. The new write tools change that. With them turned on, Claude can draft and send emails, create and move calendar events, tidy your inbox, and create and update files directly in OneDrive and SharePoint — the actual documents your team works in every day. In plain terms, Claude went from “an assistant that reads your Microsoft 365 and reports back” to “an assistant that does things in your Microsoft 365 for you.” Crucially, it's off by default — an admin has to deliberately enable it — every email Claude sends carries a header saying it came from an AI agent, and there are per-user limits. Here's what changed, why the read-to-write jump is a much bigger deal than it sounds, and exactly what your non-technical team should do about it this week.

First, What the Microsoft 365 Connector Actually Is

A connector is the secure bridge that lets Claude see and use one of your business tools without you copying things back and forth by hand.

If your company runs on Microsoft — Outlook for email, the Microsoft calendar, OneDrive and SharePoint for files, Teams for chat — the Microsoft 365 connector is what plugs Claude into all of that under your own login. Once it's connected, you can ask Claude things like “find the contract we signed with Nordwind last spring” or “summarize the email thread with the finance team about the Q2 budget,” and it goes and looks, using your existing permissions, instead of you hunting through folders and pasting text into a chat box.

That was already useful. But notice the shape of it: everything was inbound. Claude could read, search, and summarize. It could tell you what your email said and where a file lived. What it couldn't do was act — it couldn't hit send, book the meeting, or save the document. You still did all the actual doing yourself. That's the wall the write tools just removed.

What Actually Changed

Claude can now take actions inside Microsoft 365, not just read from it — but only if an admin deliberately turns that on.

When an organization enables write tools on the connector, Claude gains the ability to do things instead of just look at things. Concretely, that means:

Email. Draft, send, and organize email in Outlook — write a reply and put it in your drafts, or send it, or move and file messages to clean up your inbox.
Calendar. Create, update, and delete calendar events — book a meeting, move one, cancel one — and adjust some mailbox settings.
Files. Create and update files directly in OneDrive and SharePoint — so a document Claude produces lands where your team already keeps its work, rather than as text you have to copy out and save yourself.

The difference in day-to-day feel is large. Before, you'd ask Claude to draft a client update, then copy its answer, open Outlook, paste it in, address it, and send. Now you can say “draft a reply to Anna confirming Thursday and put it in my drafts,” and it's sitting in Outlook waiting for you to glance at and send. The gap between “Claude produced something” and “the thing is actually in my system” closes.

Why Going From “Read” to “Write” Is the Whole Story

Reading saves you looking things up. Writing saves you doing the work. Those are different sizes of help.

It's easy to underrate this because “send an email” sounds trivial. But think about where your team's time actually goes. It's rarely the thinking — it's the handling. Retyping the same confirmation for the fifth time. Copying a summary out of one tool and into another. Booking the follow-up. Filing the document in the right SharePoint folder so someone else can find it. This is the connective tissue of a working day, and it's almost entirely mechanical.

A read-only assistant can't touch any of that. It can hand you a perfect draft, but you still have to walk it the last hundred meters into your inbox. And that last hundred meters — the copying, pasting, addressing, sending, filing — is often most of the actual effort. Write tools mean Claude walks it for you. That's the shift from “this tool makes me faster at doing my work” to “this tool does a chunk of my work.”

The intelligence didn't change here. Claude was already good at writing a follow-up email. What changed is whether it can put that email where it needs to go. For a lot of everyday tasks, that last step was the whole friction.

A Plain-Language Analogy

The old connector was a research assistant who could read every file in the office but wasn't allowed to touch the keyboard. The new one can type.

Picture an assistant you've given a reading pass to the office. They can go through any folder, read any email thread, and come back and tell you exactly what's in there and what they'd suggest. Genuinely helpful — but if you want the reply actually sent or the meeting actually booked, you have to sit down and do it yourself, because they're only allowed to look.

Write tools hand that same assistant a keyboard and a calendar. Now when they say “here's the reply I'd send,” they can also put it in your drafts, or book the meeting you agreed to, or save the updated document back to the shared drive. Same competence, same access to information — but now they can finish the job instead of stopping at the recommendation.

And, importantly, this analogy includes the guardrails: a good assistant drafts rather than fires things off blindly, signs their work so everyone knows who wrote it, and doesn't get the keys until you deliberately hand them over. That's exactly how Anthropic set this up, which is the next thing worth understanding.

The Safety Design, in Plain Terms

Anthropic built this so that “AI that can send email on your behalf” doesn't become “AI that sends email you didn't want.”

Letting an AI take actions in your live email and calendar is exactly the kind of thing a cautious team should ask hard questions about. Anthropic anticipated that, and the design answers the obvious worries:

Off by default. Write tools aren't automatically on. An administrator has to go into Organization settings and deliberately enable them. If your company was already using the connector before this launched, write access stays blocked until someone consciously turns it on. Nothing changes under your feet.
Every sent email is labeled as agent-initiated. When Claude sends an email, it includes an attribution header identifying it as coming from an AI agent. Recipients — and your own systems — can tell the difference between something a person wrote and something Claude sent. No pretending to be human.
Per-user limits. There are caps on how much a single user's write tools can do, which puts a natural ceiling on any single mistake.
It works inside your existing permissions. Claude can only touch what your Microsoft login already lets you touch. It doesn't get some special master key to the whole company.

One honest limitation to know: attachments aren't supported yet. Claude can't send, forward, or draft emails with files attached through the connector. So the “send the signed PDF to the client” job still needs a human for now. That's a real boundary, and it's worth knowing before you assume it can do everything.

How This Is Different From the Claude Add-Ins for Office

This is Claude acting across your Microsoft 365 — your inbox, calendar, and shared files. The Office add-ins are Claude working inside a single document you already have open.

We've written before about Claude add-ins for Microsoft 365 — Claude appearing inside Excel, PowerPoint, and Word to help with the spreadsheet or deck you're building right now. That's useful, but it's scoped to the document in front of you.

The connector with write tools is a different surface. It's not about one file you're editing — it's about the whole flow of your Microsoft world: reading the email thread, drafting the reply, booking the follow-up meeting, saving the resulting document to SharePoint. One is a smart helper inside a document; the other is an assistant moving between your email, calendar, and file storage on your behalf. Most teams will want both, but they solve different problems, and it's worth not confusing them.

What This Looks Like for a Non-Technical Team

The payoff shows up in the small, repetitive Microsoft-shaped chores that quietly eat everyone's day.

A few realistic examples of what write tools make genuinely easier:

Inbox triage that ends in drafts, not just a summary. “Go through this morning's email, and for anything that needs a reply, draft one and leave it in my drafts.” You open Outlook to a set of ready replies to skim and send, instead of a to-do list.
Booking the meeting you just agreed to. After a thread lands on “Thursday at 2 works,” you say “book that with Anna and put the agenda in the invite,” and the calendar event appears — instead of you switching apps to create it.
The document that lands in the right folder. “Turn these notes into a one-page project brief and save it to the Marketing SharePoint.” It's created where your team already looks, not stuck as text in a chat you have to copy out.
End-of-week cleanup. “File all the newsletters into the Reading folder and flag anything from a client I haven't replied to.” A tidy inbox without you dragging messages around one at a time.
Meeting follow-ups that actually go out. Hand Claude the notes from a call and ask it to draft the follow-up email to each attendee. You review the drafts and send — the follow-up that usually slips through the cracks gets done.

None of these are exotic. They're the ordinary email-calendar-files admin that surrounds real work — the stuff that's easy to let pile up and expensive to let pile up. Closing the gap between “Claude wrote it” and “it's in my system” is exactly what turns that pile from a chore into a review-and-approve.

The Sensible Way to Start

Begin with drafting, not sending — and expand as your trust grows, the way you'd onboard a new hire.

The smart first posture is to let Claude draft rather than send. Ask it to prepare replies in your drafts folder, not fire them off. That gives you the time savings — you're not writing from scratch — while you stay the final set of eyes on everything that leaves your name. You get to see how good its judgment is before you widen the leash.

The same goes for files and calendar: start with low-stakes, easily-reversible actions. Have it save a draft document, book an internal meeting, file some newsletters. Watch how it behaves. Once you've seen it get the small things right a dozen times, you naturally know which bigger things you're comfortable handing over. That's how trust with any capable new colleague works, and it's exactly the right instinct here.

What Your Team Should Do This Week

You don't need a rollout plan. You need your admin to make a decision, and one person to try the “draft, don't send” workflow.

1. Have your admin decide on write tools deliberately

Because write tools are off by default, someone with admin rights has to consciously enable them in Organization settings. Make that a real decision, not an accident — discuss what you want Claude to be able to do, whether you're comfortable with sending versus drafting, and turn it on with intent. The default-off design is a feature: use it to have the conversation rather than skip it.

2. Try the “draft, don't send” inbox workflow

Once it's on, pick one person to spend a week having Claude draft email replies into their Outlook drafts each morning. The test is simple: are the drafts good enough that you're mostly skimming and sending, rather than rewriting? That single habit is where most of the everyday time savings live.

3. Book one meeting and save one file through Claude

Deliberately do two small actions the new way: ask Claude to book an internal meeting on your calendar, and ask it to save a document to a SharePoint folder. The point is to feel the difference between “Claude told me what to do” and “Claude did it,” so you build an accurate sense of what it's reliable at.

4. Note the boundaries so you don't get surprised

Remember two things: attachments aren't supported yet, so anything involving sending a file stays manual for now; and every email Claude sends is labeled as agent-sent, which is a good thing but worth telling your team so nobody's confused when they see the header. Knowing the edges up front keeps the experience positive.

FAQ

What is the Microsoft 365 connector in one sentence?

It's the secure bridge that lets Claude reach into your company's Outlook, Calendar, OneDrive, and SharePoint under your own login — and, with write tools enabled, take actions there like drafting and sending email, managing calendar events, and creating and updating files, not just reading and summarizing.

What's actually new — didn't the connector already exist?

The connector existed, but it was read-only: Claude could search and summarize your email and files but couldn't change anything. The new part is write tools, which let Claude take actions — send and organize email, create and update calendar events, and create and update files in OneDrive and SharePoint. It moves Claude from reporting on your Microsoft 365 to doing things in it.

Will Claude start sending emails on its own now?

No. Write tools are off by default and must be deliberately enabled by an admin. Even once on, the sensible practice is to have Claude draft into your drafts folder rather than auto-send, so a person stays the final check. And every email Claude does send carries a header identifying it as coming from an AI agent, so there's no ambiguity about what was human-written and what wasn't.

How is this different from Claude inside Excel, Word, and PowerPoint?

Those Office add-ins are Claude working inside a single document you have open — the spreadsheet or deck in front of you. The connector with write tools is Claude acting across your Microsoft world: your inbox, your calendar, and your shared files. One helps you build a document; the other moves between email, calendar, and file storage to get a whole task done. Most teams will use both.

Can Claude send emails with attachments?

Not yet. Attachments aren't supported in write tools — Claude can't send, forward, or draft emails with files attached through the connector. So any task that needs a file attached still needs a person to do that part for now.

Is our data safe if we turn this on?

Claude only gets the access your own Microsoft login already has — it can't touch anything you couldn't touch yourself. Write tools are off until an admin enables them, sent emails are labeled as agent-initiated, and there are per-user limits on how much the write tools can do. As with any new capability, start on low-stakes, easily-reversible actions and expand as your confidence grows.

Which plans have this?

The Microsoft 365 connector is available across Claude plans, including Free, Pro, Max, Team, and Enterprise. Write tools specifically need to be enabled by an admin in Organization settings — and if your organization was already using the connector before write tools launched, they stay blocked until someone turns them on.

What's the one thing to take away?

That Claude just crossed from “reads your Microsoft 365 and tells you things” to “does things in your Microsoft 365 for you” — the last mechanical hundred meters of drafting, booking, filing, and sending that usually ate your time. Turn it on deliberately, start with “draft, don't send,” and you'll feel the difference in a day.

Want help deciding whether to enable Microsoft 365 write tools, and setting up the “draft, don't send” workflows so your team gets the time savings without the risk? The Deployed Kickstart gets your team hands-on with Claude in a single day, mapped to your real workflows. The Partner program gives you ongoing support to roll it out safely across the business.