Set Up AAD Application in Azure Portal
To use the ELO Connector with a Business Central SaaS, it must be registered and set up on Azure beforehand.
To do this, open the portal.azure.com page and log in with the correct tenant. In the menu you will find the item Azure Active Directory.
Here you can register new apps in the App registrations section. Create a new app registration with New registration.
Give the app a name, for example SIEVERS ELO Connector. Also make sure that in the Supported account types section, the first option Accounts in this organizational directory only is selected.
After registration, some important data is displayed. Save the Application ID (1) and the Directory ID (2) separately. You will need them later. Then add a Client Secret (3) with Add a certificate or secret. This is necessary for the creation of credentials.
You can enter any name for the description. Then add a date on which the secret should expire.
Achtung
After you have created the Secret, you must copy the Secret-Value immediately and save it separately. Copying is only possible when the value is displayed for the first time.
Then switch to the API Permissions menu.
In the API Permissions, the service must now be authorized to receive data from the Business Central API. To do this, add a new permission with Add a permission.
Then you need to select for which API you want to assign the permission.
Now the authorization is configured. It is an application authorization. In addition, the service should be able to read as well as write. Therefore set the permissions as shown in the following screenshot.
After you save the permission, the permission still needs to be granted admin consent. To do this, select Grant admin consent for Contoso.
Now only the authentication of the service must be enabled. To do this, open the Authentication page via the menu.
Add a Mobile and desktop applications configuration via Add platform (2).
In this configuration, set up the redirect URI
https://businesscentral.dynamics.com/OAuthLanding.htm (3)
Confirm the configuration with Configure (4).
Set the Allow public client flows option to Yes.
The Business Central tenant is now ready to use the SIEVERS ELO Connector.
Enable AAD Application in Business Central
In Business Central, open the Azure Active Directory Applications page and create a new client.
At this point, an ID that you created when setting up the service in Azure comes into play. Enter the client ID in the first field, add a description and switch the State to enabled.
Then assign the user permission sets D365 FULL ACCESS and SIEVERS ELO Con AD to the service.
Wichtig
The listed permission sets represent the standard configuration. Depending on the extensions (customizing) in use or individual records, it may be necessary to assign additional permission sets to the service. If permission errors occur when processing documents or accessing master data, check which additional permission sets are required for the affected objects.
Now the SIEVERS ELO Connector is set up in Azure Portal and enabled in Business Central.