peekgenticBook a call

Analysis · AI in business

Microsoft 365 Copilot vs. a custom agent for order entry

Copilot is already in a lot of Microsoft 365 bills, so why would anyone build a custom agent for order entry? Copilot helps a person work faster. A custom agent does one defined job end to end and hands it to a person to approve. What each one costs to run, who controls it, and when Copilot is the better choice.

By Miguel GutierrezCo-founder, Peekgentic · Dallas
· 7 min read
Preview card: Copilot vs. a custom agent for order entry.
An assistant helps a person. An agent does a defined job and hands it to a person to approve.Peekgentic

In brief

Microsoft 365 Copilot is an assistant for a person. It drafts, summarizes and finds things inside Outlook, Teams and Excel, and it only sees what that person can see. Order entry is a repeat job that starts when an email lands, not when someone asks a question. For that you need an agent: one built in Microsoft's Copilot Studio, Microsoft's own Sales Order Agent if you run Business Central, or a custom agent built for your ERP. Microsoft's published rates show that an agent triggered by an email runs on Copilot Credits, not on the Copilot seat you already pay for. Pick by where your orders land, which ERP you run, and who will own the agent.

  • Microsoft 365 Copilot is an assistant for one person. Order entry starts with an email, so it needs an agent.
  • Microsoft lists Copilot at $30 per user per month (paid yearly) and Copilot Studio at $200 per month for 25,000 credits.
  • By Microsoft's rules, an agent started by an email uses credits even if your team has Copilot seats.
  • Under prepaid capacity, agents are blocked at 125% of what you bought. Someone has to watch the meter.
  • Business Central shops should try Microsoft's Sales Order Agent first. Other ERPs, many PO layouts and specific rules point to a custom agent.

The question we keep hearing

An owner pays for Microsoft 365. Some of the team already has Copilot. Then someone suggests building an agent to enter customer orders, and the fair question is: don't we already have that?

Mostly, no. But the honest answer isn't "Copilot can't do it." Microsoft sells more than one thing called Copilot, and one of them can be used to build an order-entry agent. So the real choice has three or four options, not two. This page lays them out with Microsoft's own numbers.

What each one actually is

Four ways to use AI on the order desk

OptionWhat starts itWhat it does wellWhere it stops
Microsoft 365 Copilot (the seat)A person asks it somethingSummarize an email thread, draft a reply, pull numbers into ExcelDoesn't watch the order inbox or post to your ERP on its own
A Copilot Studio agentA person, a schedule or an event like a new emailRuns a set of steps across Microsoft 365 and connected appsSomeone has to design, test and own it; it runs on credits
Business Central Sales Order AgentA new email in a set mailboxReads the request, checks stock, drafts a quote, then an orderOnly for Business Central
A custom agentA new email, portal order or fileReads any PO layout, maps it to your ERP, checks your rules, drafts the orderYou (or your builder) own the maintenance

The first row is what most people mean by "Copilot." Microsoft's privacy page says Copilot only surfaces organizational data the user can at least view. That's a good safety rule. It also tells you what Copilot is: a helper sitting next to one person, working with that person's access.

Order entry doesn't work like that. A customer emails a PDF at 6:40 a.m. Nobody asks a question. Something has to notice the email, read the PO, find the customer and items in your ERP, check the price and the date, and put a draft in front of the order desk. That's an agent's job, not an assistant's.

Option 2: building the agent in Copilot Studio

Copilot Studio is Microsoft's tool for building agents. Its agents can be started by a person or by an event, and they can call agent flows. Microsoft describes agent flows as deterministic: the same input always produces the same output. That's exactly what you want for the steps that must never vary, like "check the customer's credit hold before drafting."

If your company already lives in Microsoft 365 and has someone who builds in Power Platform, this is a real option. You stay in one vendor's admin center, with one set of logins and one bill.

What each one costs to run

Here is where the "we already pay for Copilot" idea breaks down. The Copilot seat and the agent are billed differently.

Microsoft lists Microsoft 365 Copilot at $30 per user per month, paid yearly, as an add-on to a qualifying Microsoft 365 plan. Copilot Studio is sold as packs of 25,000 Copilot Credits at $200 per pack per month, or on a pay-as-you-go meter. Those are Microsoft's list prices as of Nov. 13, 2026; your reseller's price may differ.

Every step an agent takes uses credits. Microsoft's billing page lists the rates:

Copilot Credits per agent feature

Microsoft's published Copilot Studio rates. One interaction can use several of these at once.

  1. Classic answer1
  2. Generative answer2
  3. Agent action5
  4. Reading a document, per page8
  5. Grounding in company data10
  6. Agent flow, per 100 actions13

Source: Microsoft Learn, Billing rates and management, Copilot Studio. "Reading a document" is Microsoft's "content processing tools" line.

Now the key footnote. Microsoft says employee-facing use of an agent is included with a Copilot license when a licensed user is the one using it, under their own identity. For agent flows, that only applies when the flow is started by the agent a licensed user is talking to. Flows started any other way use credits at the standard rate.

An order-entry agent is started by an email, not by a licensed user chatting with it. So by Microsoft's own rules, it runs on credits even if everyone on the order desk has a Copilot seat.

