Trusted by winning dev teams
Sync data with Microsoft Busniness Central
Unified. Reliable. Secure.
Microsoft Dynamics 365 Business Central is a cloud ERP platform used by SMBs across more than 160 countries. It covers financial management, supply chain, sales, project management, and manufacturing. The API is OData v4-based, runs on Azure Active Directory OAuth 2.0, and requires both a Tenant ID and an Environment Name in every request URL. It supports multiple company environments per tenant, each with its own Company ID.
Integrate Business Central alongside dozens of other accounting and ERP systems through Maesn Unified API.
Tenant ID, Environment Name, and Company ID: Three Context Values Required Before Any Data Request
Every Business Central API request URL must include the Azure AD Tenant ID, the environment name (e.g. Production or Sandbox), and the Company ID. None of these can be assumed as defaults in a multi-tenant SaaS context. Maesn resolves all three identifiers during onboarding, stores them per tenant, and constructs the correct URL for every request automatically.
Azure AD App Registration Required: Service-to-Service Auth With Permissions Per Environment
Business Central integrations require an Azure Active Directory app registration with the correct API permissions, and the app must be explicitly enabled in each Business Central environment by an administrator. Standard user credentials or Web Service Access Keys are retired for SaaS. Maesn manages the AAD OAuth flow and handles the environment-level permission model as part of its unified authentication setup.
OData v4 With Wave-Based Schema Changes: Breaking Changes Released Twice Per Year
Business Central's OData API evolves through Microsoft's twice-yearly release waves, which can introduce field renames, entity changes, and deprecated endpoints. Integrations built against one wave version may break after an upgrade. Maesn maintains its Business Central connector against current API versions, absorbing wave-based changes so your integration remains stable without code updates on your side.
"Adding Qonto to our existing integrations was a piece of cake with Maesn. It is a game changer for our customers with all the integration cababilites!"
Juri Preis
CEO @ Smarta
Learn more about Microsoft Business Central API Integration
The Maesn difference
Built faster and sell more with Maesn
Stop keeping your engineers busy with building one integration after the other. Focus on your core value: Your product.
Focus on your core product
Engineering focus
Enable your sales team to have what your leads want. Launch a portfolio of integrations in days, not quarters. Accelerate your sales.
Stop losing deals due to integrations
Sales enablement
Integrations reduce churn - dramatically. Increase your customer satisfaction with end-to-end integration to all relevant systems.
Tie your customers for ever
Higher customer retention
Integrate with
Maesn API
Production
approval
Integration
App
Why companies choose Maesn
3 Reasons Why It Is Better To Integrate Microsoft Business Central API With Maesn
Secure & Compliant
We have a strong relationship to Microsoft Business Central. This ensures that the Maesn API is always up-to-date and any maintenance is covered on our end.
Common Data Model
We provide a clean, unified data model that abstracts away system-specific quirks, so teams can build reliable integrations without dealing with ERP-specific complexity or workaround-heavy implementations.
Microsoft Business Central Sandbox
We provide you with everything you need, so you can focus on what counts.
Business Central is a cloud ERP platform for SMBs available in more than 160 countries. It covers financial management, supply chain, project management, sales, and manufacturing. The API is OData v4-based and uses Azure Active Directory for authentication.
The main challenges are constructing the correct request URL with Tenant ID, Environment Name, and Company ID; setting up Azure AD app registration with correct permissions; ensuring the app is enabled in each customer's BC environment; managing OData v4 query complexity; and handling breaking changes introduced by Microsoft's twice-yearly release waves.
The Tenant ID is the Azure Active Directory identifier for the Microsoft 365 tenant that owns the Business Central environment. The Company ID is the identifier for a specific company within that environment. A single tenant can have multiple environments, and each environment can contain multiple companies. All three values must appear in the API request URL.
Microsoft releases two major waves per year that can include field renames, new required fields, deprecated endpoints, and other breaking changes. Integrations built against older API versions may return errors or missing data after an upgrade. Maesn maintains its Business Central connector proactively against current versions.
Business Central integration requires Azure AD app registration, resolving and storing Tenant ID and Company ID per tenant, constructing complex OData v4 URLs, managing wave-based breaking changes twice per year, and ensuring correct permissions per environment. Maesn handles all of this through a single unified API.
Frequently Asked Questions About Microsoft Business Central Integration
