Dynamics 365 Finance & Operations Guide

Setting up the Dynamics 365 Finance & Operations Integration

To access your users' data from Dynamics 365 Finance & Operations (F&O), you need to enable the integration in the Platforms Page of the Rutter dashboard.

Dynamics 365 F&O uses OAuth 2.0 client credentials (service-to-service) via Microsoft Entra ID (Azure AD). Before a user can connect, the following one-time setup steps must be completed:

  1. Create an Azure AD App Registration in the Azure Portal (App registrations → New registration). Record the Application (client) ID and create a Client Secret under Certificates & secrets. Note that Azure only displays the client secret value once — copy it immediately.

  2. Activate the Dynamics ERP service principal. In the Azure Portal, navigate to Entra ID → Enterprise applications, change the filter to "Microsoft Applications", find Microsoft Dynamics ERP, and set "Enabled for users to sign-in?" to Yes.

  3. Register the app inside Finance & Operations. In your F&O environment, go to System administration > Setup > Microsoft Entra ID applications, add a new row with the Application (client) ID, a name, and the F&O User ID (e.g. Admin) the connection should act as.

User Authentication with Dynamics 365 Finance & Operations

A Rutter Connection is created when your end user authenticates their Dynamics 365 F&O environment via Rutter Link. This in turn allows you to access their account data via the Rutter API.

Rutter Link prompts the user for the following four credential fields:

  1. F&O Environment URL — The URL used to access Finance & Operations in a browser, e.g. https://yourcompany.operations.dynamics.com. The user should paste the full address up to and including .dynamics.com, with no trailing slash.

  2. Azure AD Tenant ID — A GUID identifying the user's Microsoft 365 / Azure organization. Found at portal.azure.com → Entra ID → Overview → Tenant ID.

  3. Azure AD Application (Client) ID — The GUID from the App registration's Overview page (step 1 above).

  4. Azure AD Client Secret — The secret value generated under Certificates & secrets (step 1 above).

Rutter uses these fields to obtain an OAuth 2.0 access token via the client credentials grant against Microsoft Entra ID, then calls the F&O OData API on behalf of the connected environment. No interactive user login is required during or after this setup.

Previous
DualEntry
Next
eBay