MC921752 - Retirement of the SharePoint SendEmail API

Updated June 5,October 1, 2025: General Availability timeline andAs 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 requirements update. We have simplified enablement for Scheduled prompts.center

Key updates:

1.  Power Automate license is no longer required. Users only needAs a tenant admin, navigate to the Microsoft Copilot forPurview Portal available within the Microsoft 365 licenseAdmin Center.
2. Open Audit to use Scheduled prompts.search for activities.
3. No changes Select a date range to DLP policies are required. Admins no longer need to configure DLP settings to enablerun the Copilotaudit search for Microsoft 365 connector.(recommend running it for at least 90 days)
4. A dedicated Microsoft 365 environmentPut the following text, “SendEmailApiInvoked” into the “Activities – operation names” textbox and click search.
5. The request will be created automaticallyqueued, and results will be available once processed.
6. Click on the first time a licensed user creates scheduled prompt.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 environment is a production environment type usable only by first party Copilot scenarios. ForSP.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 detailsinformation on 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 processoriginal implementation at Utility.SendEmail method 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.

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

Coming soon for Microsoft Copilot for Microsoft 365: A new Scheduled prompts feature that allows users to automate Copilot prompts to run at set times and frequencies in Copilot in Microsoft Teams, Office.com/chat, and Microsoft Outlook for the web and Desktop. A Microsoft Copilot for Microsoft 365 license and a Standard Microsoft Power Automate license are required to use 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 Microsoft 365 connector in their default PowerPlatform environment.

This message is associated with Microsoft 365 Roadmap ID 401124. CSOM.

When this will happen:

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 JulyOctober 31, 2025 (previously mid-May) expect to complete by mid-July 2025 (previously late May). 

How this will affect your organization:

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

AfterAny components, custom code, or Power Automate connections that utilize the rollout: Users can findSP.Utilities.Utility.SendEmail API, should be updated before the Scheduled prompts feature by hovering over a prompt they have submitted to Copilot or by clickingend of life date. The API will stop providing services on the Schedule prompts button in the Copilot response footer (references images below). After configuring their Scheduled prompt, when a user selects the Saveretirement date and activate button to confirm the scheduled prompt, a user's prompt information will be sent to the Power Automate and Power Platform system, and the Power Automate terms of service and privacy policy apply:

Schedule prompt entry points

Schedule prompt Creation dialog

no longer send any email requests from that date.

What you need to do to prepare:

ManagingMigrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the Scheduled prompts feature as an admin: To continue havingSP.Utilities.Utility.SendEmail API.

The following are recommended or alternative approaches:

1. Use Microsoft Graph to send email using the Scheduled prompts feature available in your organization, no action is required after completing the opt-in process. The feature is automatically included as partuser: SendMail API (Part of the Optional Connected Experiences admin setting, which is on by default.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

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.
• Sessions for previously run scheduled prompts will continue to exist.
• Users will no longer see the Scheduled prompts feature or the prompt management pane.

Relevant articles

• Data, Privacy, and Security for Microsoft Copilot for Microsoft 365 | Microsoft Learn
• Security in Microsoft Power Platform - Power Platform | Microsoft Learn
• Admin controls for optional connected experiences in Overview of optional connected experiences in Office - Deploy Office | 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;