web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / SharePoint Site Addres...
Power Automate
Unanswered

SharePoint Site Address 'https://******-mediap.svc.ms/' is not valid clientRequestId*

(2) ShareShare
ReportReport
Posted on by 6
Good day 

I have a step in my flow that zips a sharepoint folder as there is no functionality in powerautomate that can zip an exiting folder in Sharepoint 

Ever since yesterday I started getting this error 

SharePoint Site Address 'https://******-mediap.svc.ms/' is not valid clientRequestId: *******-7539-*****-9202-*******

Is this now a feature that is removed?
Categories:
I have the same question (0)
  • CU11121632-0 Profile Picture
    3 on at
    Hi, I am having this exact same issue starting at the same time. I was using a step to zip a file from sharepoint and as of yesterday ~9 pm CST, it ceased functioning giving the same error just with my site address. Any feedback on troubleshooting is appreciated.
  • SS-11121617-0 Profile Picture
    4 on at
    Good morning, 
     
    As of this morning I am having the exact same issue and I get the exact same error message.  My flow has been running fine for almost two years.  There are more posts on this thread of people having the same issue and they were posted today too:  https://community.powerplatform.com/forums/thread/details/?threadid=a684e45c-a0b7-ef11-b8e8-7c1e5259f813
     
    Here are some screenshots for my issue:
     
    Show raw outputs:
     
     
    Error in Power Automate screenshot: 
     
     
    Flow Action: 
     
     
    Seems like this may be a Microsoft issue or an outage?  I hope they have a fix soon! 
  • Verified answer
    Expiscornovus Profile Picture
    33,189 Most Valuable Professional on at
     
    In that same thread the root cause and a proposed workaround/solution was posted as well.
     
    The root cause is that Microsoft doesn't allow these type of URLs in the URI field anymore in that type of action, the Send an HTTP request to SharePoint (that is the zip action renamed).
     
    The workaround is to replace the Send an HTTP request to SharePoint by a HTTP with Microsoft Entra ID action or other type of HTTP action which allows these URLs.



    Happy to help out 😁

    I share more #PowerAutomate and #SharePointOnline content on my Blog, Bluesky profile or Youtube Channel

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard