Showing results for 
Search instead for 
Did you mean: 
New Member

Not able to subscribe to WebHook using OAUTH2 Authentication

Hello Team,

We are facing below issues in Power Automate for WebHook subscription. Could you please help us the resolve those.

1) We used OAUTH2 authentication mechanism to Subscribed WebHook, but we getting 401 error.
Upon analysis it was found out that, there is difference in AUD claim in access token generated by Power Automate and what WebHook application expects.
WebHook app expects AUD claim as api://client-id and in Power Automate generated access token, AUD claim is
We also passing scope as api://client-id/.default but still AUD claim is generate as
Please let us know here what we can do to generate proper AUD claim.

2) The flow used in OAUTH2 type is accessCode in Power Automate. We also wanted to try flow as application in OUATH2 type.
So, we added flow as application in Swagger and updated the connector. But, as soon as we update the connector the flow gets defaulted back to accessCode.
Please let us know how we can use flow as application in Power Automate.




Advocate III
Advocate III

Hi @avgode did you ever find a solution to this? I'm having the same problem with my Azure API Management service API. The JWT validation fails because of an audience mismatch, exactly as you described.



Helpful resources

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

New Process Advisor Capabilities carousel.png

Read the blog for the latest news

Read the latest about new experiences and capabilities in the Power Automate product blog.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

Top Kudoed Authors
Users online (3,550)