The SharePoint SendEmail API, known as SP.Utilities.Utility.SendEmail, is an API utilized to send email from within the context of SharePoint. This may include usage within Power Automate, custom code, custom workflows, and web parts within SharePoint.
The SendEmail API is referenced via REST in the following way (“/_api/SP.Utilities.Utility.SendEmail”) while for CSOM, it would be “Utility.SendEmail”.
Important
- Please ensure that you follow the guidance and identify and update any use of the API prior to the end-of-life date of October 31st, 2025.
- No further emails will be sent after this date.
- Please review the updates that are sent to the Microsoft 365 message center related to the retirement of this API. SharePoint workflows will not be affected by this change. Please refer to SharePoint 2013 Workflow retirement.
Steps to follow
- Identify usage of the Utility.SendEmail API within custom code, custom workflows, or through Power Automate including “SharePoint Send HTTP Request flow action in Power Automate“.
- For Power Automate, update the API to utilize the Outlook connector (“Send an email”) within the Actions. (More information is available at Overview of using Outlook and Power Automate – Power Automate | Microsoft Learn)
- For custom code, or custom workflows, utilize Microsoft Graph user:SendMail API (Automate creating, sending, and processing messages using the Outlook mail API – Microsoft Graph | Microsoft Learn).
I believe SP 2013 workflows uses this API for Send Email action. So, the timeline should impact with retirement of SP 2013 workflows. Is there any action plan to support them?
I understand. Is there any other business reason why you need to retire it, except that it can’t be measured / tracked and monetized?
There's no objectives to monetize all of our APIs - as that's not beneficial for anyone. This API has been tracked and measured - like all of our APIs for sure. It's also an API which was introduced ~20 years ago and having a backwards compatibility for APIs for more than two decades has an operational and support cost, especially if more modern APIs are available, like in this case.
Our objective is not just...
Will the Grant access to an item or a folder action, that allows to send an email, be affected?
https://learn.microsoft.com/en-us/sharepoint/dev/business-apps/power-automate/guidance/manage-list-item-file-permissions#grant-access-to-an-item-or-a-folder
That’s an out-of-the-box feature and there are no requirements for you to adjust your flows with this announced API level end-of-life.
This is going to cause so many problems. I am sure you guys will be coming out with a way to do this with a premium license. lol.
This API has excited for ~20 years – which is a really long time – and shows the enterprise level commitment we have on these platforms. We though also need to sometimes clean the old stuff and there’s an easy replacement for it within the Graph API side.