How to Send SharePoint Emails as the Modified By User in Power Automate
Question details
The user wants to configure a Power Automate flow to automatically send an email using the SharePoint item's 'Modified By' user's email address as the sender.

- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- Triggering an automated email notification via Power Automate when a SharePoint item's status or content is updated.
- Observed behavior
- Exchange Online blocks the email sending action because the flow connection or owner lacks the required 'Send As' or 'Send on Behalf' permissions for the target user's mailbox.
Verify that you have edit access to the Power Automate flow and determine if you have an Exchange Administrator available in your organization to modify mailbox permissions if necessary.
Use a Fixed Mailbox and Include Modifier Details in the Body
This is the safest and most immediate workaround. It avoids security blocks by using an approved sender account while dynamically citing the modifier in the message text.
Navigate to your specific flow in Power Automate, click 'Edit', and locate the 'Send an email (V2)' action within your workflow steps.
Ensure the 'From' field is either left blank (to use the default authenticated connection) or set to an approved shared mailbox where you already have Send As permissions.
Click inside the 'Body' field of the email action. Type 'This email was sent on behalf of: ' and then select the '[Modified By Email]' token from the dynamic content menu.

Grant Send As Permissions via Exchange Admin Center
If the email must genuinely originate from the person who modified the SharePoint item, explicit Exchange permissions must be configured for the flow connection.
Need a Lightweight, Highly Compatible Office Suite? Try WPS Office
While resolving complex Power Automate permissions requires Exchange Admin configurations, your everyday document tasks shouldn't be a hassle. WPS Office offers a free, lightweight, and user-friendly alternative to Microsoft Office, ensuring seamless format compatibility for all your workflow documents.

Frequently Asked Questions
Why does Exchange Online block sending emails as another user?
Exchange Online enforces strict security policies to prevent email spoofing and phishing. A Power Automate flow connection can only send emails from its authenticated account unless explicit 'Send As' or 'Send on Behalf' permissions are granted by an administrator.
Can I use flow conditions to select different approved sender accounts?
Yes. You can retrieve the profile of the user who modified the item and use a 'Condition' control in Power Automate to route the flow to different 'Send an email' actions. However, each sender account used will still require the appropriate Exchange permissions.
Does granting 'Send As' permission pose a security risk?
Granting 'Send As' permissions allows the specified account to send emails that appear exactly as if they were sent by the mailbox owner. It should be tightly controlled and audited by IT administrators to prevent misuse.
Where can I get advanced help with my Power Automate workflow?
For highly specific implementation guidance or complex logic configurations, you can post your scenario, along with screenshots of your flow, in the official Microsoft Power Automate Community forums.