What does that mean per order? It depends on how the agent is built, and Microsoft offers an agent usage estimator for that. As a rough illustration only (our numbers, not Microsoft's): an agent that reads a two-page PO (16 credits), takes three agent actions (15 credits) and runs a 20-step flow (about 3 credits) uses about 34 credits per order. At that rate, one 25,000-credit pack covers about 735 orders a month. Build it differently and the number moves a lot.

What happens when the credits run out

This matters more for an order desk than the price does. Under prepaid capacity, Microsoft says that when a company reaches 125% of its prepaid capacity, its agents are blocked, and a blocked agent stops responding, even in the middle of a conversation. When an environment has no credits left, new agent flow runs are blocked too. You can avoid that with a pay-as-you-go meter or by moving capacity around, but someone has to watch it.

Billing is also changing. From Dec. 1, 2026, new Copilot Business licenses bought through a reseller come with metered billing on by default. We covered that in Microsoft Copilot billing is going metered by default.

And a custom agent?

A custom agent costs money to build, and then it costs the AI model usage and hosting it runs on. We don't publish prices here. But you can hold any builder, including us, to one rule: show the run cost per order in writing, and what happens when volume doubles. If they can't, that's your answer.

The Copilot seat you already pay for doesn't cover an agent that wakes up when an email lands.

Who controls it

With Copilot, Microsoft controls the model, the features and the rates. Its billing page says Microsoft reserves the right to update the usage limits as the product changes. That's normal for a big platform. It also means the rules can move under you.

Copilot's permission model is a strength and a warning. It shows each person only what they can already open. If your SharePoint has open folders nobody cleaned up, Copilot makes them easier to find. Fix access first.

With a Copilot Studio agent, you own the design and Microsoft owns the platform and the meter. Admins can set monthly limits per agent in the Power Platform admin center. Whoever built it needs to stay around, or the agent becomes the next spreadsheet only one person understands.

With a custom agent, you should own the rules, the prompts, the logs and the connection to your ERP. You can change the AI model underneath without starting over. The other side of that: someone has to maintain it, and if your builder disappears, you need the code and the documentation. Put that in the contract.

If you run Business Central, look at Microsoft's agent first

Microsoft built an order agent for its own ERP. The Sales Order Agent watches a set mailbox, reads PDF, PNG and JPG attachments, checks whether the customer exists and whether items are in stock, and prepares a quote. It always creates a quote first, even when the customer asks for an order, and turns it into an order when the customer confirms. Designated users review and approve every outgoing message before it goes to the customer.

It also filters out emails that aren't requests, like offers to sell or attempts to get internal data, and Microsoft says partners can inspect its prompt instructions. For a Business Central shop with simple orders, that's a strong place to start, and a custom build may not be worth it.

When Copilot is the better choice

  • Your order volume is low. If one person enters 10 orders a day, Copilot helping that person read and summarize may be all you need.
  • You run Business Central. Try the Sales Order Agent before anything else.
  • You have a Power Platform builder on staff who will own a Copilot Studio agent for years, not months.
  • Your orders are mostly clean: few layouts, your own item numbers, standard prices.

When a custom agent is the better choice

  • Your ERP isn't Microsoft's, or it runs on your own server: Sage 100, Epicor, an older industry system. See our pages on Sage 100 and Epicor order entry.
  • Your customers send dozens of PO layouts, with their own part numbers that need a cross-reference.
  • Your rules are specific: contract prices, case quantities, ship-to codes, credit holds, lead times by item.
  • You want a fixed run cost per order and logs you own, not a shared credit pool that other agents also draw from.

A fair test before you decide

  1. Pull 20 real orders from last month: easy ones, ugly ones, a scan, a revised PO.
  2. Time how long each takes your team today, start to finish.
  3. Run the same 20 through each option you're considering. Count what it got right with no edits.
  4. Ask each option's owner for the cost per order at your volume, and what happens when credits or budget run out.
  5. Ask who fixes it when a customer changes their PO layout next spring.

Whatever you pick, keep a person approving each order before it posts, as we explain in human-in-the-loop automation. And measure minutes per order before and after, as in how to measure the ROI of office automation.

Common questions

Can Microsoft 365 Copilot enter orders into our ERP?

Not on its own. The Copilot seat helps a person draft, summarize and find things using what that person can see. Watching an order inbox and drafting orders takes an agent, built in Copilot Studio, Microsoft's Sales Order Agent for Business Central, or a custom agent.

Does our Copilot license cover a Copilot Studio agent?

Only partly. Microsoft says employee-facing use is included when a Copilot-licensed user uses the agent under their own identity. Agent flows started some other way, like a new email, use Copilot Credits at the standard rate.

How much does Copilot Studio cost?

Microsoft lists Copilot Studio as packs of 25,000 Copilot Credits at $200 per pack per month, or a pay-as-you-go meter. Each agent step uses credits, for example 5 per agent action and 8 per page for document reading.

What happens when Copilot Studio credits run out?

Under prepaid capacity, Microsoft says agents are blocked when the company reaches 125% of its prepaid capacity, and new agent flow runs are blocked when an environment has no credits. A pay-as-you-go meter can cover overage.

We run Business Central. Should we build a custom agent?

Try Microsoft's Sales Order Agent first. It reads emailed requests and PDF or image attachments, checks stock, drafts a quote and then an order, and a person approves every outgoing message.

When is a custom agent the better choice?

When your ERP isn't Microsoft's or runs on your own server, when customers send many PO layouts with their own part numbers, when your pricing and shipping rules are specific, or when you want a fixed run cost per order and logs you own.

Sources

  1. Microsoft, Microsoft 365 Copilot enterprise pricing, checked Nov. 13, 2026
  2. Microsoft, Copilot Studio pricing, checked Nov. 13, 2026
  3. Microsoft Learn, Billing rates and management (Copilot Studio), checked Nov. 13, 2026
  4. Microsoft Learn, Agent flows overview (Copilot Studio), checked Nov. 13, 2026
  5. Microsoft Learn, Data, privacy and security for Microsoft 365 Copilot, checked Nov. 13, 2026
  6. Microsoft Learn, Sales Order Agent (Business Central), checked Nov. 13, 2026

More from Peekgentic

Published November 13, 2026 · Written by Miguel Gutierrez, Co-Founder, Peekgentic (Dallas, TX). Every statistic links its source.