Internal Server Error when trying to Post/Patch to the SharePoint Admin Center

(0) Share

Report

Posted on by KS-22061817-0

I am trying to run a flow where it pushes data to the SharePoint admin center using Power Automate with the Microsoft.Online.SharePoint.TenantAdministration class, it had previously worked but it started to give me this internal server error a few days ago. I am still able to pull data from the admin center but pushing data is now being blocked. Could this be due to a security/policy change in the SharePoint Admin Center?

Thank you.

Categories:

Building flows

Power Automate Desktop

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

Sajeda_Sultana 189 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @KS-22061817-0,

This looks like the request is reaching SharePoint Admin Center, but SharePoint is rejecting the write operation during the POST/MERGE call.

Since you mentioned that GET still works but POST/PATCH/MERGE now fails, I would first check permissions and admin policy changes rather than the flow structure itself.

A few things to verify:

Make sure the account/connection used in Power Automate still has the required SharePoint Admin permissions.

Confirm that the tenant has not had any recent security, Conditional Access, or admin center policy changes.

Check whether the endpoint you are calling still supports the update operation you are trying to perform.

Try the same request in Postman or Graph Explorer using the same account to confirm whether the issue is with Power Automate or with the SharePoint Admin API permission/policy.

Also check the request body and headers. For a MERGE-style update, the headers and payload must match what the SharePoint Admin endpoint expects.

Because the error is InternalServerError and the read operation still works, it may not be a syntax issue only. It could be that the account can still read from the admin center but no longer has permission to update, or a tenant-side policy is blocking write operations.

I would also recommend checking the SharePoint Admin Center audit logs or asking the tenant admin if any recent changes were made to app permissions, admin roles, or security policies.

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Sajeda_Sultana

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

Start by capturing the full HTTP response body, status code, and correlation/request ID from a failed run. Since reads continue to work and writes suddenly

stopped, the issue is more likely related to permissions, tenant governance, or a recent Microsoft service change than to a problem in your Power Automate flow

logic itself. If the error persists and the correlation ID is available, opening a Microsoft support case with that ID will allow Microsoft to trace the failure in

SharePoint Online telemetry.

Was this reply helpful? Yes No
Sajeda_Sultana 189 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @KS-22061817-0,

Just following up to check if everything is working now. Let me know if you still need any help - I’m happy to assist.

If the issue has been resolved, please consider marking the answer as solved so it can help others with a similar question.

Thanks, and have a great day!

Was this reply helpful? Yes No
Suggested answer

KS-22061817-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

It was a mistake on my part, the SharingCapability site setting that I tried to patch it to was more permissive than the tenant-level settings. I adjusted it to the proper value and it went through.

Was this reply helpful? Yes No