'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Power Automate HTTP 400 Errors with SharePoint Requests
Question details
Users encounter an HTTP 400 error when using the 'Send an HTTP request to SharePoint' action in Power Automate to call non-SharePoint services or APIs.
- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- Running a Power Automate flow that calls external APIs, such as Microsoft Forms, using the SharePoint HTTP connector.
- Observed behavior
- The flow fails and returns an HTTP 400 Bad Request error because using the SharePoint connector for external, non-SharePoint services is unsupported and was recently blocked by a backend service change.
Verify the endpoint URL in your failing HTTP request action to confirm whether it is targeting a native SharePoint resource or an external service like Microsoft Forms.
Replace SharePoint Connector with Microsoft Entra HTTP Request
This is the officially supported method for calling non-SharePoint Microsoft services from within Power Automate flows.
Microsoft Support has confirmed that using the 'Send an HTTP request to SharePoint' action for non-SharePoint services was a previously tolerated workaround that is no longer supported.
Recent backend changes have blocked this behavior, resulting in HTTP 400 errors. You must migrate these requests to the appropriate Microsoft Entra ID connector.
Open Power Automate, navigate to 'My flows', select the flow that is failing with the HTTP 400 error, and click 'Edit'.
Locate the 'Send an HTTP request to SharePoint' action that is calling the external service, click the three dots (More commands), and select 'Delete'.
Click 'New step', search for 'Invoke an HTTP request', and select the action under the Microsoft Entra ID (formerly Azure AD) connector.
Set the Method (e.g., GET or POST) and enter the URL of the external API you are trying to reach. Save and test your flow.
Update JSON Parsing for Changed API Responses
If you are calling an API like Microsoft Forms and the response structure has recently changed, your flow may fail during the parsing step.
Open a Microsoft Support Ticket
If the above solutions do not resolve your HTTP 400 errors or you require further investigation into backend changes.
Simplify Your Document Workflow with WPS Office
Troubleshooting backend API errors and flow failures in Power Automate can be time-consuming. If you're looking for a hassle-free, lightweight, and powerful alternative for your daily document and spreadsheet tasks, WPS Office is an excellent choice. It lets you focus on your work without worrying about complex cloud configurations.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button.
- 2. Install WPS Office: Run the downloaded installer file and follow the on-screen instructions to complete the setup.
- 3. Open and Edit: Launch WPS Office and open your existing Microsoft Office documents directly to start working seamlessly.
Frequently Asked Questions
Why did my 'Send HTTP request to SharePoint' action suddenly stop working?
Microsoft implemented backend service changes that strictly enforce the intended use of the SharePoint connector. Calling non-SharePoint endpoints (like Microsoft Forms) was never officially supported and is now blocked, resulting in a 400 Bad Request error.
Can I still use the SharePoint HTTP action for SharePoint REST APIs?
Yes, the 'Send an HTTP request to SharePoint' action works perfectly and is fully supported as long as it is querying a valid SharePoint endpoint within your tenant.
What is the alternative for calling external Microsoft APIs in Power Automate?
You should use the 'Invoke an HTTP Request' action via the Microsoft Entra ID (formerly Azure AD) connector. This action is officially supported for authenticating and calling other Microsoft services.
