Answered

API request to MS forms via Sharepoint API action

(2) Share

Report

Posted on by Mikbank

Hi all,
We’ve encountered an issue over the past 72 hours with the "Send an HTTP Request to SharePoint" action.

We are using it to call MS Forms (via https://forms.office.com/formapi/api/). to dynamically fetch all questions and answers from a form. However, since Friday, we've been receiving a 400 Unexpected response error message when running the action.

So far, we haven't found any outage alerts or documentation suggesting a change has been made. The issue was first spotted friday morning, and our monitoring still shows that the problem persists. I'm beginning to worry that the API calls to Forms via the SharePoint API might have been changed or restricted, though I haven’t found any documentation supporting that yet.

Interestingly, I’ve seen five-six other posts on Power platform forums reporting the same issue. Given that these API calls aren’t very common, I suspect it might be a general error or a recent change in how the Forms API can be accessed. I’ve also tried altering the request headers based on available documentation, but that hasn't resolved the issue.

Do anybody have a similar issue, and if so have you heard of what has caused this issue?

Categories:

Building flows

I have the same question (0)

All responses (9)

Answers (1)

JC-23091310-0 2 on at

Like (2)

Report

I have the same issue. Our Power Automate flow started failing Wednesday 18th of September at 11am PST. I have a similar feeling than you, something has changed in the send HTTP request to SharePoint action that no longer supports get requests to forms API.

Was this reply helpful? Yes No
Verified answer

Mikbank 24 on at

Like (4)

Report

I found a workaround to this myself :P :
Use the Http with microsoft Entra (pre authorized) to make the request. you just need to use https://forms.office.com/ for both URI and url when loging in to the connector.

Unfortunately this is a premium connector, so will need to liscense the flow or user when running it.
For users that are not using premium liscenses this is an issue.

**EDIT**

Got confirmation from Microsoft support that the HTTP with microsoft Entra ID will be the only way going forward to handle these request. Please seee this thread for clarification
https://community.powerplatform.com/forums/thread/details/?threadid=9ca4e187-9e76-ef11-a671-000d3a9e52a3

1 people found this reply helpful.

Was this reply helpful? Yes No
Michael E. Gernaey 53,442 Super User 2025 Season 2 on at

Like (2)

Report

Yeah its happening all over

Was this reply helpful? Yes No
MikeV 6 on at

Like (0)

Report

Same thing happened to me as well. I tried it with the Invoke an HTTP Request with the Microsoft Entra (pre authorized) but still no luck. I'm getting a badRequest with no error message stating what is wrong. does this look right?

Was this reply helpful? Yes No
Mikbank 24 on at

Like (0)

Report

Hi Mike

I dont think you need a bearer token - the authorization is handled by the connector.
I would suggest starting by removing that.

Was this reply helpful? Yes No
Birt 2 on at

Like (0)

Report

Not a solution but this is what I've found.

If you strip back the URI that you're making the request to and leave it at formsapi / api / tenant ID / groups / group ID then it works with the SharePoint connector it's only when you add Forms or Forms('FORM ID') that you start getting an error. If I copy and paste the URI into a browser I can still view the form data. Which to me points to something in the background of that specific connector.

Was this reply helpful? Yes No
MikeV 6 on at

Like (0)

Report

I tried it without the auth and with not headers but still no luck. I get this error now: UnauthorizedAccess to CDB
I inserted a ticket to ms and am waiting to hear back. Still no luck.

Was this reply helpful? Yes No
SS-10100935-0 2 on at

Like (0)

Report

Has anyone found a solution for this yet while using a non-premium connector?

It looks like the API should work as intended but there might have been some behind the scene updates which may have broken this.

Was this reply helpful? Yes No
Suggested answer

SaiRT14 1,990 Super User 2025 Season 2 on at

Like (0)

Report
Best practice is :

Check Microsoft 365 Service Health for possible issues.

Review and test the API request format to ensure it matches the latest Forms API requirements.

Inspect the response body in Power Automate's run history for more detailed error messages.

Use Postman to test the API independently.

Re-authenticate if the issue seems related to authorization.

Contact Microsoft Support if the issue persists after troubleshooting.

Was this reply helpful? Yes No