Dynamics 365 hands the small deals to an agent from 30 September, and it is one of the more useful things Microsoft has shipped for sellers this year. Message centre notice MC1464732, published on 1 September, confirms that the Sales Development agent reaches general availability at the end of the month with a new set of capabilities: it can generate quotes through Dynamics 365 Sales and through first-party and third-party quoting systems, share them on company-branded templates, answer questions about the quote, adjust the details when the customer pushes back, help the customer complete a self-service transaction, and escalate to a human seller when someone gets stuck. The agent that used to stop at a qualified lead now carries a straightforward deal all the way to a signed order.
The opportunity here is bigger than it first looks. Every B2B sales organisation carries a long tail of small, repeatable deals: spare parts, standard configurations, licence top-ups, renewals with no change in scope. Individually unremarkable and collectively worth a great deal, they have always competed for attention with the large opportunities that decide a seller’s quarter. A quoting desk that never queues, works in 22 languages and logs every exchange in the CRM changes the economics of that tail. The teams getting the most from it will be the ones who decide, before the switch is flipped, which deals count as small and what the agent needs to know to price them.
What did Microsoft ship for Dynamics 365 Sales on 30 September?
Two message centre notices landed together. MC1464732 covers the Sales Development agent, which Microsoft describes as taking leads from qualified opportunities through to closed deals. In preview the agent handled outreach, qualification and handoff, working from a playbook, a set of tone guidelines and product knowledge you upload as documents or URLs. General availability adds the commercial half: quoting, quote revision, self-service transactions and escalation, with connections to quoting and transaction systems running through the Agent 365 MCP registry. MC1464753, published the same day, lets sellers create contacts, accounts and opportunities from Microsoft 365 Copilot Chat, with an inline form pre-filled from the conversation.
Microsoft Dynamics 365 Sales is Microsoft’s CRM application for managing leads, opportunities, accounts and the sales process, built on the Dataverse data platform and licensed per user as Professional, Enterprise or Premium. It sits inside the wider Dynamics 365 suite alongside Customer Service, Customer Insights and the finance and operations applications, and integrates natively with Outlook, Teams and Microsoft 365 Copilot. It ships a family of out-of-the-box AI agents for lead qualification, opportunity research and, from 30 September 2026, autonomous quoting and deal closure for low-complexity sales. For organisations already standardised on Microsoft 365, it is usually the shortest path to a CRM that sellers open every day.
One note for early adopters: the Sales Close Agent preview, which covered this segment until now, stops accepting new instances on 30 September and existing instances are removed on 30 October 2026. Recreating it as a Sales Development agent is a modest job and a good excuse to revisit the playbook.
Which deals should an agent quote and close on its own?
The most valuable decision in this rollout is the one nobody in Redmond can make for you: the definition of a low-complexity deal in your business. Microsoft frames the agent as designed for high-velocity, low-complexity sales, and the guidelines you configure tell it whether to give high-level pricing guidance or escalate for a detailed quote. That is a segmentation exercise, and the organisations getting the most from the agent treat it as one.
A practical test has three parts. Can the price be derived from the catalogue and price list without human judgement? Is the commercial risk bounded, meaning standard terms, standard discount band, no bespoke delivery commitments? And does the customer already know what they want, so the conversation is about confirming rather than diagnosing? A manufacturer’s aftermarket parts orders, a software vendor’s seat expansions and a distributor’s reorders of stocked lines all pass comfortably. A configured machine with engineering review or a multi-year framework agreement does not, and the agent’s escalation path is exactly where those belong. Drawing the line generously on the simple side, and clearly on the complex side, is what makes the agent safe to switch on.
Why does the product catalogue decide how far the agent can go?
An autonomous quoting agent is only as good as the catalogue it prices from, and this is where the release quietly rewards teams that have kept their Dynamics 365 product data in order. The agent recommends products, applies pricing and adjusts quotes on customer feedback, and all three depend on the product records, price lists, units and bundles being current, complete and unambiguous. Microsoft’s guidance on the earlier Sales Close Agent put it directly: accuracy comes from a well-defined product catalogue and pricing information. The catalogue is now doing a job it never had before, which is answering a customer without a seller reading it first.
CRM data quality is important because every automated decision in the system inherits the accuracy of the records it reads. Clean, complete and consistent data lets routing, forecasting, reporting and AI agents act without a person checking each step, which is where the productivity gains of CRM automation come from. Poor data quality shows up as misdirected leads, unreliable forecasts and, with autonomous agents, quotes that are wrong in front of a customer. The practical standard is that fields used for decisions are mandatory, validated at entry and owned by someone. For quoting agents, that means product names, SKUs, list prices, discount rules and active-or-retired status are trustworthy enough for a customer to act on without a human review. The clean-up pays back on every other channel too, and most organisations can get the high-velocity segment of the catalogue agent-ready in two to four weeks, because the simple products are usually the best maintained.
Where do CPQ and ERP integration come in?
The most interesting line in MC1464732 is the one about third-party systems reached through the Agent 365 MCP registry: the agent is not limited to the native quote entity in Dynamics 365 Sales. If your pricing logic lives in a CPQ tool or your order confirmation has to come from the ERP, the agent can call those systems as tools once an administrator has published and approved the connection. For manufacturers, this is the arrangement that makes sense: the CPQ engine holds the configuration and pricing rules, the ERP holds stock and delivery dates, and the agent runs the conversation across both for the deals simple enough to close that way.
CPQ software, short for configure, price, quote, is a category of sales tool that lets a seller or a customer assemble a valid product configuration, price it according to the organisation’s rules and discount policy, and produce a quote document without manual calculation or engineering review for standard cases. It matters most where products have many options and interdependencies, which is why manufacturing, industrial equipment and technology vendors are its heaviest users. Integrated with a CRM, CPQ turns the quote from a spreadsheet exercise into a governed, repeatable step in the sales process, and it is the natural pricing engine behind an autonomous quoting agent.
Integrating a CRM with an ERP means connecting the system that manages customers, opportunities and quotes with the system that manages orders, inventory and invoicing, so that a deal closed in one becomes an order fulfilled in the other without re-keying. The standard approach is to decide which system owns each piece of data, typically the CRM for accounts and opportunities and the ERP for products, prices, stock and invoices, then synchronise on defined events such as quote accepted or order shipped. Native connectors link Dynamics 365 Sales with Dynamics 365 Finance, and MCP-based tools now cover third-party ERPs. Getting the ownership rules right first keeps the integration stable as agents start to write orders directly.
How does an agent with its own identity fit your governance?
Here is the design choice that makes this release easier to govern than it sounds. The Sales Development agent is not a feature toggle inside a seller’s account. It is an agent user with its own identity in Agent 365: it needs a Dynamics 365 Sales licence assigned in the Microsoft 365 admin centre, a security role in the Power Platform admin centre (Salesperson by default, or a custom role scoped to what you want it to touch), and a connection to the Dataverse MCP server approved by a global or AI administrator. Every email it sends and every quote it issues is logged against that identity in the CRM.
That structure gives sales leadership three levers it already understands. The licence decides whether the agent exists, the security role decides what it can read and write, and the MCP approval decides which external systems it can reach. Add the playbook, which fixes the stages a prospect moves through, and the guidelines, which set tone and define what it may say about pricing, and you have an agent whose scope is written down before it sends a single message. Autonomous quoting is accountable quoting: a named user, a role and a log.
What changes for sellers when the small deals leave their desk?
The immediate change is time. A seller who spent an hour a day producing and chasing small quotes gets that hour back, and the small deals get answered in minutes. The second change is visibility. Because the agent qualifies, quotes and closes inside the CRM, the long tail that used to live in email threads and spreadsheets becomes pipeline: countable, forecastable and attributable. Many sales leaders will see the true size of their transactional business for the first time. The seller’s role in that segment shifts from producing quotes to supervising outcomes, with the agent’s escalation queue in Teams as the new inbox.
Improving CRM adoption rates comes down to making the system the easiest place to do the job, then measuring whether it is. The teams with the highest adoption remove double entry by integrating email, calendar and quoting, keep required fields to the ones that drive a decision, and give sellers something back for their data in the form of insights, priorities and automated follow-up. Agents help adoption when they take work off the seller rather than adding review steps, so introducing them on the deals sellers least enjoy, such as repetitive small quotes, is a strong first move. Track record completeness and time-to-quote before and after, and share the results, because adoption improves fastest when sellers see the return on the data they enter.
The Sirocco perspective
We work across Salesforce, HubSpot and Microsoft Dynamics 365, and the same pattern is now visible on all three: quoting and ordering are moving out of the seller’s inbox and into governed, agent-driven steps inside the CRM. HubSpot moved quote-to-cash inside the platform in July, Salesforce put B2B ordering into an agent in August, and Microsoft completes the set on 30 September. That is good news for buyers: the capability is becoming standard rather than a premium bolt-on, and the differentiator shifts to how well each organisation defines its simple deals and maintains its catalogue.
Using an independent CRM partner means working with advisers whose recommendations are not tied to selling one vendor’s licences or delivering one vendor’s methodology. An independent partner can compare Salesforce, HubSpot and Dynamics 365 on how each handles a specific need, such as autonomous quoting, and advise on the segmentation, data and integration work that makes the feature deliver on whichever platform is chosen. That matters most when three vendors ship similar capabilities within a quarter and the right answer depends on the client’s product complexity, ERP landscape and sales motion rather than on any roadmap.
Our advice for Dynamics 365 customers is to spend October on three things. Define the low-complexity segment with sales and finance in the room, and write it down as rules the playbook can hold. Audit the product catalogue and price lists for that segment. And decide the integration path, native quotes or CPQ and ERP through the MCP registry, before the first instance is created. Done in that order, the agent starts on deals it can price correctly, sellers see the time come back immediately, and the case for extending its scope writes itself. If you would like a second opinion on where to draw the line, or help getting the catalogue ready, schedule a consultation and we will walk through it with you.
Get in Touch
If you are deciding which Dynamics 365 deals an agent should quote and close first, or how your product catalogue and CPQ need to look before it can, we are happy to talk it through.
