---
title: "Connect Microsoft Dynamics 365 Finance & Operations to Rig — Rig guide"
description: "Connect Dynamics 365 Finance & Operations to Rig with an Entra app registration, and sync accounts, customers, orders, invoices and journals."
canonical: "https://rig.so/guides/connect-dynamics-365-finance-operations"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Microsoft Dynamics 365 Finance & Operations to Rig

Rig reads the OData data entities in your Finance & Operations environment, so ledger journals, sales and purchase orders and invoices sit in your warehouse beside the rest of your data. It signs in as an Entra app registration that you map to an F&O user.

## Before you start

- You need to be able to register an app in Microsoft Entra ID and to open **System administration** in Finance & Operations.
- Pick or create an F&O user for Rig to act as. That user's security roles decide what Rig can read, so give it read access to the entities you want and nothing more.
- Have your environment address to hand, for example `https://acme.operations.eu.dynamics.com`.

## Step 1: Register an app in Entra

1. In the Microsoft Entra admin center, register a new application. Microsoft's guide to registering an external application with Finance & Operations is linked under the documentation heading below.
2. On the app's **Overview** page, copy the **Application (client) ID** and the **Tenant ID**.
3. Under **Certificates & secrets**, create a client secret and copy its value straight away. Entra shows it once.

## Step 2: Register the app in Finance & Operations

1. In Finance & Operations, go to `System administration` → `Setup` → `Microsoft Entra applications` and select `New`.
2. In **Client Id**, enter the application ID from Entra. Give the record a **Name**.
3. In **User ID**, choose the F&O user Rig should act as. Microsoft recommends a dedicated service account with only the permissions the work needs.
4. Select `Save`.

The user sets the ceiling
If the mapped user's roles are narrowed later, F&O can answer with an empty list. Rig then fails the run and keeps the table it already has.

## Step 3: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **Microsoft Dynamics 365 Finance & Operations**, open the card and click `Connect`.
3. **F&O environment URL**: your environment address, such as `https://acme.operations.eu.dynamics.com`. Leave off the trailing slash and any `/data` suffix.
4. **Entra tenant ID**: the Tenant ID from the app's Overview page in the Entra admin center.
5. **App registration client ID**: the application (client) ID, the same one you registered in F&O.
6. **App registration client secret**: the secret value you copied from Certificates & secrets.
7. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
8. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

Microsoft Dynamics 365 Finance & Operations lands in its own `dynamics_fno` schema in your warehouse:

- **Company and ledger**: legal entities, main accounts and exchange rates.
- **Customers and vendors**: customers, vendors and released products.
- **Orders**: sales order headers and lines, and purchase order headers and lines.
- **Invoices**: free text invoice headers and lines, and vendor invoice headers and lines.
- **Journals and transactions**: ledger journal headers and lines, customer transactions and customer open transactions.

Choose the streams you want when you connect. Each stream carries every legal entity, with the entity code in its key.

## Good to know

- F&O entities expose no modified timestamp, so every stream is read in full on each sync and replaces the table. A row deleted in F&O disappears from the warehouse on the next sync.
- These are data entities, which join several tables, so they do not map one to one onto raw F&O tables. If your tenant also uses Link to Microsoft Fabric, that route lands raw tables, and this connector suits entity-shaped reads.
- This connector reads Finance & Operations. Customer relationship data in Dataverse has its own Dynamics 365 connector.
- To disconnect Microsoft Dynamics 365 Finance & Operations, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Review the ledger across legal entities
- Follow orders from sales and purchasing
- Chase invoices and open receivables
- Convert amounts with stored exchange rates

[More ideas for using Microsoft Dynamics 365 Finance & Operations](https://rig.so/integrations/dynamics-365-finance-operations)

## Microsoft Dynamics 365 Finance & Operations documentation

- [Service endpoints overview, including registering an external application](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/services-home-page)
- [OData in Finance & Operations](https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/odata)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-dynamics-365-finance-operations)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
