Retirement of the SharePoint SendEmail API

1. 3 Nov 2025

   Only details this page does not show changed.

2. 1 Oct 2025

   Updated September 30,October 1, 2025: As a reminder frompreviously announced in the post announced on October 31st, 2024, post, we will be retiring the Utility.SendEmail API on October 31st, 2025.  In addition,As a reminder, you are now able to identify usage of the API via the Purview audit logs …

3. 30 Sep 2025

   Updated June 5,September 30, 2025: As a reminder from the post announced on October 31st, 2024, …

4. 5 Jun 2025

   The text changed; it is too long to compare word by word here.

5. 5 Jun 2025
   • Tags User impact, Admin impact, Retirement → Updated message, User impact, Admin impact, Retirement

   Updated June 5, 2025: General 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 Copilot for Microsoft 365 connector. A dedicated Microsoft 365 environment will be retiringcreated automatically the first 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 this environment, please see here. For more general info on Scheduled prompts usage and management, please reference the Utility.SendEmail API from SharePoint.latest Admin documentation. 4/15/25: The SP.Utilities.Utility.SendEmail could be usedonboarding 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. 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 send emails from custom applications or processes within SharePoint Online, including Power Automate,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 custom workflows. From custom codefrequencies in Copilot in Microsoft Teams, Office.com/chat, and Microsoft Outlook for the API can be referenced via REST as (“/_api/SP.Utilities.Utility.SendEmail”) while for CSOM, it wouldweb and Desktop. A Microsoft Copilot for Microsoft 365 license and a Standard Microsoft Power Automate license are required to use this feature. To be “Utility.SendEmail” with more information oneligible, customers must also have the original implementation at Utility.SendEmail method Optional Connected Experience (OCE) admin toggle enabled, and configure their DLP policies to allow the Copilot for CSOM.Microsoft 365 connector in their default PowerPlatform environment. This message is associated with 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 Power Automate connections that utilizeby clicking on the Schedule prompts button in the Copilot response footer (references images below). After configuring their Scheduled prompt, when a user selects the SP.Utilities.Utility.SendEmail API, should be updated beforeSave and activate button to confirm the end of life date. The APIscheduled prompt, a user's prompt information will stop providing services onbe sent to the Power Automate and Power Platform system, and 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, processesManaging the 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 feature is automatically included as part of the Optional 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 policies running within SharePoint Online thatdisable 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 been configuredthe option to send email usingturn them by going to the SP.Utilities.Utility.SendEmail API. The following are recommended or alternative approaches: Use Microsoft Graph to send email usingprivacy settings dialog box. To prevent exposing organizational data, you should also create a data policy in the user: SendMail API (Part ofPower Platform admin center. Creating a data policy in the Outlook mail workload) Automate creating, sending, and processing messages Customizations throughcenter allows administrators to control access to these connectors in various ways to help reduce risk in your organization. Learn more here: Data policies - Power Automate may also utilizePlatform | Microsoft Learn If you disable this feature after someone in your organization has already used the Outlook connector and utilize “Send an email” withinfeature: 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 Actions. Overview of using Outlookprompt management pane. Relevant articles Data, Privacy, and Security for Microsoft Copilot for Microsoft 365 | Microsoft Learn Security in Microsoft Power Automate  Platform - Power Platform | Microsoft Learn more: RetirementAdmin controls for optional connected experiences in Overview of the SharePoint SendEmail API Automate creating, sending, and processing messages Overviewoptional 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 using Outlook and Power Automatethis product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle;

6. 30 Oct 2024 · first version seen

• Utility.SendEmail methodNot read yet
• Automate creating, sending, and processing messagesNot read yet
• Overview of using Outlook and Power AutomateNot read yet
• Retirement of the SharePoint SendEmail API
• Learn about the Microsoft Purview portal | Microsoft LearnChecked 27 Oct 2026

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

• Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
• 3 linked pages have not been read yet.