OAuth requires the authenticating user to interact with Dynamics 365 using the browser. The connector facilitates this in various ways as described below.

Embedded Credentials

Desktop Applications

See Embedded Credentials to connect with the connector's embedded credentials and skip creating a custom OAuth app.

Headless Machines

See Headless Machines to skip creating a custom OAuth app and authenticate an application running on a headless server or another machine where the connector is not authorized to open a browser.

Custom Credentials

Instead of connecting with the connector's embedded credentials, you can register an app with Custom Credentials to obtain the OAuthClientId and OAuthClientSecret.

When to Create a Custom OAuth App

Desktop Applications

Creating a custom OAuth app is optional as the connector is already registered with Dynamics 365 and you can connect with its embedded credentials. You might want to create a custom OAuth app to change the information displayed when users log into the Dynamics 365 OAuth endpoint to grant permissions to the connector.

Headless Machines

Creating a custom OAuth app is optional to authenticate a headless machine; the connector is already registered with Dynamics 365 and you can connect with its embedded credentials. In the headless OAuth flow, users need to authenticate via a browser on another machine. You might want to create a custom OAuth app to change the information displayed when users log into the Dynamics 365 OAuth endpoint to grant permissions to the connector.

Creating a Custom OAuth App

See Creating a Custom OAuth App for a procedure.