This was extremely useful. I would say I'm quite an experienced Flow creator but haven't fully understood the use of this "Run only" feature, until now. I guess I haven't been required to use it in any project so haven't had the need to research it thoroughly. From this use case and your detailed explanation, my understanding has been deepened and I can now figure out various use cases for this feature. Thanks for sharing.
Since "service accounts" require a license, some organizations don't allow their use. In my org, I often have a "shared mailbox" created (which *does not* require a license, just that the connection being used has "send as" permission) and use the "send email from shared mailbox" action. Yes, there's a bit of overhead in terms of managing who has send as permission to that mailbox, and you wouldn't want to allow *everyone* that access, but it's less costly from a financial point of view.
Nice DC! The step to change Outlook connection to a "do not reply" address is really useful when building RPA to client companies. Does it (this Outlook part) work for any other flow (apart from specific item)?
Glad it was helpful! My educated guess is 'yes' you can change the Outlook connector's connection in other flows as well, better test and verify first.
"How To Use Power Automate Run-Only for Outlook & SharePoint" is a valuable guide for those looking to make the most of Power Automate in their workflows with Outlook and SharePoint. This "Run-Only" functionality allows delegating flow execution to specific users, ensuring more precise and secure control over the automations. By following this guide, users can optimize their work processes, increase efficiency, and reduce the burden of repetitive tasks. It's an essential tool for enhancing productivity and collaboration in modern office environments!🚀🚀🚀
