Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My automation cannot read or send from our shared mailbox

Short answer

A shared mailbox needs Full Access to be opened and Send As or Send on Behalf to send. Microsoft says Full Access alone cannot send. Automation also fails when the connection has no permission, a mailbox was converted from a personal one, or a group address is used. Check these before rebuilding.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The flow gets a 403 or 401 when it touches the shared mailbox.
  • It can read the shared mailbox but cannot send as it.
  • Emails go out from a person's name instead of the shared address.
  • A new flow works for me but not for a colleague.
  • The trigger runs twice, or runs for old emails.

Why does this happen?

  1. Reading and sending are separate permissions

    Microsoft states that Full Access lets someone open the mailbox, but they cannot send from it unless they also have Send As or Send on Behalf. With Send on Behalf, mail shows as sent by the person on behalf of the mailbox, and Microsoft notes it cannot be granted in the admin centre, only by PowerShell.

  2. The connection's account lacks permission

    Microsoft's connection guide says a 403 when sending from or reading a shared mailbox means the connection owner needs Send As or Full Access in the Exchange admin centre.

  3. The Outlook connector has its own conditions

    Microsoft documents that sending from a shared mailbox is expected to work only with the Microsoft 365 shared mailbox feature and does not work for a personal mailbox converted to shared. A Microsoft 365 group address cannot be used as the shared address, and after permissions are granted it can take about two hours to replicate.

  4. The trigger behaves in documented ways

    The same page says the shared-mailbox trigger may fire again for older emails moved to another folder, that one flow is needed per mailbox, and that with Safe Attachments Dynamic Delivery it may run twice, the first time with no attachments.

  5. The shared mailbox has a sign-in account

    Microsoft notes that creating a shared mailbox also creates an active user account with a system-generated password, and describes blocking its sign-in. Automation should use a named permission-holding account or app, never that password.

What can I do about it today?

  1. Write down what the automation must doRead only, read and send, or send only. The needed permission follows from that.
  2. Ask your Microsoft 365 admin who has which permissionThey can see Full Access, Send As and Send on Behalf on the mailbox. Ask in writing and keep the answer.
  3. Do not share the shared mailbox's own passwordNo one should sign in to a shared mailbox account with a password. Permissions are given to named people or apps.
  4. Wait before retrying a new permissionMicrosoft says replication after a permission change can take about two hours, so a retry minutes later can still fail.
  5. Check for doubled or missed emailsLook at what was sent or received since the automation started, so customers are not contacted twice.

When should I bring someone in?

  • Customer emails are involved and a mistake would reach customers.
  • The setup depends on one employee's account, who may leave.
  • You need rules across several mailboxes, or to process attachments reliably.

How do I handle it?

  1. Define the job and the least permissionI decide whether the automation reads, sends or both, and ask for only the permissions that job needs.
  2. Use an identity that outlives a personI prefer a dedicated service identity or app registration over a staff member's login, so a leaver does not stop the process.
  3. Test with a copy mailbox firstI test on a test mailbox with sample emails, including attachments and moved messages, before the live one.
  4. Guard against repeatsI record each processed message ID, so a double trigger or a moved email is not handled twice.
  5. Alert on failureA failed read or send raises an alert to a named person instead of failing silently.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Why can it read the mailbox but not send?

Microsoft says Full Access does not allow sending. Send As or Send on Behalf is also needed.

Can I use a group address as the shared mailbox?

Microsoft's connector page says an Office 365 group address cannot be used as a shared mailbox address.

Is it safe to give the automation Full Access?

It can read everything in the mailbox, so give it only if the job needs to. Ask your admin to review it and use a dedicated account.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.