'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix SharePoint Online Showing Wrong Sender Name in Emails
Question details
Users are experiencing an issue where emails sent through SharePoint Online display 'SharePoint Online' instead of the correctly configured sender display name.
- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- Sending automated emails through SharePoint Online using .NET applications or Power Automate flows.
- Observed behavior
- The sender name in received emails incorrectly shows as 'SharePoint Online', ignoring the custom sender display name configured in the Microsoft.SharePoint.Client.Utilities library.
Ensure you have administrator privileges for your Microsoft 365 tenant, as resolving this backend service issue requires submitting an official support ticket.
Submit a Support Ticket via Microsoft 365 Admin Center
Because this issue stems from a service-side backend change, Microsoft engineers must investigate your specific tenant to resolve the email display name behavior.
This problem is not caused by your local code or library version. A backend update to SharePoint Online has altered how the Microsoft.SharePoint.Client.Utilities library processes sender names, requiring administrative intervention from Microsoft.
Navigate to the Microsoft 365 admin center at admin.microsoft.com and log in with your administrator credentials.
On the left navigation pane, click on 'Support' and then select 'Help & support' to open the service request panel.
Describe the issue, noting that emails sent via Microsoft.SharePoint.Client.Utilities are displaying the wrong sender name due to a recent service-side change, and submit the ticket.
Consult the Microsoft Q&A Developer Forum
Engage with Microsoft engineers and community partners in the official developer forums for potential workarounds or updates regarding this specific service change.
Try WPS Office for Your Document Needs
While SharePoint and Microsoft 365 handle your backend workflows, WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office for creating, editing, and managing your daily documents effortlessly.
- 1. Download WPS Office: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install and Launch: Run the lightweight installer and open WPS Office to access Writer, Spreadsheet, and Presentation tools.
- 3. Save in Standard Formats: Create your documents and save them in standard .docx, .xlsx, or .pptx formats for seamless sharing with Microsoft users.
Frequently Asked Questions
Why did my SharePoint email sender name suddenly change to 'SharePoint Online'?
This issue is typically caused by a service-side backend update applied to Microsoft 365 or SharePoint Online, which altered how the Microsoft.SharePoint.Client.Utilities library processes and applies sender display names.
Does this sender name issue affect Power Automate flows as well?
Yes, multiple users have reported that automated emails sent through Power Automate flows using SharePoint connectors also exhibit the same 'no-reply' or generic 'SharePoint Online' sender name behavior.
Can I fix the wrong sender name by modifying my .NET application code?
Typically, no. If no code or library versions were changed on your end before the issue started, it is an external service-side problem that requires Microsoft backend support to investigate and resolve for your specific tenant.
