Microsoft announced the retirement SharePoint SendEmail API, known as SP.Utilities.Utility.SendEmail, which is utilized to send internal SharePoint emails. It is getting retired on October 31, 2025.
This means all email notifications send through this method will stop to work. This change affects skybow Send internal email action that has used this method. The action Send internal email will no longer work in SharePoint Online after October 31, 2025. 

With the latest update, end users will now see the following notification message:

To keep send email functionality, you must migrate Send internal email to the Send email action. You can perform the migration in one of the following ways: 

Migration steps for the solution in Teamsware studio

• When you navigate to the solution, dialog window appears on startup if your solution contains any Send internal email action in one of the features. 

  Note:  The 'Actions retirement' dialog will continue to appear on startup as long as there are any Send internal email actions remaining in the solution and the Show this dialog on startup option is checked.
  Note: You can skip the Migration step for the whole solution, and do migration for feature or for individual action (see below). 
  
  
  

• Click the 'Migrate' button in the dialog window.
  
  Note: Before migrating, please ensure all changes to the form are saved; otherwise, any unsaved changes will be lost. 
  
  Note: Send email action in Modern Forms, List Actions and Automation Actions requires to approve API access request with 'Mail.Send' permissions. This should be done once per tenant by a tenant admin. 
  
  
  
  
  

• Next, click the 'Start' button. This will start the migration of all Send internal email actions to Send email actions across the entire solution - including Scheduled and Triggered Actions.
• Once the migration is complete, Teamsware Studio will automatically reload. 
  
  

Migration steps for Modern Forms

• If you have configured Send internal email action on the form, you will see a notification: 
  
  
  
  

• Click the 'Migrate' button on the form. 

• Note: Before migrating, please ensure all changes to the form are saved; otherwise, any unsaved changes will be lost. 
  
  Note: Send email action requires to approve API access request with 'Mail.Send' permissions. This should be done once per tenant by a tenant admin.
  
  
  
  

• Mark the checkbox if you want to migrate retiring actions in all customizations on the current site (in Modern Forms, List Actions and Automation Actions on pages. Note: This migration does not include actions in Scheduled or Triggered Actions).
• Click on 'Start' button to start migration of retiring actions.
• After the migration is complete, the form will automatically reload. 
  
  

Migration steps for List Actions

• In the List Actions panel click on 'Migrate' button. 
  
  
  
  
  
  

• Mark the checkbox if you want to migrate retiring actions in all customizations on the current site (in Modern Forms, List Actions and Automation Actions on pages. Note
  : This migration does not include actions in Scheduled or Triggered Actions). 
  
  
  
  
  
  
  
  

• Click on 'Start' button to start migration of retiring actions.
• After the migration is complete, the page will automatically reload. 
  
  

Migration steps for Automation Actions

• Open page in edit mode.
  
  

• Click on 'Migrate' button.
  

  
  
  
  

• On the next screen, mark the checkbox if you want to migrate retiring actions in all customizations on the current site (in Modern Forms, List Actions and Automation Actions on pages. Note: This migration does not include actions in Scheduled or Triggered Actions).
• Click on 'Start' button to start migration of retiring actions.
• After the migration is complete, the page will automatically reload. 
  
  
  

Migration for Scheduled/Triggered actions

• In the List Actions panel click on 'Migrate' button.

  
  
  

• After the migration is complete, the page will automatically reload.
• Approve Teamsware Exchange Connector API Permissions (This should be done once per tenant by a tenant admin.)
• Configure Additional Options: Additional settings for the Send Email action can be adjusted as needed. These include fields such as Attachments, Fallback, Show before send and others.  
  
  

Migration steps for individual action

• Click the "Migrate" button displayed on the action. This will automatically switch the configuration to the new Send Email action. All previously configured settings will be saved. After the migration is complete, you need to finish configuring the Send Email action. Please follow the steps below: 

  • Approve API Permissions (This should be done once per tenant by a tenant admin.):
    for Modern Forms:  
    - Mail.Send — required to send emails.  
    -  Mail.ReadWrite — required only if the total size of attachments exceeds 3 MB. 

    for Scheduled/Triggered actions: 
    - Teamsware Exchange Connector - required to send emails. 

• Configure Additional Options: Additional settings for the Send Email action can be adjusted as needed. These include fields such as Attachments, Fallback, Show before send and others.  
  
  
  

Important

Important: After October 31, 2025, the Send internal email action will be automatically switched to the Send email action — only if the Teamsware Exchange Connector has been approved for the tenant in the Scheduled/Triggered actions. 

Important: In Send email action, emails cannot be sent from external users in Modern Forms, List Actions and Automation Actions.

Important: In SharePoint On-Premises 2019 and SharePoint Subscription Edition (SE), the Send email action functions as Send internal email. The following options: Attachments, Show before send, Save to sent items, Fallback will not work. These limitations are due to platform constraints in on-premises SharePoint environments.

Important: If you have active deployments, please make sure after migration create new package and update deployment for all target sites. Best to do this before retirement date.

Purview audit logs

Additionally, you are able to identify usage of the retired API via the Purview audit logs in the admin center (Admin center -> Microsoft Purview):

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.

 More details you can find in the Microsoft 365 Message Center Archive.