Identifying Flows Using the SharePoint SendEmail API and Recommended Alternatives

Applies to Product - Power Automate

What’s happening?
With the retirement of the SharePoint SendEmail API by October 2025, there is a need to identify which flows are using this API in the SharePoint Send HTTP Request flow action across the entire tenant, and to find suitable alternative connectors to achieve similar functionality.

Reason:
The SharePoint SendEmail API is being retired, necessitating the identification of existing flows that utilize this API and the implementation of alternative solutions.

Resolution:
To identify which flows are using the SharePoint SendEmail API in the SharePoint Send HTTP Request flow action across the whole tenant, and to find the best alternative, please follow these steps:

1. Identify Usage: Use PowerShell to list all flows that have a specific API and action. Here is an example script to identify flows using the Utility.SendEmail API: powershell $actionName = @('SendEmail') $flows = Get-AdminFlow -EnvironmentName $environmentName $flowListArray = @() foreach($flow in $flows) { $flowProp = Get-AdminFlow -EnvironmentName $environmentName -FlowName $flow.FlowName foreach($action in $flowProp.Internal.properties.definitionSummary.actions) { if(($action.swaggerOperationId -in $actionName) -and $action.api.name -eq 'Utility') { $flowListArray += [PSCustomObject]@{ FlowName = $flow.FlowName DisplayName = $flow.DisplayName Action = $action.swaggerOperationId } } } } $flowListArray | Select-Object -Unique 'FlowName', 'DisplayName', 'Action' | Sort-Object -Property 'DisplayName'     
2. The above script will output a list of flows that use the SendEmail action.
3. Update Power Automate Flows -For Power Automate, update the API to utilize the Outlook connector ("Send an email") within the Actions. 
4. Update Custom Code or Workflows- For custom code or custom workflows, utilize the Microsoft Graph user:SendMail API.