Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,220 questions
Troubleshooting Azure Logic App OAuth Claims Error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 50%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
SteveAtMSLearning
25
Reputation points
An existing Azure app registration with a client ID and secret was created earlier this year. There is a consumption Logic App with an "HTTP Request is Received" trigger that is activated from Postman. OAuth policy has been enabled in the Azure portal for the Logic App, and the HTTP request behaves as expected for valid and invalid bearer tokens.
A new Azure app registration and a new consumption Logic App were created, copied from the first Logic App, but using the new client ID and secret.
When posting to the new Logic App from Postman, the following error is received:
"code": "MisMatchingOAuthClaims",
"message": "One or more claims either missing or does not match with the open authentication access control policy."
The app registrations appear the same in the Azure portal, yet they exhibit different behavior. How can the issue with the second app registration be diagnosed?
Sign in to answer