Published Oct 30, 2024
The SharePoint SendEmail API is being retired. Key updates include the removal of the Power Automate license requirement, automatic creation of a dedicated Microsoft 365 environment, and no changes needed for DLP policies. Scheduled prompts feature will be available for Microsoft Copilot for Microsoft 365 users starting July 2025.
Updated June 5, 2025: As a reminder from the post announced on October 31st, 2024, we will be retiring the Utility.SendEmail API on October 31st, 2025.
In addition, you are now able to identify usage of the API via the Purview audit logs in the admin center
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
How this will affect your organization:
Any components, custom code, or Power Automate connections that utilize the SP.Utilities.Utility.SendEmail API, should be updated before the end of life date. The API will stop providing services on the retirement date and will no longer send any email requests from that date.
What you need to do to prepare:
Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API.
The following are recommended or alternative approaches:
Learn more: