Showing results for 
Search instead for 
Did you mean: 
Advocate I
Advocate I

OAuth2 client flow - is it supported in powerapps custom connectors?

Hello All,


When using a custom connector, does PowerApps OAuth2 implementation allow for the client/application flow?


I can use the accessCode flow just fine, but I cannot use the 'client' flow.  Heres the relevant part of my swagger doc:


"securityDefinitions": {
"oauth2": {
"type": "oauth2",
"description": "OAuth2 Application Flow",
"flow": "application",
"tokenUrl": "https://tokenserver/oauth/token",
"scopes": {
"impersonate": "Fully impersonate"

When trying to create this connector, I get the follow error:



Manage your custom connectors | Microsoft Flow

'Parsing error(s): JSON is valid against more than one schema from 'oneOf'. No valid schemas. Path 'securityDefinitions.oauth2', line 147, position 16.'.
Can anyone help?
Thanks for your help in advance,
Community Support
Community Support

Hi @MattDendle,


So far, in PowerApps, authentication mechanism OAuth 2.0 is supported for specific services like Dropbox, Facebook, and SalesForce. I saw an idea submitted in the forum and you can vote there:




Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hello Mona,


Thanks for your reply, but I think it is confusing, and even misleading; Generic OAuth2 is supported for Custom Connectors for use in connecting PowerApps/Flows to custom APIs.  In fact, I have several custom connectors pointing to my custom API using OAuth2 right now.


But my question is more specific than this; of the OAuth2 flows, the accessCode flow works great, but I do not seem to be able to use the client/application flow.


Can anyone confirm if this is supported?




Not applicable

I am getting the same error if I use a FLOW other than IMPLISIT.

In both cases here what is common is that the FLOW is pointing to APPLICATION which is required when the Grant Type is Client Credentials.

I got Swagger validation elswhere!

The request failed with error: 'Parsing error(s): JSON is valid against more than one schema from 'oneOf'. No valid schemas. Path 'securityDefinitions.oauth_2_client_credentials_auth', line 51, position 41.'. The tracking Id is '29510f5e-bcc8-4d0b-a9d4-53e945928d58'.


Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on June 15, 2022 at 8am PDT.

PA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.


New Release Planning Portal (Preview)

Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.

Top Solution Authors
Top Kudoed Authors
Users online (3,830)