VantegrateNative API integrationIntegrate Business Central with AI agentsthat take orders beyond the inbox
Vantegrate's AI agents connect to Business Central through API v2.0 with a Microsoft Entra ID app: they quote and enter sales orders from WhatsApp, SMS or web chat, process vendor invoices, answer business questions and log each conversation in Salesforce. They work alongside Microsoft's Sales Order Agent, which handles email, and your data stays in your Business Central environment.
How the data flows
What does it mean to integrate Business Central with Vantegrate's AI agents?
Integrating Business Central with Vantegrate's AI agents means that an agent, such as the sales agent that answers customers on WhatsApp, SMS or web chat, works on your ERP through Microsoft's API v2.0: it checks items, availability and prices, creates the sales quote or order and logs every conversation. It authenticates with Microsoft Entra ID as an application, with the permission sets you assign.
It doesn't compete with the Sales Order Agent that Microsoft includes in Business Central, which processes orders that arrive by email. It adds the channels where your customers write (WhatsApp, SMS and web chat) and Salesforce, if that's where your sales team works. Your business data stays in your Business Central.
What do you want to connect to your Business Central?
Pick what you need and we'll write the message for you.
1 · Pick what to solve
2 · What our team receives
Vantegrate
online
What data moves between Vantegrate and your Business Central
The agent works with Business Central's standard APIs in real time: it reads to answer and records every document in the right company.
Items, customers and availability
The agent reads items, customers and inventory to answer whether something is available and at what price, from the same data your team sees in Business Central.
Sales quotes and orders
When the customer confirms, the agent creates the quote or the order through the API, following the rule you set, and ties the conversation to the customer.
Changes through webhooks
With webhook subscriptions, Business Central notifies the agent when an order, a customer or an item changes, and the agent reads the updated record.
How the integration works, step by step
Vantegrate handles the setup and rollout. Your team authorizes, validates and starts using it.
An app in Microsoft Entra ID
We register an app in your Microsoft Entra ID with Business Central's application permission and authenticate it with the OAuth 2.0 client credentials flow, without anyone's personal account.
Least-privilege permission sets
In Business Central, the app gets only the permission sets it needs to read items and customers and create quotes and orders. Microsoft doesn't allow the SUPER permission set for apps.
Subscriptions and rules
We create the webhook subscriptions and load your rules: which channel the agent handles, when it hands off to a rep and what stays with Microsoft's Sales Order Agent.
Validation with real data
We test in a Business Central sandbox with your items and customers, validate with sales, finance and IT, and roll out in phases.
The agents Business Central already includes, and what Vantegrate adds
Business Central includes a Sales Order Agent that monitors a Microsoft 365 mailbox, matches the customer by email address, checks inventory and replies with a PDF quote that later becomes an order (Microsoft Learn). Microsoft lists it as generally available and bills it in Copilot Credits (Microsoft Learn). Email is a sensible home for it: Microsoft 365 ranks #1 by number of customers in Okta's Businesses at Work report (Okta, 2026).
Its channel is the inbox, and a person on your team approves every message before it goes out. When customers order over WhatsApp, SMS or your website chat, that order never reaches the mailbox, and that's where Sellium works: it checks the same Business Central, builds the quote, enters the order and logs the conversation in Salesforce. The Microsoft 365 mailbox stays with Microsoft's agent.
Vendor invoices follow the same logic. Microsoft's Payables Agent processes PDF invoices that arrive by email, up to 100 emails and 500 invoices a day, and leaves unposted drafts for review (Microsoft Learn). Arconte covers what falls outside that mailbox: delivery notes, customer purchase orders, phone photos and Spanish-language invoices, entered as purchase invoices through the API.
| Dimension | Business Central's Sales Order Agent | Sellium on Business Central |
|---|---|---|
| Inbound channel | A Microsoft 365 mailbox | WhatsApp, SMS, web chat and Instagram |
| Customer matching | By the email on the contact card | By the phone number or chat details |
| Document it creates | Always a quote first, then the order | A quote or an order, per your rule |
| Human review | A person approves every outgoing message | Hands off to a rep when your rule says so |
| Where the conversation lives | In the mailbox and in Business Central | In Salesforce or in Business Central |
Channel comparison based on Microsoft's documentation; which agent handles what is defined with your team during discovery.
No overlap: we define which channel each agent handles and which document it creates, so the same order never comes in through email and WhatsApp at once.
API v2.0, Microsoft Entra ID and webhooks: how it connects
Business Central's API v2.0 is REST on OData v4, and Microsoft calls its API stack the preferred way to integrate (Microsoft Learn). For an agent that runs without a person signing in, Microsoft documents service-to-service authentication: a Microsoft Entra ID app using the OAuth 2.0 client credentials flow, which gets only the permissions it needs inside Business Central (Microsoft Learn).
To learn about changes, the agent subscribes to Business Central webhooks. Subscriptions expire after three days and must be renewed, each notification says which record changed without carrying the full record, and Business Central waits 30 seconds to batch changes (Microsoft Learn). That's why the integration renews subscriptions on time and reads the record again after every notification.
Access you can audit is not a detail for US IT teams: in Okta's Businesses at Work report, 58% of organizations name AI governance and identity as their top concern (Okta). An Entra ID app with its own permission sets gives you one identity to review, rotate or revoke, separate from any employee's account.
About the Business Central MCP server: Microsoft publishes an MCP server for Business Central online, built for assistants such as Copilot Studio or Claude; every operation uses the signed-in person's identity and permissions, and the default configuration is read-only (Microsoft Learn). It suits one person's assistant; an agent that serves customers for the company uses API v2.0 with its own app and least privilege.
You've seen how it connects. Want to walk through your case?
Tell us how your Business Central is set up and we'll tell you what data we need and where the agent connects.
An agent connected to your Business Central vs. a standalone tool
| Standalone AI tool | Agent connected to your Business Central | |
|---|---|---|
| Data source | A copy that drifts | Your source of truth, live |
| Where your data lives | In a third-party system | In your environment, encrypted end to end |
| Result of each operation | Stuck in another app | Written back to your Business Central |
| Permissions and audit | Broad and hard to audit | Least-privilege scope and an audit trail |
| Reaching production | Often stalls as a pilot | Validated, phased rollout |
Why add conversational channels on top of Business Central
Third-party figures, each with its published source, to size the ERP and the mechanics of the integration. None of them is a Vantegrate result.
55,000
Companies that trust Business Central, Microsoft's ERP for small and midsize businesses, by Microsoft's count
31,066
Companies Enlyft detects using Business Central, most often in the United States and at firms with 50 to 200 employees
6,000
Requests per user in a five-minute sliding window; past that, Business Central returns an HTTP 429
Source: Microsoft Learn, Business Central operational limits (2025)
95%
Of generative AI pilots never reach production with measurable business impact
Microsoft reports its own company count. Enlyft counts the companies its dataset detects using a tool, not paying customers, so read it as footprint. The request limit is Business Central online's, and it applies to application users too; the integration respects it with orderly retries. The MIT NANDA figure reflects the gap between experimenting with AI agents and running them in production.
Which agents run on your Business Central
Every product in the suite uses the same integration through API v2.0 and records the result where it belongs.
Sellium
Sales agent: checks items, availability and prices in Business Central, creates the quote or the sales order over WhatsApp, SMS or web chat, and logs the conversation in Salesforce, alongside Microsoft's Sales Order Agent.
Explore Sellium
Arconte
Document agent: reads vendor invoices, delivery notes and purchase orders that arrive as PDFs, photos or email, in English or Spanish, checks them against your data and enters the purchase invoice in Business Central.
Explore Arconte
Metrix
Data agent: your team asks about sales, inventory or collections from Microsoft Teams, Slack, WhatsApp or the web, and Metrix answers from Business Central's live data, showing each person only what they're allowed to see.
Explore MetrixThe integration doesn't take your data anywhere
The principle is simple: AI comes to your data, not your data to the AI. The agent reads and updates your Business Central through the official API, as an app with narrow permissions, and logs every operation.
- Connection through API v2.0 with a Microsoft Entra ID app and the OAuth 2.0 client credentials flow, without anyone's personal account.
- Least privilege: the app gets only the permission sets your use case needs, never SUPER.
- Your database stays in your Business Central environment, and every operation the agent performs is logged and auditable.
- The agents run on Salesforce or Oracle Cloud Infrastructure, whose SOC 2 and ISO 27001 certifications belong to those platforms, not to Vantegrate or Microsoft.
Frequently asked questions about the Business Central integration
What sales, finance and IT teams usually ask before connecting an AI agent to Business Central.
How do I integrate Business Central with an AI agent?
How do I integrate Business Central with an AI agent?
With an app registered in your Microsoft Entra ID that connects to Business Central's API v2.0 through the OAuth 2.0 client credentials flow. Inside Business Central, that app gets only the permission sets it needs, and the agent reads items and customers, creates quotes and orders, and learns about changes through webhooks. Vantegrate handles the setup and rollout. For the wider picture, see Selling on WhatsApp with your ERP.
If Business Central already has a Sales Order Agent, why add another agent?
If Business Central already has a Sales Order Agent, why add another agent?
Because they cover different channels. Microsoft's agent processes what arrives in a Microsoft 365 mailbox, and a person approves every outgoing message. Vantegrate's agent serves the customers who write over WhatsApp, SMS or web chat, with the same inventory and prices from Business Central, and logs the conversation in Salesforce if that's your CRM. We define which channel each one handles, so no order comes in twice.
We run Business Central in more than one country. Does that change the integration?
We run Business Central in more than one country. Does that change the integration?
Not the API. Microsoft delivers its own localization for the United States, Canada and Mexico, among others, while most of Latin America runs on localization apps that partners publish on Marketplace on top of the international version (Microsoft Learn). API v2.0 is the same everywhere; what changes by country, such as tax fields, is mapped during discovery. The agent can also serve each market in English or Spanish.
Is this the same as integrating Dynamics 365 Sales?
Is this the same as integrating Dynamics 365 Sales?
No. Business Central is the ERP for small and midsize businesses in the Dynamics 365 family, with its own API and permission model, and this page covers that product: orders, vendor invoices and business questions. If your sales team runs Salesforce, the agent logs conversations and opportunities there (Salesforce integration). And if your team lives in Microsoft Teams, Metrix answers questions about Business Central right in Teams.
Can the agent reach US customers on WhatsApp and SMS?
Can the agent reach US customers on WhatsApp and SMS?
Yes, with each channel used for what it does best. WhatsApp reaches 32% of US adults (Pew Research Center, 2025), so it works well for customers who already message you there, and conversations they start aren't affected by Meta's rules. Meta does not deliver WhatsApp marketing templates to US (+1) numbers (Meta), so campaigns to US customers go by SMS. Either way, the order lands in Business Central.
Microsoft 365 integration
How the AI agents work with Outlook and the rest of Microsoft 365.
Learn moreMicrosoft Teams integration
How the agents' alerts and answers reach your team's channels in Teams.
Learn moreSelling on WhatsApp with your ERP
What ERP data the agent reads, how it connects and which mistakes to avoid when selling with live inventory and prices.
Learn moreLet's connect AI agents to your Business Central
Tell us which localization you run, where your customers place orders and whether you've turned on Microsoft's Sales Order Agent, and we'll show you what the agent queries, which permissions we request for the app and how the two agents work side by side. A 30-minute conversation, no commitment.
Francisco Morales, co-founder, takes your call. We reply on WhatsApp within 4 business hours, no strings attached.
