AI agents for Dynamics 365 F&O, in every legal entity
Lleverage brings AI to Dynamics 365 Finance and Operations as one agent per job: orders read from the inbox and created as sales orders, supplier replies checked against the purchase order they belong to. Each agent picks the legal entity first and works with that company’s records. Anything outside your rules goes to a person.
What you get
Each legal entity on its own terms
Finance and Operations keeps customers, vendors and products per company. The agent picks the company first and then works with the records and rules of that legal entity.
Already running on Dynamics 365
At SIG Benelux, 73% of order emails reach Dynamics 365 as a draft order ready to review, and 88% of order lines match the right article first time.
One monthly price per agent
Integration, AI usage and ongoing improvement are included in the price of each agent. There are no seats to count and no usage bills at the end of the month.
What the agent reads and writes in Dynamics 365 F&O
The agent works with the customers, released products and sales and purchase documents your team opens every day, in the legal entity the work belongs to.
Microsoft 365
SharePoint
Outlook
Teams
Gmail
Google Workspace
SAP
Epicor
Ridder iQ
Navision
NetSuite
Outlook, Teams and SharePoint around F&O
Most Finance and Operations work starts outside it, with an order in a shared mailbox or a supplier reply in a thread. The agent reads and answers there too.
14 orders read this morning, 3 replies sent
Teams#orders2 questions answered, 1 approval asked
Contract C-2291 opened for the price check
ZendeskService deskTicket 4471 updated and escalated in place
On your own servers, in files and on screens with no API
Some of the work sits where an API cannot reach: an installation on your own servers, a portal, a nightly file. Our engineers connect those during delivery.
How can AI be used in Dynamics 365 Finance and Operations?
One AI agent per job, each working on the F&O documents that job touches. The order card shows it running on Dynamics 365 F&O.
↗
Quote to orderSales orders into D365 F&OEmails, PDFs and spreadsheets read, tied to the customer account and released products, and created as sales orders without retyping.
↗
AP & ARVendor invoices matched, ready for your team to postEvery line against the purchase order and the product receipt, within your tolerances. Releasing a payment stays with a person.
↗
Purchase to payPurchase orders and supplier confirmationsEach purchase order priced off the contract and sent for the right signature, and each supplier reply read back against it.
↗
Forecast to produceA plan that moves with the ordersThe plan reworked when an order, a machine or a delivery moves. A date already promised to a customer is moved only by a person.
↗
Master dataCustomers, vendors and products in stepEach change checked where it happens, so F&O, the CRM and the webshop hold the same record in every legal entity.
↗
Order to deliveryOrder questions answered from the sourceOrder status, delivery dates and product questions answered from the live sales order and your own documents, with the source named.
How Lleverage connects to Dynamics 365 F&O
What the agent reads and writes in Finance and Operations, how it signs in, and what changes when F&O runs on your own servers. Microsoft’s side comes from Microsoft Learn, which we read on 17 November 2026.
| How it works | |
|---|---|
| Connection | Through Lleverage’s Finance and Operations connection, which our team sets up with yours because every environment needs its own configuration. It then shows under Configure, Connections in your Lleverage project, ready for workflows and agents. Nothing is copied into a second database, and F&O stays the system of record. |
| Authentication | You sign in with a Microsoft account that has access to your Finance and Operations environment, or connect with an app registration. On Microsoft’s side, OData services take OAuth 2.0 through Microsoft Entra ID, and an external app is registered under System administration, Setup, Microsoft Entra applications, tied to a service account user. |
| Reads | Customers, vendors and released products with their details, existing sales orders and sales quotations, sales invoices and purchase orders. It can list the companies in your environment, and most requests name the company first, because one environment often holds several legal entities. |
| Writes | Creates customers, sales orders with their lines, sales quotations and purchase orders, and updates existing sales orders. Several requests can be sent together as one batch. |
| Microsoft’s API | Finance and Operations exposes its public data entities through an OData endpoint at your environment’s root URL plus /data, with create, read, update and delete. An OData call runs the entity’s validate methods, and by default returns only the user’s default company unless the call asks for cross-company data. |
| On-premises | Our engineers connect systems on your own servers during delivery, without opening them to the internet. Where there is no API to call, the agent works the screen with a person’s access. Microsoft’s on-premises Finance + Operations signs in through Active Directory Federation Services (AD FS) rather than Microsoft Entra ID. |
| Permissions | The F&O account behind the connection decides what it can see and change. In Lleverage you choose which actions the connection allows and which wait for an approval first, and the audit history shows who changed what. |
Copilot in Dynamics 365 F&O or a Lleverage agent: which fits when?
Microsoft builds its own AI into the finance and operations apps: the Copilot sidecar, summaries on pages, and agents that are in production-ready preview. We read Microsoft Learn’s pages on Copilot in finance and operations apps, Copilot set-up and the Procurement Agent, Microsoft’s FastTrack sample on GitHub and the Lleverage docs on 17 November 2026.
| Copilot and agents (Microsoft) | Lleverage | |
|---|---|---|
| What it is | A Copilot sidecar for generative help and chat with F&O data, AI summaries on pages such as the customer page and workflow history, and agents in production-ready preview, among them the Account Reconciliation Agent and the Procurement Agent. | One AI agent per job, such as order entry or invoice matching. It does the whole job as the work arrives and hands a person only what falls outside your rules. |
| Customer orders sent by email | No order agent is among the Copilot and agent features Microsoft lists for Finance and Supply Chain Management. Its FastTrack team publishes a Sales Order Agent sample on GitHub, built on Copilot Studio and Power Automate, that reads PDF attachments and matches products by product code. | Reads the email body, PDF, Excel and CSV, ties lines that carry only a description to released products using the customer’s order history, and creates the sales order. At SIG Benelux 88% of lines match the right article first time. |
| Supplier confirmations and changes | The Procurement Agent reads vendor emails, works out whether each is a confirmation, a change request or a rejection, marks confirmed orders as confirmed, cancels rejected ones and suggests the changed fields for the purchaser to review and apply. Splitting a line into several deliveries is not yet supported. | Reads every reply, from a line in the thread to a PDF, against the purchase order it looks up in F&O. The buyer gets only the lines that moved, in Teams or Slack, and the agent carries on with the answer. |
| Ledger reconciliation | The Account Reconciliation Agent spots a difference between a subledger and the general ledger, offers ways to resolve it and can resolve it for you. | Lleverage has no ready-made agent for this. |
| A decision a person has to make | The Procurement Agent can save its follow-up emails to vendors as drafts that need a person’s review before they are sent. | The exception reaches a named person as a card in Teams, Slack or the inbox, listing every value the agent will send. Once they answer, the agent finishes the job. |
| Building your own agents | Developers can build agents on the Dynamics 365 ERP MCP server, which reaches nearly any function a user has in the application. Building an agent on it is in production-ready preview. | Our engineers build the first agent with your team. After that your team builds and changes agents and workflows by asking the agent, or by showing it a process on a screen-share call. |
| Getting better at the job | Users can rate Copilot answers with thumbs up or thumbs down, which goes to Microsoft as product feedback. | Your team rates the agent’s work, the agent drafts a change to the Skill from those ratings, and the change goes live once a person approves it. |
| Setting it up | Copilot needs Power Platform Integration switched on in Lifecycle Services, and agents are not supported in developer environments deployed through Lifecycle Services. The Procurement Agent is charged in Copilot Studio credits per run. | Forward deployed engineers connect the agent to F&O with your IT team. The first process typically runs supervised within a few weeks, at one monthly price per agent. |
| Fits best when | Your people want help inside the F&O pages they already use, and the work is answering questions, reading summaries or reconciling the ledger. | A whole job should leave the desk, such as orders and invoices that arrive in every layout, or supplier replies someone now chases by hand. |
We think Copilot is worth switching on first if your environment already runs Power Platform Integration: generative help and page summaries save time inside F&O. We think Lleverage fits when a whole job should leave the desk. One of those jobs runs on Dynamics 365 F&O today: order management.
Our engineers set it up with you.
Forward deployed engineers connect the agent to Dynamics 365 F&O with your team and work alongside your people, so work comes off the desk within a few weeks.
They work inside your operation, starting in the legal entity where the first job runs, and you set the confidence line.
Triggers, checks and the log are yours to configure. Our documentation and support sit behind your team, and an engineer is a call away whenever you want one.
Talk to us about either ↗Frequently asked questions
Does Dynamics 365 Finance and Operations have AI?
Yes. Microsoft offers a Copilot sidecar for generative help and chat with F&O data, AI summaries in Finance and Supply Chain Management, and agents in production-ready preview: the Account Reconciliation Agent in Finance and the Procurement Agent for supplier emails. None of them takes customer orders from the inbox into F&O, which is where Lleverage starts.
Does Copilot work with Dynamics 365 F&O?
Yes, on cloud environments with Power Platform Integration switched on in Lifecycle Services. The sidecar runs on Copilot Studio, needs Bing Search for generative answers, and may need cross-region data movement in Dataverse. Microsoft notes that some Copilot features are limited to specific data regions and languages, and agents are not supported in Lifecycle Services developer environments.
How does Lleverage connect to Dynamics 365 Finance and Operations?
Our team sets up the Finance and Operations connection with your IT team, signed in with a Microsoft account or an app registration. It then finds customers, vendors and released products, and creates sales orders, quotations and purchase orders, choosing the legal entity first. The connected account’s permissions in F&O decide what it may see and change. More on integrations.
Can an AI agent create sales orders in D365 F&O from customer emails?
Yes. At SIG Benelux, where around 3% of orders carry an article number, 73% of order emails reach Dynamics 365 as a draft order and 88% of lines match the right article first time. The sales desk still approves every draft. How it works step by step is on order management for F&O.
Who decides what the agent changes in Finance and Operations?
You do, per action. Reading customers can run freely while creating a sales order or a purchase order waits for an approval card in Teams or Slack, showing every value the agent will send to F&O. The connected account’s roles set the outer limit, and the audit history records each change. More on control and approvals.
The rest of the platform.
↗
Element 01AgentsA colleague that takes a job off the desk, start to finish.
↗
Element 02AutomationThe routine volume runs in the background all day.
↗
Element 03IntelligenceEvery correction becomes a change to the Skill once a person approves it.
↗
Element 04ControlApprovals, permissions and a full audit trail, set by you.
↗
Element 06DashboardsWhere the work stands, on one screen you can ask about.