Configure an OAuth 2.0 provider for portals


Effective October 12, 2022, Power Apps portals is Power Pages. More information: Microsoft Power Pages is now generally available (blog)
We will soon migrate and merge the Power Apps portals documentation with Power Pages documentation.

To use OAuth 2.0–based external identity providers, you register an application with a third-party service to obtain a client ID and client secret pair. Often this application requires that you specify a redirect URL to allow the identity provider to send users back to the portal (the relying party). The client ID and client secret are configured as portal site settings to establish a secure connection from the relying party to the identity provider. The settings are based on the properties of the MicrosoftAccountAuthenticationOptions, TwitterAuthenticationOptions, FacebookAuthenticationOptions, and GoogleOAuth2AuthenticationOptions classes.

To learn about individual OAuth 2.0 providers, select the name of the provider that you want to configure:


  • Custom OAuth providers aren't supported. For custom OAuth providers, use OpenID Connect instead. Changes to the authentication settings might take a few minutes to be reflected on the portal. Restart the portal by using portal actions if you want the changes to be reflected immediately.

For general settings applicable to all OAuth 2.0 providers, go to Configure additional settings for OAuth 2.0 providers.