MC921752 – (Updated) Retirement of the SharePoint SendEmail API (archived)

Product:

Copilot, Microsoft 365 admin center, Microsoft 365 Copilot, Microsoft Graph, Outlook, Power Apps, Power Apps in Microsoft 365, Power Automate, Power Automate in Microsoft 365, Purview, Purview Communication Compliance, SharePoint

Platform:

Developer, Online, World tenant

Status:

Change type:

Admin impact, Retirement, Updated message, User impact

Links:

Details:

Summary:
The SharePoint Utility.SendEmail API will retire on October 31, 2025. Tenants should identify usage via Purview audit logs and update any custom code or Power Automate flows using this API. Alternatives include Microsoft Graph SendMail API and Outlook connector in Power Automate.

Details:
Updated October 1, 2025: As previously announced in the October 31st, 2024, post, we will be retiring the Utility.SendEmail API on October 31st, 2025.
As a reminder, you are able to identify usage of the API via the Purview audit logs in the admin center
As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center.
Open Audit to search for activities.
Select a date range to run the audit search for (recommend running it for at least 90 days)
Put the following text, "SendEmailApiInvoked" into the "Activities - operation names" textbox and click search.
The request will be queued, and results will be available once processed.
Click on the results and review each of the items.
Use the UserAgent and ApplicationDisplayName to help identify the caller.
[NOTE:] If the ApplicationDisplayName = "Workflow" then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows.
From custom code the API can be referenced via REST as ("/_api/SP.Utilities.Utility.SendEmail") while for CSOM, it would be "Utility.SendEmail" with more information on the original implementation at Utility.SendEmail method for CSOM.
[When this will happen:]
October 31, 2025

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2024-10-31

updated:
2025-11-04

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Retirement of SendEmail API
Custom applications and workflows relying on the SendEmail API will fail to send emails post-retirement, disrupting communication processes.
   - roles: Tenant Admin, Developer
   - references: https://learn.microsoft.com/purview/purview-portal, https://learn.microsoft.com/graph/outlook-create-send-messages" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/graph/outlook-create-send-messages

Increased workload for IT support
Users may experience issues with email functionalities, leading to increased support requests and potential downtime.
   - roles: IT Support, Helpdesk Staff
   - references: https://learn.microsoft.com/power-automate/email-overview, https://learn.microsoft.com/previous-versions/office/sharepoint-csom/jj167799(v=office.15)

Need for migration to alternative APIs
Organizations must migrate to Microsoft Graph or Outlook connector, requiring development resources and time, potentially delaying other projects.
   - roles: Developer, Project Manager
   - references: https://learn.microsoft.com/graph/outlook-create-send-messages" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/graph/outlook-create-send-messages, https://learn.microsoft.com/power-automate/email-overview " target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/power-automate/email-overview

User experience degradation
Users relying on automated email notifications may face disruptions, leading to frustration and decreased productivity.
   - roles: End User, Business Analyst
   - references: https://learn.microsoft.com/purview/purview-portal, https://learn.microsoft.com/power-automate/email-overview " target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/power-automate/email-overview

Compliance and audit challenges
Failure to update systems may lead to compliance issues if automated processes do not function as intended, risking data governance.
   - roles: Compliance Officer, Data Governance Manager
   - references: https://learn.microsoft.com/purview/purview-portal, https://learn.microsoft.com/graph/outlook-create-send-messages" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/graph/outlook-create-send-messages

Configutation Options**

XXXXXXX ... paid membership only

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

Imagine you're managing a library, and you have a specific system for sending out notifications to members about overdue books or upcoming events. This system has been in place for years, but now it's being phased out. This is similar to what's happening with the SharePoint SendEmail API, which will retire on October 31, 2025.

In the library analogy, think of the SendEmail API as a trusty old librarian who has been manually sending out these notifications. However, the librarian is retiring, and you need to find a new way to handle these tasks. You have a couple of options: you could hire a new librarian who uses a more modern method to send notifications, or you could automate the process entirely with a new system.

In the world of IT, the alternatives to the retiring SendEmail API are the Microsoft Graph SendMail API and the Outlook connector in Power Automate. These tools are like the new librarian or the automated system, respectively. They offer more modern and efficient ways to handle email notifications, similar to how the new librarian might use email or text messages instead of paper notices.

To prepare for this change, it's important to review your current processes and identify where the old system is being used. This is like checking which notifications the retiring librarian is responsible for. You can use the Purview audit logs to track down where the SendEmail API is being utilized, ensuring you don't miss any critical processes.

Once you've identified these areas, you can start transitioning to the new methods. The Microsoft Graph SendMail API can be thought of as a direct replacement, allowing you to send emails in a similar way but with updated technology. Meanwhile, Power Automate's Outlook connector offers a more integrated approach, automating the process and potentially saving time and effort.

In summary, just as you would plan for a librarian's retirement by finding new ways to manage library notifications, it's essential to plan for the retirement of the SharePoint SendEmail API by adopting newer, more efficient email-sending methods. This ensures a smooth transition and continued service without interruption.