cancel
Showing results for 
Search instead for 
Did you mean: 

Please add the posibility to send mails via an Alias

 

Hi,

 

Sending notification mails should be possible via an alias. 

 

In my case my client wants me to send automatic emails to partners when a corresponding item is added in a sharepoint list. I have nothing to do with these partners but they do get to see my personal email adress when I create a flow for automatic notifications.

 

This will only cause problems for me... the mails should be sent via "noreply" or something that indicates that it's coming from the flow.

 

The only solution that I see now, is to create an extra office 365 user... wich is a bit of overkill...

 

Thanks,

Status: Completed

I'm copying up the very helpful response from @stormea : 

 

This isn't necessary. Just use the Mail - Send an email notification action.

mail - send email action.JPG

 

This connector works the same as the normal connectors, but instead of using a user account it acts as its own Flow based connector. Therefore when you send emails using it, the message will read as coming from microsoft@powerapps.com and display like the following:

 

mail send email header.JPG

 

I only use this as it makes sure to avoid sending the info for the Flow initiator.

Comments
Level: Powered On

There is another Idea out there for this same thing with over 300 votes from 2017 and still this has not been added. Man Sad

 

https://powerusers.microsoft.com/t5/Flow-Ideas/Add-the-From-field-on-the-action-Send-Approval-email/...

Power Automate Staff

Allowing free-form aliases is a security risk.

If say for eg: "Joe" is  sending an email from joe@contoso.com and we allow Joe to override the "sender" address to ceo@contoso.com - the receiver could potentially be baited into thinking that the email actually came from ceo@contoso.com.

This is why it is highly unlikely that free-form "sender address" override will be coming to flow soon.

 

Having said that if you don't want to send emails from your Personal account, you still have the following options:

1. Use the built-in "send email" action

2. Acquire a "service account" and create a Office 365 Outlook connection with Service account credentials and then configure your flow to send emails using the connection that contains the service account creds.

3. Send an email from a Shared Mailbox (Assuming you have permissions to send emails from a shared mailbox.

4. Use a mailer service like SendGrid, MailChimp etc. that allows you to configure your own mail server with customizable sender addresses.

 

Hope this helps!

-Sunay

 

Level: Powered On

 

I really don't see it that way.. contoso.com is an internally managed domain name. Fact that I'm creating aliasses in office 365 means that I already have administration permissions. When you have a self hosted exchange server, you can send mails to whoever from whoever you want. The security is already there when creating aliasses in office 365. All I'm doing is using the alias created in the administration section to send an email but still my own email adress is shown when the final mail arrives and not the alias.

 

So, trying to make sense of what you are saying....

 

1. Use the built-in "send email" action => Are you saying that I should just ignore the problems described in my original post and just go ahead blindly? 

2. Acquire a "service account" and create a Office 365 Outlook connection with Service account credentials  and then configure your flow to send emails using the connection that contains the service account creds. => When I look around online on how to create a service account, it seems like I have to use a noffice 365 license so with Acquire you actually mean BUY an extra license?

3. Send an email from a Shared Mailbox (Assuming you have permissions to send emails from a shared mailbox. => Buy an extra license and share it with others?

4. Use a mailer service like SendGrid, MailChimp etc. that allows you to configure your own mail server with customizable sender addresses. => Go buy email services somewhere else?

Anonymous
Not applicable

@Sunay- I understand your concern.  Please check out other workflow tools which do have this functionality including Nintex and K2.

 

Perhaps a step in the right direction would be adding some options for "from" during the Flow build.  I'd suggest at minimum, ncluding the flow author (flow developer), current user (sharepoint item author / whoever is actually initiating the flow), or O365 group where the flow is located.

 

My concern is that anyone intiating a workflow which I publish can send email as me.  For example, a sharepoint list (say a grocery list) and includes an email function to notify the designated purchaser should come from the item author, not from the flow developer so any email replies to that item notification go to the person who actually entered the list item instead of me.

 

I don't like the "no-reply" option because there are many times when I build flows which facilitate discussions among others in my organization... and have nothing to do with me.

Power Automate Staff

@Erdem- Shared Mailboxes don't need licenses.

"You don’t need to assign licenses to shared mailboxes that are under 50GB."

Source: https://support.office.com/en-us/article/create-a-shared-mailbox-871a246d-3acd-4bba-948e-5de8be0544c...

 

 

@AnonymousRe: Perhaps a step in the right direction would be adding some options for "from" during the Flow build.  I'd suggest at minimum, ncluding the flow author (flow developer), current user (sharepoint item author / whoever is actually initiating the flow), or O365 group where the flow is located.

 

 

The Flow team is actively working on lighting up some of these use cases - this is something we are definitely looking to solve for our customers.

Level 8

This isn't necessary. Just use the Mail - Send an email notification action.

mail - send email action.JPG

 

This connector works the same as the normal connectors, but instead of using a user account it acts as its own Flow based connector. Therefore when you send emails using it, the message will read as coming from microsoft@powerapps.com and display like the following:

 

mail send email header.JPG

 

I only use this as it makes sure to avoid sending the info for the Flow initiator.

Power Automate Staff
Status changed to: Completed

I'm copying up the very helpful response from @stormea : 

 

This isn't necessary. Just use the Mail - Send an email notification action.

mail - send email action.JPG

 

This connector works the same as the normal connectors, but instead of using a user account it acts as its own Flow based connector. Therefore when you send emails using it, the message will read as coming from microsoft@powerapps.com and display like the following:

 

mail send email header.JPG

 

I only use this as it makes sure to avoid sending the info for the Flow initiator.