On-Prem AIFree templatePDF, Excel, Word exportMicrosoft Dynamics 365 Business Central (on-premises)

Business Central On-Premises Private AI Layer Blueprint Generator

Business Central on-premises exposes a clean API surface, which makes a private AI layer easier than on older systems. This generator turns your environment details into a plan covering APIs, retrieval, model serving, permissions and rollout.

Fill in

Live preview
Download:

Business Central On-Prem Private AI Layer Blueprint Generator

Business Central Private AI Layer Plan: Ridgeway Fabrication Ltd

System: 2021 to 2023 releases (18 to 22) on SQL Server 2019, hosting: On-prem server. Scale: 120 named users, 3 companies or plants. Target go-live: Q2 2027.

Context

Sales order and shipment status, item availability and reorder questions, vendor payment status, production order lookups, search of attached quotes and drawings.

Goal: a natural-language assistant over Business Central data and documents that runs wholly within Ridgeway Fabrication Ltd infrastructure.

Components

ComponentDesignNotes
Data access pathAPI v2.0 for standard entities; custom API pages in AL for gaps; OData web services where already publishedPreferred over SQL for anything user-visible
Bulk readsRead-only SQL replica for aggregates, validated against the applicationTables are per company and carry app ids
Retrieval indexAttachments, notes, external documents, with incremental refresh on modified datesLocal vector store
Model servingOpen-weight model via vLLM or Ollama, GPU: One 48 to 80 GB class GPUPlan for model updates
Tool serverMCP server with named read actions, parameter validation and row limitsNo free-form query generation against production
Identity and permissionsDelegate user identity to API calls or enforce permission set filters in tool codeTest with low-privilege users
AuditLocal log of question, endpoint, parameters, answer, approverRetain per policy

Security controls

RequirementControl
Never leaves site: Pricing, customer contracts, bank data, controlled technical data.No external APIs; inference, index and logs inside the On-prem server boundary; blocked egress
TransportTLS on the server instance and tool server; certificates managed by IT
PermissionsBusiness Central permission sets honoured through delegated identity or equivalent filters
Write-backDrafts only, human approval, POST through API
TraceabilityEach answer cites the API call or view behind it

Three-phase rollout

PhaseScopeExit criteria
1. Read-only questionsPilot group, standard APIs, document searchAgreed test set answered correctly; permissions verified
2. DraftsDraft quotes, purchase orders and notes for reviewLow rework rate
3. Approved actionsFew write actions through API with approvalAudit log reviewed by IT and finance

Open questions for IT

1. Which authentication method is configured on the server instance? 2. Which extensions add tables or fields users ask about? 3. Who can write and deploy custom API pages in AL? 4. Are API rate or resource limits a concern at peak? 5. Is a readable SQL replica available for aggregates? 6. Which Copilot or cloud features, if any, are available on this deployment and permitted?

Prepared by / Date
IT architect / Date
Business owner / Date
Security reviewer / Date

A starting plan. Check API availability, authentication options and extension behaviour for your Business Central build.

Get an expert review of your Business Central AI blueprint

Optional: send the exported plan for comments on API design, permissions and sequencing.

Optional. The tool and every export work without this. No spam.

How to use the generator

Pick your Business Central release and database version, then list the use cases and the data that must stay on site. The output names the access path per question type, the tool server design, security controls and an open-questions list for your IT and AL developers.

  • Know your authentication method
  • List extensions with custom tables
  • Decide delegation versus a service identity
  • Export and review with security

The design behind the plan

The plan uses API v2.0 and custom API pages for reads that must match what users see, a replica for aggregates, an index for documents and a local open-weight model. Permissions come from the calling identity, which is the main advantage of API-based access over SQL.

Common mistakes

Using a broad service identity without per-user filtering, treating SQL columns as equal to API fields, pulling large sets through paged APIs and assuming cloud Copilot features exist on-premises. The plan lists each as a control or an open question.

Frequently Asked Questions

Can I use this for Business Central online?

It is written for on-premises. An online tenant has different networking, authentication and data residency considerations.

Why prefer APIs over SQL?

APIs apply business logic and the caller's permissions. SQL reads raw tables, which are per company and may omit calculated values.

Does it need AL development?

Only if the standard API does not expose the data you need. Then a custom API page is the supported way to add it.

Is data stored by this tool?

No. The document is generated locally in your browser.

If you would like help checking this plan against your extensions and server setup, Netray can review it with your team.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Comparisons

Software