A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Hi @Laura Rathbone,
Thank you for reaching out. Regarding your information, the "unauthorized" error encountered during the Send an email notification (V3) step typically indicates an authentication, permission, or tenant policy issue related to the email connector itself, rather than an error within the SharePoint folder trigger.
To help resolve this, kindly follow the following troubleshooting steps:
1/ Refresh or recreate the email connection
The most common resolution involves re-establishing the digital handshake between the services:
- Navigate to More > Discover All > Connections under Data within Power Automate.
- Locate the connection used by the email action and select Reconnect.
- Alternatively, remove the existing connection and create a new one. Once updated, ensure the flow is pointed toward this refreshed connection and re-test the process.
Ensure the Status is always Connected.
2/ Transition to the Office 365 Outlook Connector
In many tenants, the generic "Mail/Notifications" action can trigger an unauthorized status due to security configurations.
- Recommendation: Replace the "Send an email notification (V3)" step with Office 365 Outlook > Send an email (V2).
- The Office 365 Outlook connector is generally more robust and adheres more reliably to standard business licensing.
3/ Verify shared mailbox permissions
If the flow is configured to send "from" a shared mailbox or a different user's address, the account associated with the connection must have explicit "Send As" or "Send on Behalf of" permissions. Without these, the system will return an "Unauthorized" or "Forbidden" response.
Additionally, because this issue is often influenced by specific tenant governance and environment settings, I highly recommend engaging with the Power Automate Community. Experienced makers and specialists there can provide targeted advice on optimizing your notification patterns and navigating complex policy constraints.
Moderator Note: Please be advised that as a moderator, I can provide general guidance and best practices based on standard documentation. However, I do not have direct access to your specific tenant, environment settings, or connection health to validate the exact root cause. If these adjustments do not resolve the error, involving your internal IT admin or the dedicated community forums is the most effective path forward.
Thank you for your cooperation and patience.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.