Claude Can Now Send Emails and Manage Your Calendar via Microsoft 365

Introduction

For months, Claude's Microsoft 365 connector let you search emails, browse SharePoint documents, and review calendar events. It was useful, but it was strictly read-only. You could ask Claude to find information, but any action — replying to an email, scheduling a meeting, uploading a file — still required you to switch over to Outlook or Teams and do it yourself.

That changed on July 7, 2026. Anthropic flipped the connector from read-only to read-write, and the implications are significant. Claude can now draft and send emails from your account, create and update calendar events, and manage files in OneDrive and SharePoint. This is Claude stepping from research assistant into executive assistant territory.

This guide covers what the write tools actually do, how they work under the hood, the safety guardrails Anthropic built in, and how to get the most out of them without accidentally emailing your entire company at 2 AM.

What Changed: From Read-Only to Read-Write

The Microsoft 365 connector has been available across all Claude plans — Free, Pro, Max, Team, and Enterprise — for several months. Until now, it gave Claude the ability to search and retrieve content from four Microsoft services: SharePoint, OneDrive, Outlook, and Teams.

The July 7 update adds write capabilities to three of those four services. Here is what Claude can now do beyond searching and reading.

Email (Outlook)

Claude can draft emails, send them directly from your account, organize your inbox with categories, set up inbox rules, and configure automatic replies. When you ask Claude to send an email, it composes the message based on your instructions and sends it through your Microsoft 365 account. The recipient sees the email as coming from you, with one important distinction: a message header is added identifying the email as agent-initiated.

This means you can say things like "Draft a follow-up to the vendor about the delayed shipment and send it" or "Set up an out-of-office reply for next week" and Claude handles the entire workflow without you opening Outlook.

Calendar (Outlook)

Claude can create new calendar events, update existing ones, and delete events. You can ask Claude to schedule meetings, move appointments, or clear your afternoon — and it executes directly against your Outlook calendar.

Practical examples include "Schedule a 30-minute design review with the frontend team next Tuesday at 2 PM" or "Move my 1-on-1 with Sarah from Thursday to Friday same time." Claude handles the calendar API calls and confirms the changes.

Files (OneDrive and SharePoint)

Claude can create new files and update existing ones in both OneDrive and SharePoint. This is particularly useful for workflows where Claude analyzes data or drafts documents and you want the output saved directly to your company's file system rather than downloading it separately.

What Stays Read-Only

Teams remains read-only. Claude can search and read Teams messages and channel discussions you have access to, but it cannot post messages, reply to conversations, or change any Teams settings. Anthropic has drawn a clear line here — for now, Claude observes Teams but does not participate in it.

Safety and Attribution: How Anthropic Handles Trust

Giving an AI agent write access to someone's email account is a move that demands robust safety measures. Anthropic has built several layers of control into this update.

Agent Attribution Headers

Every email Claude sends includes a message header that identifies it as agent-initiated. This means that while the email appears to come from your address — because it does — there is metadata in the message indicating that an AI agent composed and sent it. This is a transparency measure. Recipients with email clients or IT systems that inspect headers can identify AI-generated correspondence.

It is worth noting that calendar and file writes do not currently carry this attribution tag. Anthropic has acknowledged this asymmetry, and it is likely something that will be addressed in future updates.

Admin-Controlled Enablement

Write tools are not enabled by default. If your organization was already using the Microsoft 365 connector before this update, write capabilities are blocked until an administrator explicitly enables them. This is a deliberate opt-in design.

For Team and Enterprise plans, the Claude organization Owner enables write tools through Organization Settings, then navigates to Connectors, and adjusts the Microsoft 365 permissions. A Microsoft Entra administrator also needs to grant consent for the updated permissions. This two-step process — Claude admin plus Microsoft admin — prevents any single person from unilaterally giving Claude write access to the organization's email and calendar.

Delegated Permissions Model

The connector uses delegated permissions, which means Claude acts on behalf of each individual user and can only access data that the user already has permission to interact with in Microsoft 365. If you cannot access a particular SharePoint site or shared mailbox in Outlook, Claude cannot access it either. There is no privilege escalation.

Per-User Rate Limits

Write tools are subject to per-user limits. Anthropic has not published the exact numbers, but the rate limiting prevents scenarios where a misconfigured prompt or an overly enthusiastic automation loop floods an inbox or creates hundreds of calendar events.

No Attachment Support

Claude cannot send, forward, or draft emails with attachments. This is both a current limitation and an implicit safety boundary. It prevents scenarios where Claude might attach sensitive documents to outgoing emails. If you ask Claude to send an email with an attachment, it will decline and explain the limitation.

Setting Up Write Tools: A Step-by-Step Walkthrough

Getting write tools working requires action from both an administrator and the individual user. Here is the process broken down.

For Administrators

First, a Microsoft Entra Global Administrator needs to grant updated permissions for the Claude Microsoft 365 integration. This is a one-time consent that covers the new write scopes — mail send, calendar read-write, and file read-write.

Second, on Team and Enterprise plans, the Claude organization Owner needs to enable write tools. Navigate to Organization Settings, find the Connectors section, locate Microsoft 365, and toggle write permissions on. You can enable write tools for the entire organization or keep them disabled and let individual teams decide.

For Individual Users

