Emails are coming from SharePoint Online (no-reply@sharepointonline.com) even if specifying the 'From' to Distribution Email group.

[Ashrestha]

DL = Distribution Group Email

I am using Send Https SharePoint Online trigger to send email to my users and I saw a change of behaviors on how the email is sent out now. 

In the past by using this trigger and specifying the 'From' to a DL group, Even thou the email was sent from  (no-reply@sharepointonline.com), the Title of the email use to come from that DL email group (See snapshot below) but now it says SharePoint Online. How can I change the behavior so that the Title of the email is shown as it came from that DL email group. 

Here is the before and after screen shot of the email that I use to send to the users.

Before: I had specify the 'From' type to Web Dev email and it came from web dev even if it was sent from SharePoint online. 

After: Now, even specifying the 'From' Type to web dev, it shows SharePoint online and its confusing to the users. 

My Power automate:

How can I fix it??

[SudeepGhatakNZ]

@Ashrestha ,

I have experienced that the From header doesn't work even if you try to enforce it. It works in On-prem but nor in SPO. I found this back when I was struggling with this issue. Let me know if you find a solution.

sharepoint online - SP.Utilities.Utility.SendEmail Change "From" display text - SharePoint Stack Exc...

[Ashrestha]

Thanks @SudeepGhatakNZ for your prompt response. Like I said, It was working for me a month ago and now suddenly I see this change so I am struggling to figure this out. If I find a work around, I will post it here. 

Please keep me informed as well if you find any alternative solution for this issue. 

Thanks again. 

[Eric-Vana]

We are seeing the same issue it was fine until December 1st, now the From text is ignored and confusing users.

[joseluisharo]

I am facing the same issue, all emails are showing the same From information as "SharePoint Online" which is significantly confusing users. Did anybody find any possible workaround?

[joselaru]

We have had the same problem for a few days 😣

Any workaround?

[username_1]

Same issue for us, but it is not only related to Power apps, but in general in Sharepoint Online 2013

[VictorIvanidze]

You can modify your flow by changing the action that sends a message.

If you don't want to change the flow, you can use a third-party address rewriting service that will change the display name in the From: field..

[Anonymous]

Same issue occurring for me since last couple of days is there some Microsoft update because of that this has happened

[Vidushi2Chau]

I am facing the same problem, all of our emails are now showing FROM as SharePoint online instead of from the site name. Please suggest me if anybody knows the issue.

[VictorIvanidze]

Use the action "Send an email (V2)" instead of the "Send an HTTP request to SharePoint" action. 

[ialbasheir-kbr]

This Just hit our neck of the woods. is there a way to tracking of the SPO API updates? and saw a post that this issue started more than a month ago and tickets to MS no response yet. "Send an email (V2)" wont do us any good, as we are looking for unattended, anonymous email client. 

[VictorIvanidze]

>"Send an email (V2)" wont do us any good, as we are looking for unattended, anonymous email client. 

Why? Create a shared mailbox or a distribution lost and use it as a sender.

[ekarim2020]

Hi @Ashrestha ,

Here's a tip that you can use so that these Send email notifications are sent from your domain.

Here is an example. The SharePoint Online email address of my developer tenant is now noreply@mydomain.com (no mailbox needed):

This setting needs to be done at the Organisation level settings for Office so your Office 365 administrator will need to enable this feature:

 

"The default option is that users receive no-reply emails sent by Microsoft on behalf of your organization, which users receive as [EXTERNAL] notifications. You now have the option to use a custom domain as the sender of these notifications. Using this feature means that emails will now be sent from your own Exchange Online instance and they become internal communication. For example, no-reply@sharepointonline.com [External] could become no-reply@contoso.com, if Contoso.com is the domain that has been selected."

Supported Products. Please note that the following products currently support this feature:

• SharePoint Online
• OneDrive for Business
• Office
• Stream
• Planner
• Project
• Viva Connections
• Viva Topics
• Viva Amplify

To learn more please see: Select the domain to use for email from Microsoft 365 products - Microsoft 365 admin | Microsoft Lea...

Ellis
____________________________________
If I have answered your question, please mark the post as ☑️ Solved.
If you like my response, please give it a Thumbs Up.
My Blog Site

[NAJC]

I can confirmed I've experienced this issue on 2 environments and 4 SharePoint sites with Nintex for Office 365 workflow notifications. Started on the 8th of December. 

A rollback or resolution from Microsoft would be super cool and awesome. Plz fix. 

[happyccy]

Thanks for the workaround solutions. However, these ideal ways aren't' suitable for us since most of the subordinates under an organization don't have the ultimate admin rights, i.e., Office 365 administrator.

I hope that Microsoft will stress this issue.

[joselaru]

We have the same licensing problem, alternative solutions do not work for us.

Let's wait for a solution or a return to previous operation.

[VictorIvanidze]

Could you please explain what do you mean saying "alternative solutions do not work for us"?

[joselaru]

Maybe I explained it wrong, I don't want to say that it doesn't work for us, but for example we cannot use third-party components due to the type of company, and we cannot use the 'Send an email (V2)' component either because not all users of the organization have an O365 license.

It's a shame about the change, it causes confusion for the user.

[VictorIvanidze]

Sorry I just don't understand what do you mean saying "third-party components".

Also, to use 'Send an email (V2)' you have to have only one user with 0365 license.