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 https://apihub.azure.com.
We also passing scope as api://client-id/.default but still AUD claim is generate as https://apihub.azure.com.
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.
Thanks,
Amey
Is there a solution for this yet?
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.
Thanks,
Greg