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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / AuthorizationFailed wh...
Power Apps
Answered

AuthorizationFailed when calling a Logic App Http trigger from Power Automate

(0) ShareShare
ReportReport
Posted on by 99

Hi,

I have a logic app triggered by HTTP, it works fine from Postman but when i try to call it from a Power Automate flow I get this http 401 error :
{
"error": {
"code": "AuthorizationFailed",
"message": "Vous n’êtes pas autorisé à effectuer l’action « run Â» sur l’étendue « /triggers/manual/paths/ Â». Vérifiez que votre demande utilise la méthode HTTP appropriée. Pour plus de détails, voir http://aka.ms/logic-trigger."
}
}

Categories:
I have the same question (0)
  • ChrisPiasecki Profile Picture
    6,422 Most Valuable Professional on at

    Hi @spaillasse,

     

    What kind of security do you have on the Logic App, SAS signature or Azure AD OAuth2? If using SAS, did you ensure to include it as part of the request url? 

     

    Have you considered exporting the Logic App as a Custom Connector and calling the connector in your Power Automate flow instead?

     

    ---
    Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

  • spaillasse Profile Picture
    99 on at

    Hi @ChrisPiasecki,

    The security is SAS signature (I'm using the url generated by the logic app which includes the SAS token) and it's working fine with Postman.

    I add screenshot of the query working in Postman but not in Automate.

    I'll take a look at the export as a Custom Connector, but still I think there is an issue with Automate.

    2022-03-16 15_16_08-Historique des exécutions _ Power Automate et 6 pages de plus - Travail – Mi.png
    2022-03-16 15_13_46-Postman.png
  • Verified answer
    spaillasse Profile Picture
    99 on at

    Ok got the solution.

    In the Queries section of the HTTP action, I realized the value of the "sp" parameter was wrong: "%2Ftriggers%2Fmanual%2Frun" instead of "/triggers/manual/run"

    Now it's working

  • ChrisPiasecki Profile Picture
    6,422 Most Valuable Professional on at

    Hi @spaillasse,

     

    You beat me to it, I was going to suggest to try using unencoded value in your body parameter. Glad it worked.

     

    ---
    Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 549 Most Valuable Professional

#2
Kalathiya Profile Picture

Kalathiya 225 Super User 2026 Season 1

#3
Haque Profile Picture

Haque 224

Last 30 days Overall leaderboard