MC921752 - Retirement of the SharePoint SendEmail API

Updated October 1,June 5, 2025: As previously announced inGeneral Availability timeline and admin requirements update. We have simplified enablement for Scheduled prompts.

Key updates:

•  Power Automate license is no longer required. Users only need a Microsoft Copilot for Microsoft 365 license to use Scheduled prompts.
• No changes to DLP policies are required. Admins no longer need to configure DLP settings to enable the October 31st, 2024, post, weCopilot for Microsoft 365 connector.
• A dedicated Microsoft 365 environment will be retiringcreated automatically the Utility.SendEmail APIfirst time a licensed user creates scheduled prompt. The environment is a production environment type usable only by first party Copilot scenarios. For more details on October 31st,this environment, please see here.

For more general info on Scheduled prompts usage and management, please reference the latest Admin documentation.

4/15/25: The onboarding process for the feature in public preview has concluded. New customers interested in using the feature will need to wait until it becomes available to all customers in May 2025.

AsPlease note that customers who are interested in joining the preview must opt-in. To join the preview, customers should file a reminder,support ticket requesting to join the Scheduled prompts preview. Thank you are ablefor your feedback.

Coming soon for Microsoft Copilot for Microsoft 365: A new Scheduled prompts feature that allows users to identify usage ofautomate Copilot prompts to run at set times and frequencies in Copilot in Microsoft Teams, Office.com/chat, and Microsoft Outlook for the API via the Purview audit logs in the admin center

1.  As a tenant admin, navigate to theweb and Desktop. A Microsoft Purview Portal available within theCopilot for Microsoft 365 Admin Center.
2. Open Auditlicense and a Standard Microsoft Power Automate license are required to searchuse this feature. To be eligible, customers must also have the Optional Connected Experience (OCE) admin toggle enabled, and configure their DLP policies to allow the Copilot 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. Microsoft 365 connector in their default PowerPlatform environment.

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”This message is associated with more information on the original implementation at Utility.SendEmail method for CSOM.Microsoft 365 Roadmap ID 401124.

When this will happen:

October 31,Public Preview: We will begin rolling out mid-December 2024 (previously mid-November) and expect to complete by late December 2024 (previously late November).

General Availability: Rollout has officially begun early July 2025 (previously mid-May) expect to complete by mid-July 2025 (previously late May). 

How this will affect your organization:

Any components, custom code,Before this rollout: Users are unable to schedule Copilot for Microsoft 365 prompts to run at a specific time and frequency.

After the rollout: Users can find the Scheduled prompts feature by hovering over a prompt they have submitted to Copilot or by clicking on the Schedule prompts button in the Copilot response footer (references images below). After configuring their Scheduled prompt, when a user selects the Save and activate button to confirm the scheduled prompt, a user's prompt information will be sent to the Power Automate connections that utilizeand Power Platform system, and the SP.Utilities.Utility.SendEmail API, should be updated before the end of life date. The API will stop providing services on the retirement datePower Automate terms of service and will no longer send any email requests from that date.privacy policy apply:

Schedule prompt entry points

Schedule prompt Creation dialog

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 usingManaging the SP.Utilities.Utility.SendEmail API.

Scheduled prompts feature as an admin: To continue having the Scheduled prompts feature available in your organization, no action is required after completing the opt-in process. The following are recommended or alternative approaches:

1. Use Microsoft Graph to send email using the user: SendMail API (Partfeature is automatically included as part of the Outlook mail workload) Automate creating, sending, and processing messagesOptional Connected Experiences admin setting, which is on by default.

   Admins can access the Optional connected experiences setting at config.office.com

   If you prefer not to have this feature available to your organization, you can file a customer support ticket requesting to exit the preview program or disable the optional connected experiences setting at config.office.com. For more information: Admin controls for optional connected experiences. If you turn off the Optional connected experiences setting, this action will prevent anyone in your organization from seeing the Scheduled prompts feature in Copilot. If you choose to make these optional connected experiences available to your users, your users will also have the option to turn them by going to the privacy settings dialog box.

   To prevent exposing organizational data, you should also create a data policy in the Power Platform admin center. Creating a data policy in the center allows administrators to control access to these connectors in various ways to help reduce risk in your organization. Learn more here: Data policies - Power Platform | Microsoft Learn

   If you disable this feature after someone in your organization has already used the feature:

   • Users will no longer be able to manage previously scheduled prompts.
   • Customizations through Power Automate may also utilizeSessions for previously run scheduled prompts will continue to exist.
   • Users will no longer see the Outlook connector and utilize “Send an email” withinScheduled prompts feature or the Actions. Overview of using Outlook and Power Automateprompt management pane.

Learn more:Relevant articles

• Retirement of the SharePoint SendEmail APIData, Privacy, and Security for Microsoft Copilot for Microsoft 365 | Microsoft Learn
• Automate creating, sending, and processing messagesSecurity in Microsoft Power Platform - Power Platform | Microsoft Learn
• Overview of using Outlook and Power AutomateAdmin controls for optional connected experiences in Overview of optional connected experiences in Office - Deploy Office | Microsoft Learn
• Learn about the Microsoft Purview portal | Microsoft Learn

Before rollout, we will update this post with revised documentation.

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle;