Shared-mailbox flows send department emails from the wrong account
Reviewed by Helen Jones
Collab365 Spaces published a shared-mailbox automation problem analysis on 14 September 2026. It explains why a Power Automate run can succeed while the message appears to come from the maker, shows an on-behalf-of sender, or leaves no expected shared Sent Items record. The article describes an existing configuration problem, not a new Microsoft connector release.
Before a department starts sending automated HR, support or finance messages, a maker may check only that the flow ran successfully. That does not prove the recipient saw the intended sender or that the team can find and answer the message later. The Spaces analysis separates the Outlook action, the account behind its connection, Exchange sending rights and the Sent Items setting. Microsoft guidance confirms that the dedicated shared-mailbox action and Send As or Send on Behalf permissions have different effects, so a safe sender test is more useful than typing a shared address into a From field and hoping.
Analysis
Send one safe internal test message before using real recipients. Record the visible From name, where a reply lands and which Sent Items folder holds the message; ask an Exchange admin for the exact permission or mailbox setting if any check fails.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Shared-mailbox flows send department emails from the wrong account", Collab365 Spaces.