← Back
(Updated) Retirement of the SharePoint SendEmail API
MC921752 · build prod-20251231-200323
Category
planForChange
Severity
normal
Major change
True
Last modified
2025-11-03 21:49:48
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
Action by (AI)
Services
SharePoint Online, Power Apps in Microsoft 365, Microsoft Power Automate in Microsoft 365
Tags
Updated message, User impact, Admin impact, Retirement
Master tags
Roadmap IDs

One-line summary

The Utility.SendEmail API in SharePoint Online will be retired on October 31, 2025; update custom code and workflows to use Microsoft Graph or Outlook connectors before then.

Similar updates

More like this
MC542767 (Updated) SharePoint 2013 workflow retirement
(Updated) SharePoint 2013 workflow retirement SharePoint 2013 workflows will be retired and stop working for all tenants on April 2, 2026; migrate to Power Automate or other supported solutions before this date. Updated October 3, 2025: This update serves as a reminder that SharePoint 2013 workflow will reti... Since the release of SharePoint.
MC693865 (Updated) SharePoint Add-In retirement in Microsoft 365
(Updated) SharePoint Add-In retirement in Microsoft 365 SharePoint Add-Ins will retire and stop working on April 2, 2026; migrate customizations to SharePoint Framework (SPFx) and notify users and developers. Updated October 3, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 6 months from now (April.
MC1072889 (Updated) SharePoint Alerts retirement
(Updated) SharePoint Alerts retirement SharePoint Alerts will be retired; creation ends for all tenants Jan 2026, and all alerts stop working July 2026. Updated October 22, 2025: We have updated the content below with Power Automate templates to assist in this transition. Microsoft is retiring the SharePoint Alerts feature to streamline and.
MC693863 (Updated) Azure ACS retirement in Microsoft 365
(Updated) Azure ACS retirement in Microsoft 365 Azure ACS will retire for SharePoint Online on April 2, 2026; update custom apps and integrations to use Microsoft Entra ID to maintain access. Updated October 3, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 6 months from now (April 2, 2026)..
MC1156359 (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online
(Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online Legacy Power BI integration in SharePoint lists and libraries will be retired between mid-November and mid-December 2025; users must switch to supported alternatives. Introduction To streamline reporting experiences and focus development.
MC1188232 Power Automate - Information regarding the end of support for Document Automation Toolkit
Power Automate - Information regarding the end of support for Document Automation Toolkit Document Automation Toolkit in Power Automate is no longer supported as of November 15, 2025; users must transition to alternatives like Microsoft Copilot Studio. On November 15, 2025, the Document Automation Toolkit feature in Power Automate reached of.

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.

Body (from Message Center)

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

  1.  As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center.
  2. Open Audit to search for activities.
  3.  Select a date range to run the audit search for (recommend running it for at least 90 days)
  4. Put the following text, “SendEmailApiInvoked” into the “Activities – operation names” textbox and click search.
  5. The request will be queued, and results will be available once processed.
  6. 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

[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:

  1. Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages
  2. Customizations through Power Automate may also utilize the Outlook connector and utilize “Send an email” within the Actions. Overview of using Outlook and Power Automate 

Learn more:

  1. Retirement of the SharePoint SendEmail API
  2. Automate creating, sending, and processing messages
  3. Overview of using Outlook and Power Automate
  4. Learn about the Microsoft Purview portal | Microsoft Learn

Raw JSON (for debugging)

Expand/collapse the full payload below.
Show/hide raw
{
  "snapshot_item": {
    "action_required_by": null,
    "ai_action_required_by": null,
    "ai_actions": [
      "Audit current API usage via Purview logs",
      "Migrate custom code and workflows to Microsoft Graph or Outlook connectors",
      "Update Power Automate flows using the retiring API"
    ],
    "ai_master_tags": [],
    "ai_model": "gpt-4.1",
    "ai_summary": "The Utility.SendEmail API in SharePoint Online will be retired on October 31, 2025; update custom code and workflows to use Microsoft Graph or Outlook connectors before then.",
    "ai_topics": [
      "SharePoint",
      "Power Apps",
      "Power Automate",
      "Power Platform",
      "Outlook"
    ],
    "category": "planForChange",
    "details_map": {
      "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."
    },
    "id": "MC921752",
    "importance": 5,
    "is_major_change": true,
    "last_modified": "2025-11-03T21:49:48Z",
    "ms_products": [
      "SharePoint",
      "Power Apps",
      "Power Automate"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "SharePoint Online",
      "Power Apps in Microsoft 365",
      "Microsoft Power Automate in Microsoft 365"
    ],
    "severity": "normal",
    "tags": [
      "Updated message",
      "User impact",
      "Admin impact",
      "Retirement"
    ],
    "title": "(Updated) Retirement of the SharePoint SendEmail API"
  }
}