On April 8, 2026, a short entry appeared in ChatGPT’s release notes: the Outlook Email and Outlook Calendar apps built into ChatGPT can now work with delegated or shared Outlook resources. The sentence is small; the signal is not. For the first time, ChatGPT can act under a team identity — triaging a support@ or info@ mailbox on your behalf and creating or editing meetings directly on a shared calendar.
To a casual user this looks like one more connector checkbox. To product and IT teams, it is the first step of an AI assistant moving from the personal inbox into shared organizational assets. And the way OpenAI shipped it — permissions fully passed through, write actions tightly scoped — is worth a close read from anyone building enterprise AI products.
What the Update Actually Ships
Per OpenAI’s documentation, the shared-mailbox capabilities are: read messages, browse folders, mark mail as read or unread, move messages, and send plain-text email “from” or “on behalf of” the mailbox. On shared calendars, ChatGPT can create, update, RSVP to, cancel, and delete events, and attach small files to events.
One requirement is explicit: when you make a request, you have to name the exact shared mailbox address or target calendar. ChatGPT will not guess which resource you mean. Authorization is not a new account, either — you connect a Microsoft account that already has access to the resource. If a support lead’s account can already open support@, connecting it lets ChatGPT ride on exactly that grant.
The Permission Model: ChatGPT Grants Nothing New
The most consequential sentence in the documentation is this one: “ChatGPT does not grant Microsoft sharing or delegation permissions.” Under the hood, the feature runs on existing Microsoft Graph scopes — Mail.Read.Shared, Mail.ReadWrite.Shared, Mail.Send.Shared, Calendars.Read.Shared, Calendars.ReadWrite.Shared — each of which must be tenant-approved by a Microsoft Entra administrator.
There is a second layer on the ChatGPT side: workspace admins can enable read or write actions per app, and when new actions ship they can choose “enable all new actions,” “enable only new read actions,” or “disable new actions.” Put together, a write action against a shared mailbox has to clear two gates owned by two different admin roles — Entra’s permission grant and the workspace’s action toggle. Who approved what, and who owns the blast radius, stays legible.
Why Shared Mailboxes Are the Signal
The shared mailbox is the smallest unit of team collaboration: support, recruiting, finance, and PR all run on them. An assistant that can read, tidy, and reply “on behalf of” an address that many people share has been inserted into an organization’s identity and workflow, not just bolted onto one user’s account.
Zoom out and OpenAI’s apps strategy reads clearly: read access on personal accounts first, then personal write actions, now shared resources — with cross-app agentic workflows the obvious next stop. The restraint on writes is just as deliberate: sends are plain-text only, event attachments are limited to small files, and attachments inside shared mailboxes cannot be retrieved at all (attachment fetch actions only work on the signed-in user’s own mailbox). Having the capability and choosing to stage it is itself a product statement.
Limits and Rollout Reality
- Availability depends on Microsoft permissions and workspace app settings; admins can additionally restrict connections to Outlook accounts from approved domains only.
- Broad search or summarization requests may return incomplete results; OpenAI recommends narrowing date ranges and batching searches with more specific sender or subject terms.
- For enterprise IT, the Entra admin and the ChatGPT workspace admin are usually different people. Sorting out the org-level consent process and ownership before rollout decides whether this lands as “read-only” or actually useful.
What It Means for Product Teams
First, permission passthrough is the cheapest path to enterprise acceptance for an AI assistant: don’t invent an authorization system, reuse Microsoft’s existing delegation and sharing machinery, and keep the audit burden on IT near zero. Second, the staged expansion of write actions — plain text first, attachments later, shared-mailbox attachment reads not at all — is a clean template for sequencing “useful” against “controllable.” Third, once ChatGPT acts on shared identities, the risk profile jumps a tier: workspace-level action toggles and domain allowlists are about to become table stakes for this product category, not a bonus.
Sources
- ChatGPT — Release Notes — OpenAI Help Center
- Outlook Email and Calendar apps in ChatGPT — OpenAI Help Center
- April 8, 2026 — Outlook shared mailboxes and calendars in ChatGPT — Reconn AI
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.