Outlook Email & Calendar

Access Microsoft 365 Outlook email and calendar via Microsoft Graph API.

CRITICAL: Replies preserve ALL original recipients (reply-all by default)

reply, mdreply, and followup use Microsoft Graph's createReplyAll endpoint. The new draft includes every To: and Cc: recipient from the original message — not just the sender.

Mandatory rules:

1. Always read the original message's full To: and Cc: lists BEFORE creating a reply. Use a direct API call if read truncates: curl … "/me/messages/<id>?$select=toRecipients,ccRecipients". Knowing who's on the thread is part of "reading the full body end-to-end" — do not skip it.
2. After creating any reply draft, confirm the displayed To:, Cc:, and Bcc: lines match what you intended. All three reply commands now print every recipient (not just To[0]). If the list looks short, the original might have had CCs you missed — re-check before sending.
3. If you genuinely want sender-only, create the reply, then run update to <sender-email> and update cc "" (or manually edit) to trim recipients. Default is "everyone stays in the loop".
4. Never assume a single-recipient To: means a single-recipient thread. Estate agents, solicitors, accountants, and courts routinely Cc colleagues, assistants, and audit addresses. Dropping those CCs on reply is a real harm — they stop seeing the conversation.

This rule exists because a previous reply silently dropped two CCs (assistant addresses on an estate-agent thread); the recipients had to be looped back in via a follow-up email. Reply-all is now the default to make recipient loss impossible by accident.

CRITICAL: Reading email content