Once admin setup is complete, individual users connect through Claude's Customize menu. Go to Customize, then Connectors, find Microsoft 365, and click Connect. Sign in with your Microsoft 365 work credentials. Personal Microsoft accounts — Outlook.com, Hotmail, Live.com — are not supported.

After connecting, you can selectively toggle individual tools on or off. If you want Claude to manage your calendar but not touch your email, you can disable the email write tools while keeping calendar write tools active. This granularity is available under the Tool Permissions section of the Microsoft 365 connector settings.

You can also enable or disable the connector on a per-conversation basis. Click the plus button in the lower-left corner of the chat window, hover over Connectors, and toggle Microsoft 365 on or off for that specific chat.

Real-World Use Cases That Actually Make Sense

Having write access to email and calendar opens up workflows that were previously impossible without leaving the Claude interface. Here are scenarios where the integration genuinely saves time.

End-to-End Email Workflows

Before this update, a common workflow was: ask Claude to find an email thread, ask Claude to draft a reply, copy the draft, switch to Outlook, paste it, and send. Now the entire flow happens inside Claude. You say "Find the latest email from the procurement team about the hardware order and reply confirming we approve the revised quote." Claude searches, finds the thread, composes the reply, and sends it.

Meeting Scheduling With Context

Claude can now combine its ability to read your calendar with its ability to write to it. Ask "Find a free 45-minute slot next week that works around my existing meetings and schedule a project kickoff with the engineering leads" and Claude reads your calendar, identifies gaps, creates the event, and adds the attendees.

Inbox Management and Triage

You can ask Claude to set up inbox rules, categorize messages, or configure automatic replies. For example, "Set up an auto-reply for next Monday through Wednesday saying I am at a conference and will respond when I return." Claude configures the automatic reply directly in Outlook.

Document Creation Pipelines

If Claude helps you draft a report or analysis, you can now have it saved directly to a specific SharePoint site or OneDrive folder. Instead of downloading a file and uploading it manually, you say "Save this quarterly summary to the Finance team's SharePoint site in the Q3 Reports folder." Claude creates the file in place.

Cross-Service Workflows

The real power emerges when you chain read and write across services. "Search SharePoint for the latest project status update, summarize the key risks, draft an email to the steering committee with those risks highlighted, and schedule a 30-minute review meeting for Friday afternoon." Claude reads from SharePoint, writes an email, and creates a calendar event — all in one conversation turn.

Common Mistakes and What to Avoid

Write tools are powerful, but they also introduce new categories of mistakes. Here are the pitfalls to watch for.

Not Reviewing Before Sending

Claude will ask for confirmation before sending emails in most cases, but you should still review the content carefully. AI-generated emails can occasionally include incorrect details, overly formal language that does not match your communication style, or assumptions about context that are wrong. Treat Claude's draft as a draft, not a final product.

Overloading a Single Prompt

Asking Claude to "send emails to all 50 vendors confirming their contracts" in a single prompt is a recipe for problems. If one detail is wrong, it propagates across all 50 emails. Break bulk operations into smaller batches and verify the first few before continuing.

Ignoring the Attachment Limitation

If your workflow depends on sending documents as attachments, the write tools will not cover it. Plan for this limitation rather than discovering it mid-workflow. You can have Claude create the document in SharePoint and then send an email with a link to it instead.

Forgetting Per-Conversation Toggles

If you are having a sensitive conversation and do not want Claude to accidentally trigger a write action, disable the connector for that conversation. The per-chat toggle exists precisely for this reason.

Not Coordinating Admin Setup

The most common frustration is users trying to use write tools before their admin has completed both the Microsoft Entra consent and the Claude organization enablement. If write tools are not appearing, it is almost always an admin configuration issue, not a bug.

What This Means for the Broader AI Assistant Landscape

Claude's move to read-write Microsoft 365 integration is part of a larger trend. AI assistants are transitioning from information retrieval tools to action-taking agents. The distinction matters because it changes the trust model. When an AI can only read, the worst case is a privacy concern — it saw something it should not have. When an AI can write, the worst case is an action that cannot be undone — an email sent to the wrong person, a meeting deleted, a file overwritten.

Anthropic's approach — admin-gated opt-in, delegated permissions, agent attribution headers, no attachments — reflects a careful philosophy. They are shipping capability while maintaining control surfaces at every level. Compare this to the broader market where some AI tools request full access with minimal guardrails, and Anthropic's measured approach stands out.

The fact that Teams remains read-only is also telling. Messaging is more immediate and less forgiving than email. An errant email can be followed up with a correction. An errant message in a busy Teams channel gets read by dozens of people instantly. Anthropic appears to be rolling out write access service by service, starting with the ones where mistakes are most recoverable.

Conclusion

The Microsoft 365 write tools update is one of the most practically useful changes to Claude in recent months. It eliminates the constant context-switching between Claude and Outlook that defined previous workflows. For teams and individuals already embedded in the Microsoft ecosystem, this turns Claude from a smart search engine into a genuine productivity partner that can act on your behalf.

The key is treating it as a tool that requires oversight, not a fully autonomous agent. Review emails before they send. Start with simple tasks and build complexity as you develop trust in the system. Use the granular permission controls to limit scope until you are comfortable.

If you are a power user juggling Claude and Microsoft 365 daily, tools like Gaugr can help you track your Claude usage across models and make sure you are getting the most out of your plan while these new capabilities ramp up.