Connecting your Microsoft Dynamics 365 system to Rapidi requires an OData connection. Whether you're integrating Business Central, D365 Finance, or D365 Sales, the process follows the same pattern. Once you understand these steps, you can set up any D365 connection in about five minutes.
In this article, we will explain how to set up a connection for OData Cloud - you will also find the recording of the Open Office Hours 3 session - Connection OData Cloud.
As part of our Open Office Hours series, which are 30-minute live training sessions that we run from January through April, we cover everything from basic setup to advanced configuration.
How to Set Up Dynamics 365 OData Connections in Rapidi: Business Central, Finance & Sales
Quick Summary:
Setting up OData connections between Microsoft Dynamics 365 and Rapidi follows a three-step pattern:
- register an app in Azure,
- configure the app in your ERP,
- and then create the connection in Rapidi.
This guide walks through each step with the specific settings you need.
Watch the Replay of our third session: Connections - Dynamics 365 ODATA Cloud
Before You Start
You'll need access to three systems:
-
First, Azure Portal with permissions to register applications.
-
Second, your Microsoft Dynamics 365 instance (Business Central, Finance, or Sales) with admin access.
-
Third, your Rapidi service account.
The connection process has three main phases: Azure app registration, ERP configuration, and Rapidi connection setup. Each system passes credentials to the next.
Step 1: Register Your App in Azure
1 Create the App Registration
Open the Azure Portal and navigate to App Registrations. Click "New registration" and give your app a descriptive name (something like "Rapidi-Production" or "Rapidi-Test-2026").
Add a redirect URL. This is required for Business Central connections. Use the redirect URL provided in your Rapidi documentation.
2 Set API Permissions
Your app needs permissions to access D365 data. Go to API Permissions and click "Add a permission."
Search for your target system (e.g., Business Central, Dynamics 365 Finance). You need two types of permissions:
Delegated permissions: Select all available permissions under this category.
Application permissions: Click "Add a permission" again, select your system, choose "Application permissions," and select the available options.
After adding both, click "Grant admin consent" so the permissions show as "Granted" (green checkmark).
3 Create a Client Secret
Go to "Certificates & secrets" and click "New client secret." Give it a name and choose an expiration period.
Note on expiration: If you set a short expiration (like 3 months), you'll need to create a new secret before it expires. Rapidi will send error notifications when a secret expires. For less maintenance, choose 18-24 months.
Copy the secret value immediately. This is your password for the Rapidi connection. You can only see it once.
Before leaving Azure, note these values from your app's Overview page:
| Azure Field |
Rapidi Field |
| Application (client) ID |
User ID |
| Directory (tenant) ID |
Domain |
| Client secret value |
Password |
Step 2: Configure Your ERP
For Dynamics 365 Business Central
In Business Central, search for "Microsoft Entra" and open it. Click "New" to create a new application entry.
Paste your Azure Application ID into the Application ID field. Give it a name that matches your Azure app registration. Enable the application.
Add permission sets. At a minimum, you need:
Automation permissions and Admin permissions. Depending on your setup, you may need additional permission sets for specific functionality.
Click "Grant consent" and accept the permissions prompt.
For Dynamics 365 Finance
The process is similar. Register your Azure app in Dynamics 365 Finance, add the Application ID, and assign the required security roles.
For Dynamics 365 Sales
In Dynamics 365 Sales, register the Azure application and assign the appropriate security roles to access the data you need.
Step 3: Create the Connection in Rapidi
Log into your Rapidi service and create a new connection. Select the connection type based on your ERP:
| System |
Connection Type |
| Business Central |
BC Nav OData |
| D365 Finance |
Finance OData |
| D365 Sales |
D365 Sales OData |
Connection Fields Explained
Server/Instance URL: Get this from your ERP's web services. In Business Central, go to Web Services, find a page like Customer Card, and copy the OData URL.
Company: The company name from your ERP instance.
User ID: Your Azure Application (client) ID.
Password: The client secret value you copied from Azure.
Domain: Your Azure tenant ID.
Resource: The base URL of your ERP (the URL up to and including the domain).
Metadata URL: Your OData URL up to "/ODataV4" followed by "/$metadata".
Select "Use SSL" and choose the appropriate authentication method.
Cloud connections: You don't need the Rapidi connector installed for cloud-based systems. If it gets added automatically, you can remove it.
Click "Test" to verify the connection. If successful, you'll see a confirmation message.
Redesign to Load Metadata
After testing, click "Redesign" to read the tables and fields available from your ERP. This loads the metadata so Rapidi knows what data you can access.
OData connections show the number of records and tables available, not specific table names. To verify access, check your ERP's Web Services list. Anything published there will be available through the connection.
Managing Your Connection
When Secrets Expire
When your client secret expires, Rapidi sends error notifications. To fix this:
Go to Azure, open your app registration, and create a new client secret. Copy the new value. In Rapidi, edit your connection and update only the password field with the new secret value. Save and test the connection.
Adding New Tables or Fields
If you add new pages or fields in your ERP, they won't appear in Rapidi automatically. After publishing new pages in Web Services (for Business Central) or making fields visible in your ERP, go to your Rapidi connection and click "Redesign" to refresh the metadata.
If a field doesn't appear after redesigning, check that it's published on the page in your ERP's UI. Fields that exist only in the backend need to be exposed in the front end before Rapidi can read them.
Reusing Apps for Multiple Connections
You can use the same Azure app registration for multiple connections. Create one app in Azure, then use those same credentials when setting up connections to different ERP instances in Rapidi. This saves time and reduces the number of apps you need to manage.
OData vs API Pages
Microsoft is moving from OData pages to API pages in Business Central. Both work with Rapidi. The connection setup process is identical for either type. You can read data, write data, and perform all standard operations regardless of whether you're connecting to OData pages or API pages.
Troubleshooting Common Issues
Connection test fails: Double-check that you've granted admin consent in Azure. Verify the Application ID matches between Azure and your ERP. Confirm the client secret hasn't expired.
Missing tables: In Business Central, check Web Services to confirm the page is published. After publishing, redesign the connection in Rapidi.
Missing fields: Fields must be visible in your ERP's UI. Add the field to the page layout, then redesign in Rapidi.
Permission errors: Review the permission sets assigned to your app in the ERP. Make sure automation and admin permissions are included.
Frequently Asked Questions
What happens when my Azure client secret expires?
You'll receive error notifications from Rapidi. Create a new secret in Azure, copy its value, and update the password field in your Rapidi connection. Test to confirm the fix.
Why can't I see certain tables or fields after connecting?
Tables and fields must be published in your ERP's Web Services before they appear in Rapidi. Publish the missing items, then redesign your connection to refresh the metadata.
Can I use the same Azure app for multiple D365 connections?
Yes. Create one app registration in Azure and reuse those credentials for multiple connections in Rapidi.
Is there a difference between OData and API pages for Rapidi connections?
No functional difference in how you set up the connection. Both page types work the same way with Rapidi.
Next Steps
With your D365 OData connection configured, you can now create transfers to move data between your systems. The connection handles authentication and data access, while transfers define what data moves and when.
Register for next week's session: Connections: Salesforce & HubSpot
If you need to connect Salesforce or HubSpot, those use OAuth authorization rather than Azure app registration, but the overall process in Rapidi follows a similar pattern.
Did you miss the previous sessions? Find the replays for
