Articles
How to automate an Outlook shared mailbox

Written by Roberto Postolovski, Founder & Tech LeadUpdated
Shared mailbox basics
A shared mailbox is the natural home for team addresses like orders@, invoices@ or support@. Microsoft documents that a shared mailbox can store up to 50 GB without its own license, while every person who accesses it needs a licensed Exchange Online mailbox.
That makes shared mailboxes cheap to run and, often, the place where work piles up, because everyone can see an email and nobody is sure who owns it.
Power Automate or Microsoft Graph?
Power Automate's Office 365 Outlook connector is the quickest start, and for simple flows it's enough. For a team mailbox that carries real work, Microsoft's own list of known limitations matters:
- If many emails arrive at once, the trigger can miss some. Microsoft notes this is rare
- In rare cases the trigger can take up to an hour to fire
- Item attachments (emails or invites attached to an email, including bounce messages) aren't supported
- The trigger can run twice for one email, the first time with an empty attachments array
- A Microsoft 365 group address can't be used as a shared mailbox address
- The connector allows 300 API calls per connection every 60 seconds
Scope the app to one mailbox
Application permissions such as Mail.Read or Mail.ReadWrite apply to every mailbox in the organisation unless you restrict them. Exchange Online's RBAC for Applications lets an administrator pair the permission with a resource scope, so the app can only reach the mailboxes it's meant to. It replaces the older Application Access Policies.
For a shared-mailbox automation this is the single most important security step: if the app's credentials were ever exposed, the damage is limited to that mailbox.
Listen for new mail
Create a Microsoft Graph change-notification subscription on the mailbox's messages. Subscriptions expire and must be renewed, there is a maximum of 1,000 active subscriptions per mailbox across all apps, and Microsoft advises handling lifecycle notifications to detect and recover from missed events.
Use application permissions for this: Microsoft notes that the Mail.Read.Shared delegated permission doesn't support subscriptions on items in shared or delegated folders.
What to do with each email
1.Classify
Order, invoice, question, complaint, reply to an existing thread, or noise like auto-replies.
2.Extract
Pull the data that matters from the body and attachments, including emails attached to emails, which Graph can read.
3.Draft or act
Draft a reply from your templates and your own data, or prepare the record for your CRM or ERP.
4.Approve
A person checks the draft in Outlook and sends it, or approves the record before it's created.
5.Log
Every email handled is recorded with what was done and why, so the mailbox has an audit trail.
Limits and edge cases
- Graph throttles each app per mailbox: pace catch-up jobs instead of looping over the whole inbox
- After mailbox permissions change, Microsoft notes it can take about two hours for the Power Automate connector to pick them up
- Threads with several people need care: replying to the wrong message in a chain is worse than not replying
- Emails with payment details, contracts or complaints should always reach a person