Microsoft Dynamics 365 Business Central

Microsoft Dynamics 365 Business Central

This connector works with Business Central online through its standard API v2.0 (https://api.businesscentral.dynamics.com/v2.0/<tenant>/<environment>/api/v2.0): companies, customers, vendors, items, sales quotes and orders, sales and purchase invoices, the general ledger, the chart of accounts, dimensions and employees. Every call runs as the user who authorized the connector, with that user's Business Central licence and permission sets: the AI sees and changes exactly what that user may. Business Central on-premises is not covered (it signs in differently); for older NAV installations use the Dynamics NAV connector.

Setup (one-time, about 10 minutes)

1. Open https://entra.microsoft.com → Applications → App registrations → New registration (or reuse the app of the Outlook, OneDrive or SharePoint connector).
2. Supported account types: Accounts in this organizational directory only is the usual choice.
3. Redirect URI: platform Web, https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself. It must match character for character (AADSTS50011 otherwise).
4. API permissions → Add a permission → Dynamics 365 Business Central → Delegated permissions: tick Financials.ReadWrite.All (and user_impersonation). Then Grant admin consent if your organisation does not let users consent themselves.
5. Certificates & secrets → New client secret; copy the secret Value (shown once).
6. Fill in MICROSOFT_CLIENT_ID (Application ID), MICROSOFT_CLIENT_SECRET (secret value), MICROSOFT_TENANT_ID (the Directory (tenant) ID GUID, or your domain such as contoso.onmicrosoft.com) and BC_ENVIRONMENT, then install.
7. On the connector page click Authorize with Provider and sign in with a Business Central user. The refresh token is stored encrypted and access tokens are renewed automatically.

Tenant and environment are part of every URL. MICROSOFT_TENANT_ID cannot be common or organizations here, because Business Central needs the real tenant in the address. BC_ENVIRONMENT is the environment name exactly as the Business Central admin center lists it: Production for most live tenants, Sandbox or a custom name such as SANDBOX-TEST for sandboxes. A wrong name answers 404; bc_list_environments shows the names (some tenants show it only to administrators). Start with a sandbox when you try the connector: writes in Production create real customers and documents.

Scope: https://api.businesscentral.dynamics.com/Financials.ReadWrite.All offline_access. offline_access makes Microsoft issue a refresh token. Do not add Microsoft Graph scopes to this connector: one token serves one API.

Companies first. Business data lives in a company. Call bc_list_companies and pass its id (a GUID) as company_id to every other tool. Records are addressed by their id GUID too, not by their number: find the id with a list tool and a filter such as number eq '10000'.

Filtering (OData v4)

• filter: displayName eq 'Adatum Corporation', contains(displayName,'Adatum'), startswith(number,'10'), balanceDue gt 0, postingDate ge 2026-01-01 and postingDate le 2026-01-31. Text in single quotes (double a quote inside: 'O''Neil'), dates and GUIDs bare, enum values as text: status eq 'Open'. An enum value with a space is written with _x0020_ in place of the space, as the answers show it: status eq 'In_x0020_Review', category eq 'Cost_x0020_of_x0020_Goods_x0020_Sold'.
• select keeps answers small (id,number,displayName); orderby sorts (postingDate desc); expand adds related data, e.g. salesOrderLines on an order.
• Paging: list tools return top records (default 50, up to 1000). For the next page call again with skip raised by the records already read. Business Central also returns @odata.nextLink past 20,000 rows; use skip instead.

Writing

• bc_create_customer, bc_create_sales_quote and bc_create_sales_order create records; the documents stay open drafts and nothing is released, shipped, invoiced or posted by this connector. A document can take its lines in the same call (lines), or line by line with bc_add_sales_quote_line / bc_add_sales_order_line. A line needs lineType (Item, Account, Resource, Comment), lineObjectNumber (the item number) and quantity; Business Central fills price, description and unit from the item and the customer's price lists unless given.
• bc_update_customer changes only the fields given. Updates carry If-Match: pass the record's @odata.etag from the last read to refuse the change when someone else edited the record meanwhile (412), or leave the default *.
• Confirm customer, items, quantities and prices with the user before creating a document, and every change before updating.

Switched off at install: bc_delete_customer, bc_make_order_from_quote, bc_delete_sales_quote, bc_delete_sales_order. Deleting and converting documents cannot be undone from here; turn these on per tool only if the AI should do that.

Other data: bc_query reads any other API v2.0 resource of a company (contacts, purchase orders, credit memos, shipments, item ledger entries, aged receivables and payables, trial balance, bank accounts, payment terms, currencies, projects) or a nested path such as salesOrders(<id>)/salesOrderLines. Custom APIs published by extensions (/api/<publisher>/<group>/<version>) are not reached by this connector.

Limits: Business Central allows about 6,000 API calls per user in 5 minutes and a few calls at the same time; beyond that it answers 429 with Retry-After. Read with select and filters rather than paging through whole tables.

Common errors

• 401: the authorization was revoked or the client secret expired. Paste a new secret if needed and click Authorize with Provider again.
• 403 or Authorization_InsufficientPermissions: the user lacks a Business Central licence or a permission set for that data, or admin consent for the app is missing.
• 404 NoEnvironment or Not Found: BC_ENVIRONMENT or MICROSOFT_TENANT_ID is wrong, or an id does not exist in that company.
• 400 BadRequest_ResourceNotFound: the resource name in bc_query is misspelled (camelCase plural, e.g. purchaseOrders).
• 412 Request_EntityChanged: the record changed since the etag was read; read it again and retry.
• 400 Internal_RecordNotFound or a validation message: Business Central refused a value (unknown item number, blocked customer, missing posting group in the template).

Microsoft's own MCP server: Business Central also offers an MCP server that exposes API pages chosen by an administrator. This connector uses the standard API v2.0 instead, so it works in every environment without that configuration.