Summary: ChatGPT’s April 8, 2026 release notes added support for delegated and shared Outlook mailboxes and calendars. The assistant can read and organize messages, send plain text on behalf of a mailbox, and create or update shared-calendar events. Existing Microsoft permissions, Entra admin approval, and workspace action controls remain required gates.
Buried in ChatGPT’s release notes for April 8, 2026 is a single brief line: the built-in Outlook Email and Outlook Calendar apps can now operate on delegated or shared Outlook resources. Barely a sentence — yet the implications run deep. For the first time, ChatGPT can work under a team identity: sorting through a support@ or info@ inbox on your behalf, or setting up and adjusting meetings straight on a shared calendar.
Casual users will file this under “one more connector option.” Product and IT teams should read it differently: an AI assistant has taken its first step out of the personal inbox and toward an organization’s shared assets. How OpenAI chose to ship it — permissions passed through untouched, write actions kept on a short leash — deserves close study from anyone building enterprise AI products.
What’s Actually in the Update
OpenAI’s documentation lays out the shared-mailbox abilities as follows: reading messages, browsing folders, toggling read and unread status, moving messages, and sending plain-text email “from” or “on behalf of” the mailbox. Shared calendars get their own set: ChatGPT can create, update, RSVP to, cancel, and delete events, and attach small files to them.
One rule of use is non-negotiable: every request must name the exact shared mailbox address or the calendar being targeted, because ChatGPT never guesses at the resource. Authorization involves no new account either — you link a Microsoft account that already holds access to the resource. A support lead whose account already opens support@ just connects it, and ChatGPT inherits precisely that existing grant.
How Permissions Work: Nothing New Gets Granted
One line in the documentation outweighs all the rest: “ChatGPT does not grant Microsoft sharing or delegation permissions.” Beneath the surface, the feature sits entirely on Microsoft Graph scopes that already exist — Mail.Read.Shared, Mail.ReadWrite.Shared, Mail.Send.Shared, Calendars.Read.Shared, Calendars.ReadWrite.Shared — and every one of them needs tenant-level approval from a Microsoft Entra administrator.
A second control layer lives on the ChatGPT side: workspace admins can switch read or write actions on and off per app, and when new actions ship they can pick “enable all new actions,” “enable only new read actions,” or “disable new actions.” The net effect: before any write action touches a shared mailbox, it must clear two gates held by two different admin roles — Entra’s permission grant and the workspace’s action toggle. Who signed off, and who answers for the consequences, stays easy to trace.
Shared Mailboxes: Why This One Matters
Few things sit closer to the ground floor of team collaboration than the shared mailbox: support, recruiting, finance, and PR all depend on them. Once an assistant can read, tidy up, and answer “on behalf of” an address many people share, it has been woven into the organization’s identity and workflow rather than bolted onto a single user’s account.
Step back and OpenAI’s apps strategy comes into focus: personal read access came first, personal write actions followed, shared resources arrive now — and cross-app agentic workflows are the evident next destination. The caution around writes is equally deliberate: sends are restricted to plain text, event attachments stay limited to small files, and attachments inside shared mailboxes are out of reach entirely (attachment fetch actions work only on the signed-in user’s own mailbox). Choosing to stage a capability you already hold is, in itself, a product statement.
Constraints and Rollout Realities
- Whether the feature works at all hinges on Microsoft permissions and workspace app settings; admins can go further and allow connections only from Outlook accounts on approved domains.
- Wide-reaching search or summarization requests can come back with gaps; OpenAI’s advice is to narrow date ranges and run searches in batches using more specific sender or subject terms.
- Inside enterprise IT, the Entra admin and the ChatGPT workspace admin are usually two different people. Whether org-level consent and ownership are settled before rollout is what separates a “read-only” deployment from a genuinely useful one.
The Takeaways for Product Teams
One: permission passthrough is the least expensive route to enterprise acceptance for an AI assistant — build no authorization system of your own, lean on Microsoft’s existing delegation and sharing machinery, and IT’s audit load stays close to zero. Two: the phased widening of write actions — plain text first, attachments afterward, shared-mailbox attachment reads never — offers a tidy template for ordering “useful” against “controllable.” Three: the moment ChatGPT acts under shared identities, the risk tier moves up a level — workspace-level action toggles and domain allowlists are headed toward baseline requirements for this product category, not nice-to-haves.