...
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Snaps in the Microsoft Business Central Snap Pack require an Access Token or OAuth2 account to access the resources in Azure. For the accounts to authorize successfully, ensure to create and configure an application corresponding to the account as displayed in the workflow.
Prerequisites
An Azure account with a free subscription to create the application.
Key Steps in the Workflow
Create an Application in the Azure Portal
Log in to the Microsoft Azure Portal.
Navigate to Azure services > Azure Active Directory Microsoft Entra ID.
Navigate to Add > App registration.
On the Register an application page, specify the name for registering the application and click Register. Learn more about creating an application: https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app.
| Info |
|---|
To use an existing application, navigate to Portal Home > Azure Active Directory >App registrations > All applications. In the search box, specify the application name you want to use. The details of the registered application are displayed display in the search list. |
Define Permissions
The Microsoft Business Central Snap Pack supports the following account types:
The permissions for the registered application are either Delegated or Application based on the account types.
On the left navigation panel, navigate to Manage,andselect API permissions > Add a permission.
.png?version=3&modificationDate=1691056397115&cacheVersion=1&api=v2)
...
On the Request API permissions window, select Microsoft Graph > Dynamics 365 Business Central for the OAuth2 and Access Token Account.
...
...
Select Delegated Permissions or Application Permissions.
...
Select the permissions you require.
...
Click Add Permissions. You can view all the permissions added under Configured permissions.
...
...
Click Overview and select Add a Redirect URI. You will be redirected to the Platform configurations page.
...
...
Under Platform configurations, click Add a platform.
...
...
Select Web and specify
...
the Redirect URI in the following format:
https://<control-plane-name>.snaplogic.com/api/1/rest/admin/oauth2callback/<snap-pack-name>
where the<control-plane-name>corresponds to the domain part of your SnapLogic URL—elastic (global control plane) or emea (EMEA control plane).
For example:https://elastic.snaplogic.com/api/1/rest/admin/oauth2callback/businesscentralhttps://emea.snaplogic.com/api/1/rest/admin/oauth2callback/businesscentral
...
Click Configure. A popup message
...
indicates that the application is successfully updated.
...
On the Platform configurations page, click Save. The Redirect URIs are added to the application.
Configure the Business Central Application
Log in to the Microsoft Business Central application.
Search for aad in the search box.
Navigate to Azure Active Directory Application and select New.
Configure the following fields for the new record:
In the Client ID field, specify the client ID that is generated from the registered application in the Azure Active Directory.
In the Description field, specify a name for the application.
Change the State to Enabled.
In the User Permission Sets, select the ellipsis (…)and select the required Permission Set.
Click on Grant Consent to provide permission to access the Business Central Data.
Specify the Credentials and Validate the Snap Account
To authorize your account in the SnapLogic (R) Platform, you must have the following application credentials:
...
Navigate to the Business Central Snap of your choice and configure the Business Central OAuth2 Account with the details from the registered application in the Business Central Portal.
Click Authorize. The Access and Refresh tokens are generated. You are redirected to the sign-in page of the Azure Portal.
Sign in to Azure Portal with valid credentials to redirect to the Snap Edit account settings dialog. The Access and Refresh tokens are auto-populated and encrypted in the Account settings.Validate the Snap Account.
Troubleshooting
Error | Reason | Resolution |
|---|---|---|
Error 401 | The pipeline could not complete execution because of a connection error. | Reauthorize the account and retry. |
Snap Pack History
| Expand | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Related Content
...