Microsoft Dynamics 365 Business Central
Service ID: microsoft-dynamics-365-business-central
Microsoft Dynamics 365 Business Central is an enterprise resource planning (ERP) system focused on mid & large scale businesses.
At a Glance
- Difficulty
- ⚡MODERATESelf-Service OAuth + Required Per-Consumer Environment & Company Setup
- Authentication
- OAuth 2.0OAuth 2.0 (Authorization Code) via a Microsoft Entra ID app registration.
- Webhooks
- No webhooks — Business Central changes must be polled.
- Partnership Required
- No(No — no partner programme or app review required.)
- Partnership Application
- Developer Portal↗
- Apideck Credentials
- AvailableAvailable for testing — OAuth shows "Apideck" as the requesting application. Production is bring-your-own Entra app.
- Costs
- No Apideck fee. Business Central licence: Essentials $80, Premium $110, Team Members $8 per user/month, billed yearly (list price, varies by region).
- Sandbox Availability
- Available — Access Sandbox↗(Free 30-day trial (fastest route), or up to three sandbox environments included with an active Essentials or Premium subscription.)
- Account Type Required
- Business Central online (SaaS), any edition — on-premises deployments are not supported.
- Consumer Access Level
- Any Business Central user can authorize; a Microsoft Entra admin grants consent once per tenant.
- Rate Limits
- 6,000 requests per user per 5-minute sliding window; 5 concurrent requests per user.
What are Apideck credentials?
For select connectors, Apideck has established partnerships allowing you to integrate immediately without your own partnership. When using Apideck credentials, “Apideck” appears as the requesting application during OAuth. Learn more about partnership categories →
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Register App in Microsoft Entra | ✓ (or use Apideck credentials) | — | Docs provided |
| Grant Admin Consent | — | ✓ (Entra admin) | Docs provided |
| Rotate Client Secret | ✓ (before expiry) | — | — |
| Add Credentials to Apideck | ✓ (or use Apideck credentials) | — | — |
| Authorize Connection (OAuth) | — | ✓ | Handles OAuth flow |
| Select Environment & Company | — | ✓ | Prompts in Vault |
| Build via Unified API | ✓ | — | Maintains connector |
| Token Refresh | — | — | ✓ Automatic |
| Monitor Connections | ✓ Via Apideck Dashboard | ✓ Can revoke anytime | Logs & alerts |
Environments
- Single environment (sandbox and production share the same credential structure)
- Business Central uses one credential structure for both: the Environment the consumer selects during setup (Sandbox or Production) decides which instance is accessed, and there are no separate development credentials. To test, use a free 30-day Business Central trial, a sandbox environment included with an active Essentials or Premium subscription (CRONUS demo data or a copy of production data, created in the Business Central admin center), or a Microsoft Business Central Partner Sandbox license. Per-user rate limits apply in every environment, so take care when testing against a company that holds production data.
🚨Important to Know About Microsoft Dynamics 365 Business Central
- Purchase orders post as header-only documents: line items are accepted on write but never reach Business Central. Reads return line items correctly.
- Posting-group fields (Vendor Posting Group, and the G/L Account Card's posting groups) are not settable through the API: configure them in Business Central — or link a Vendor Template in API Setup — before creating suppliers, bills, or expenses.
- Two silent-breakage traps: an Entra client secret expires after at most 24 months (rotate it, or every connection on that app stops working), and a refresh token expires after 90 days of inactivity, so dormant connections need re-authorizing.
⚠️
27 gotchas across 22 resources
Connector-specific behaviors and limitations to be aware of
📦
21 supported resources
View field mappings, supported operations, and schema details