OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Structured read interface for the declared product and resources
Get customers ↗
Structured read interface for the declared product and resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Repeatable current-state collection retrieval within the declared employee/customer and permission scope; whole-product recovery remains unverified.
Using service-to-service authentication ↗
Calling API and web services; entityName=customers and Get entities GET companyUrl/entityName · Checked 2026-10-16
OData/API web service client performance ↗
Using server-driven paging; REST APIs and queries/pages/codeunits exposed as OData endpoints · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
S2S sample; customer $filter and collection retrieval
Using service-to-service authentication ↗
S2S sample; customer $filter and collection retrieval · Checked 2026-10-16
Access cost barrier -
-
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved
Using service-to-service authentication ↗
Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Register Entra app; grant consent; enable app and assign permissions, including partner apps
Using service-to-service authentication ↗
Register Entra app; grant consent; enable app and assign permissions, including partner apps · Checked 2026-10-16
Downstream permission -
-
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established
Using service-to-service authentication ↗
Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
POST /companies({id})/customers
Create customers ↗
POST /companies({id})/customers · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Customer application uses the documented authorization route
Using service-to-service authentication ↗
Customer application uses the documented authorization route · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Webhook subscriptions for supported API resources
Working with webhooks ↗
Webhook subscriptions for supported API resources · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Online operational limits and throttling responses
Operation limits online ↗
Online operational limits and throttling responses · Checked 2026-10-16
CDC and deletion capture -
-
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Resource notifications reviewed; full declared update/deletion coverage and gaps remain unresolved
Working with webhooks ↗
Resource notifications reviewed; full declared update/deletion coverage and gaps remain unresolved · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Repeat the company-scoped customers collection with server-driven paging to rebuild permitted current customer records. This does not restore deleted customer payloads, intermediate edits, whole-company history or expired webhook notifications.
Using service-to-service authentication ↗
Calling API and web services; entityName=customers and Get entities GET companyUrl/entityName · Checked 2026-10-16
OData/API web service client performance ↗
Using server-driven paging; REST APIs and queries/pages/codeunits exposed as OData endpoints · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Customer-held structured API records within the declared resource scope
Get customers ↗
Customer-held structured API records within the declared resource scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Applicable post-cancellation retrieval clause not established by reviewed technical documentation
Using service-to-service authentication ↗
Applicable post-cancellation retrieval clause not established by reviewed technical documentation · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified
Get customers ↗
Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Customer integration code can run outside the provider; native workflow authoring not established
Using service-to-service authentication ↗
Customer integration code can run outside the provider; native workflow authoring not established · Checked 2026-10-16
Rights to custom logic -
-
Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded.
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved
Using service-to-service authentication ↗
Ownership and reusable export or independent execution of native workflow artifacts remain unresolved · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Register an Entra application, grant API permissions and enable the app in Business Central with object permissions. Microsoft documents partner-created apps; a customer administrator grants access rather than relying on Marketplace discovery.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The v2 customer API returns records and relationships, including financial details when expanded. S2S examples enumerate company customer collections and support OData filtering; online and on-premises prerequisites differ.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Microsoft Dynamics 365 Business Central scoped API access | OAuth client credentials | Customer | No | Customer-supplied credentials | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Licensing still governs non-interactive access. The reviewed technical guidance does not establish the minimum paid license or all access-specific charges; unrelated Dynamics 365 products cannot supply that entitlement.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Create Customer documents POST to the selected company’s customers collection. Custom API creation exists as a separate platform capability; this review credits only the verified customer operation.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Webhooks require a validation handshake and subscription renewal. Delegated-admin changes have a notification caveat, so a subscription is not evidence that every mutation is independently delivered. Repeat the company-scoped customers collection with server-driven paging to rebuild permitted current customer records. This does not restore deleted customer payloads, intermediate edits, whole-company history or expired webhook notifications.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Resource notifications reviewed; full declared update/deletion coverage and gaps remain unresolved | Working with webhooks ↗Resource notifications reviewed; full declared update/deletion coverage and gaps remain unresolvedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Repeat the company-scoped customers collection with server-driven paging to rebuild permitted current customer records. This does not restore deleted customer payloads, intermediate edits, whole-company history or expired webhook notifications. | Using service-to-service authentication ↗Calling API and web services; entityName=customers and Get entities GET companyUrl/entityNameChecked 2026-10-16 OData/API web service client performance ↗Using server-driven paging; REST APIs and queries/pages/codeunits exposed as OData endpointsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customer API records can form an external copy before cancellation. An API record export does not include an entire environment, executable AL extensions or all attachments and accounting history.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Applications can run external rules against company APIs. This scoped review does not establish native AL artifact ownership, reusable export or execution outside Business Central (product-family portability is not assumed).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Structured read interface for the declared product and resources | Get customers ↗Structured read interface for the declared product and resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Repeatable current-state collection retrieval within the declared employee/customer and permission scope; whole-product recovery remains unverified. | Using service-to-service authentication ↗Calling API and web services; entityName=customers and Get entities GET companyUrl/entityNameChecked 2026-10-16 OData/API web service client performance ↗Using server-driven paging; REST APIs and queries/pages/codeunits exposed as OData endpointsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. S2S sample; customer $filter and collection retrieval | Using service-to-service authentication ↗S2S sample; customer $filter and collection retrievalChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Register Entra app; grant consent; enable app and assign permissions, including partner apps | Using service-to-service authentication ↗Register Entra app; grant consent; enable app and assign permissions, including partner appsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolved | Using service-to-service authentication ↗Reviewed entitlement documentation; minimum eligible plan and fixed route-specific access charges remain unresolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Reviewed access documentation; applicable downstream processing, AI and redistribution terms not established | Using service-to-service authentication ↗Reviewed access documentation; applicable downstream processing, AI and redistribution terms not establishedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. POST /companies({id})/customers | Create customers ↗POST /companies({id})/customersChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Customer application uses the documented authorization route | Using service-to-service authentication ↗Customer application uses the documented authorization routeChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Webhook subscriptions for supported API resources | Working with webhooks ↗Webhook subscriptions for supported API resourcesChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Online operational limits and throttling responses | Operation limits online ↗Online operational limits and throttling responsesChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Customer-held structured API records within the declared resource scope | Get customers ↗Customer-held structured API records within the declared resource scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Applicable post-cancellation retrieval clause not established by reviewed technical documentation | Using service-to-service authentication ↗Applicable post-cancellation retrieval clause not established by reviewed technical documentationChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Customer integration code can run outside the provider; native workflow authoring not established | Using service-to-service authentication ↗Customer integration code can run outside the provider; native workflow authoring not establishedChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Microsoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Ownership and reusable export or independent execution of native workflow artifacts remain unresolved | Using service-to-service authentication ↗Ownership and reusable export or independent execution of native workflow artifacts remain unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMicrosoft Dynamics 365 Business Central online API v2.0 / company-scoped customers through Microsoft Entra service-to-service grants and supported webhooks; other Dynamics products are excluded. Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverified | Get customers ↗Structured resource records can be retrieved; complete attachments, versions, relationships and native configuration remain unverifiedChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Lowest eligible plan and fixed API access fees
- Applicable downstream-use and customer cancellation terms
- Complete file, history and configuration recovery
- Native workflow artifact ownership and independent execution
- Complete declared update and deletion identity coverage
- Retained replay, checkpoints and gap-recovery procedure
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.