{"id":13605,"date":"2025-11-04T07:01:08","date_gmt":"2025-11-03T22:01:08","guid":{"rendered":"https:\/\/m365jp.net\/?p=13605"},"modified":"2025-11-04T07:06:43","modified_gmt":"2025-11-03T22:06:43","slug":"mc921752-updated-retirement-of-the-sharepoint-sendemail-api-4","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2025-11-04-mc921752-updated-retirement-of-the-sharepoint-sendemail-api-4","title":{"rendered":"MC921752 | (Updated) Retirement of the SharePoint SendEmail API"},"content":{"rendered":"
\n
\n
\n\n\n\n
MC921752 | (Updated) Retirement of the SharePoint SendEmail API<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n\n\n\n\n\n\n\n
Classification<\/th>\nplanForChange<\/td>\n<\/tr>\n
Last Updated<\/th>\n11\/03\/2025 21:49:48<\/td>\n<\/tr>\n
Start Time<\/th>\n10\/30\/2024 17:56:12<\/td>\n<\/tr>\n
End Time<\/th>\n12\/31\/2025 08:00:00<\/td>\n<\/tr>\n
Message Content<\/th>\n\n

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. <\/p>\n

As a reminder, you are able to identify usage of the API via the Purview audit logs in the admin center<\/p>\n

    \n
  1.  As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center. <\/li>\n
  2. Open Audit to search for activities. <\/li>\n
  3.  Select a date range to run the audit search for (recommend running it for at least 90 days) <\/li>\n
  4. Put the following text, \u201cSendEmailApiInvoked\u201d into the \u201cActivities \u2013 operation names\u201d textbox and click search. <\/li>\n
  5. The request will be queued, and results will be available once processed. <\/li>\n
  6. Click on the results and review each of the items. <\/li>\n<\/ol>\n

    Use the UserAgent and ApplicationDisplayName to help identify the caller. <\/p>\n

    [NOTE:] If the ApplicationDisplayName = \u201cWorkflow\u201d 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.<\/p>\n

    From custom code the API can be referenced via REST as (\u201c\/_api\/SP.Utilities.Utility.SendEmail\u201d) while for CSOM, it would be \u201cUtility.SendEmail\u201d with more information on the original implementation at Utility.SendEmail method<\/a> for CSOM.<\/p>\n

    [When this will happen:]<\/p>\n

    October 31, 2025<\/p>\n

    <\/p>\n

    [How this will affect your organization:] <\/p>\n

    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. <\/p>\n

    [What you need to do to prepare:] <\/p>\n

    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. <\/p>\n

    The following are recommended or alternative approaches: <\/p>\n

      \n
    1. Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages<\/a><\/li>\n
    2. Customizations through Power Automate may also utilize the Outlook connector and utilize \u201cSend an email\u201d within the Actions. Overview of using Outlook and Power Automate<\/a> <\/li>\n<\/ol>\n
      <\/div>\n

      Learn more: <\/p>\n

        \n
      1. Retirement of the SharePoint SendEmail API<\/a><\/li>\n
      2. Automate creating, sending, and processing messages<\/a><\/li>\n
      3. Overview of using Outlook and Power Automate<\/a><\/li>\n
      4. Learn about the Microsoft Purview portal | Microsoft Learn<\/a><\/li>\n<\/ol>\n

        <\/p>\n

        <\/p>\n

        <\/p>\n

        <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

        MC921752 | (Updated) Retirement of the SharePoint SendEmail API Classification planForChange Last Updated 11\/0 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13605","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/13605","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/comments?post=13605"}],"version-history":[{"count":0,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/13605\/revisions"}],"wp:attachment":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/media?parent=13605"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/categories?post=13605"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/tags?post=13605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}