Microsoft Dynamics 365 Business Central v2 connector prerequisites

Introduction

As the Microsoft Dynamics 365 Business Central v2 connection will be an application that interfaces with Microsoft, you will need to register an application using Microsoft Entra ID with a specific set of permissions.

Microsoft Azure app registration steps

Follow these steps to create an app registration with the Microsoft identity platform:

1. In the Azure portal, search for and click Microsoft Entra ID (previously known as Azure Active Directory or Azure AD):

   

2. In the left sidebar under Manage, click App registrations.

3. Click New registration:

   

4. Enter a Name for your app. This display name will be visible to users:

   

5. Click Register to complete the app registration. You are then directed to the app's Overview page:

   

   Important

   Retain the app registration's Application (client) ID and Directory (tenant) ID to use as client_id and tenant_id when configuring a connection.

6. Click Add a certificate or secret.

7. In the Client secrets tab, click New client secret to open the Add a client secret pane. In this pane, enter a description and select an expiration date for the client secret, then set, click Add:

   

8. The client secret is now visible in the Client secrets tab. Retain it if you want to configure a connection using the Client Credentials grant type.

Add required permissions to the app registration

Your app registration must have a specific set of permissions.

In the Azure portal, navigate to your app registration and click API permissions in the left sidebar:

These are the permissions you will need to set:

• Dynamics 365 Business Central application permissions
• Dynamics 365 Business Central delegated permissions
• Microsoft graph delegated permissions

Dynamics 365 Business Central application permissions

To add Dynamics 365 Business Central application permissions, follow these steps:

1. On the API permissions page, click Add a permission.

2. In the Request API permissions pane, click the APIs my organization uses tab, search for and click Dynamics 365 Business Central:

3. Click Application permissions.

4. Enable the AdminCenter.ReadWrite.All, API.ReadWrite.All, app_access, and Automation.ReadWrite.All permissions.

5. Click Add permissions. The updated app registration's Configured permissions page is shown.

Dynamics 365 Business Central delegated permissions

1. On the API permissions page, click Add a permission.

2. In the Request API permissions pane, click the APIs my organization uses tab, search for and click Dynamics 365 Business Central:

3. Click Application permissions.

4. Enable the Financials.ReadWrite.All and user_impersonation permissions.

5. Click Add permissions. The updated app registration's Configured permissions page is shown.

Microsoft graph delegated permissions

1. On the API permissions page, click Add a permission.

2. In the Request API permissions pane, click the APIs my organization uses tab, search for and click Microsoft Graph:

   

3. Click Application permissions.

4. Enable the Financials.ReadWrite.All and user_impersonation permissions.

5. Click Add permissions. The updated app registration's Configured permissions page is shown.

The following table summarizes the minimum set of required permissions.

Once you have added these permissions, click Grant admin consent to complete the registration. Once completed, each permission should have a green checkmark.

Link the application

Next, you need to link your application to Dynamics 365 Business Central. Follow these steps:

1. Access the following URL, making the necessary replacements: https://businesscentral.dynamics.com/{tenant_id}/{env}

2. Log in.

3. Under Search Azure Active Directory, click on New. Add your application's client_id and add a description (mandatory).

4. Under User Groups, use the dropdown to select the permission you want to grant. Jitterbit recommends D365 BUS FULL ACCESS, but the minimum acceptable is D365 COMPANY HUB.

Publish objects as web services

Business Central objects must be published as Web Services in order to be accesible via the connector. To accomplish this, follow the steps outlined in the Microsoft documentation.