Overview

Pre-built tooling

Pre-built integrations

No pre-built integration yet (time to contribute: <48h)

Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
Paid dev account✅ Not requiredFree, self-signup for a Microsoft account and Azure account.
Paid test account✅ Not requiredFree Microsoft account can be used for testing.
Partnership✅ Not required
App review⚠️ ConditionalRequired only if you want to publish your app to the Microsoft commercial marketplace or if your app needs admin consent for certain permissions.
Security audit✅ Not required

Setup guide

No setup guide yet.

Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
TopicLinks
GeneralMicrosoft Entra Admin Center
Azure Portal
DeveloperMicrosoft identity platform documentation
How to register an Application
OAuth related documentation
Microsoft Authentication Libraries (MSAL)
Microsoft Business Central REST API documentation
Contribute useful links by editing this page

Common Permissions

PermissionDescription
Financials.Read.AllRead all financial data (no user sign-in required)
user_impersonationAccess as the signed-in user
AdminCenter.ReadWrite.AllFull access to Admin Center API
Automation.ReadWrite.AllFull access to automation
API.ReadWrite.AllFull access to web services API

API gotchas

  • See particularly the tenantId parameter under Get a token.
  • This tenantId parameter must be provided as extra configuration to the frontend SDK.
  • When requesting Application Permissions that require admin consent, an Microsoft Entra ID administrator must pre-authorize the permissions. Without admin consent, the app cannot obtain tokens for those scopes.
  • For multitenant applications, each tenant administrator must grant consent to the app’s required permissions before access is granted in their tenant.
  • The .default scope is a special scope that tells Azure AD to issue a token containing all the Application Permissions that have already been granted (consented) for your app on that resource. Using .default ensures your app receives permissions consistent with those configured and consented at the tenant or organization level.
  • The .default scope can’t be combined with the scopes registered in the Azure portal. So either just use the .default scope or remove it to list out explicit parameters that are required. If you attempt to combine them you’ll receive the following error
.default scope can't be combined with resource-specific scopes
  • No user interaction is involved when using the Microsoft Business Central provider. Therefore, a Microsoft Entra ID administrator must grant consent for the required Application Permissions ahead of time. This can be done through the Azure Portal or by using the admin consent endpoint.
    Contribute API gotchas by editing this page

Going further

Connect to Microsoft Business Central

Guide to connect to Microsoft Business Central using Nango Connect UI.