I want to use a connector that does not give anyone else editing the flow access to my emails, nor does it have risk of any internal information getting leaked to a third party, which some of these connectors look like they might do. I am thinking about using the Outlook 365 option to send from a shared mailbox, but I am not sure if this means that anyone who edits this flow be able to access and/or influence my email account. I want to make sure my choice is secure for me and the company.
One option is to use SharePoint SendEmail capability using REST API.
'Body': '<b>Yo</b><br/>O boy!',
'Subject': 'E-mail using Flow via SharePoint'
I will end up turning over the flow to someone else, and I don't want that person to be able to access my email account. I'm trying to determine what kind of connector and email action there is such that no connection to my work email account is necessary.
@VictorIvanidze - When you use actions by providers like Sendgrid, there is a disclaimer that some information will be shared. @HelloThereAll is avoiding this situation. On the other hand, if they use the Shared inbox again their concern is that the inbox will be used for some other purpose. I think with a shared inbox their situation should be resolved because shared inbox can only be used by the people who has access to use it. I recommended another approach to send email.
Check out new user group experience and if you are a leader please create your group
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Many congratulations to the Season 1 2021 Flownaut Crew!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.