Sales Close Agent in Dynamics 365: Setup Guide (2026)

In Customer Engagement · 8 July 2026

The Dynamics 365 Sales Close Agent is an autonomous AI that contacts prospects, handles objections, guides buyers to self-service checkout, and closes CRM records as won or lost, all without a seller in the loop. The setup requires actions across four admin portals and takes most teams two to four hours end to end. In this guide I walk you through every setup step in order and six things to check that might get missed.

What does the Sales Close Agent do?

The Sales Close Agent is grounded in four D365 entities: Accounts, Contacts, Leads, and Opportunities. It is designed for fast and simple deals such as renewals and outreach where the sales process is short and the salesperson’s time is better spent elsewhere.

Once activated, the agent selects records that match your target customer profile and begins autonomous outreach by email.

The sales close agent can:

• Respond to prospect replies using knowledge sources you configure such as product pages, SharePoint documents, or your company’s website.
• Handle common objections based on those knowledge sources.
• Guide the buyer toward a self-service checkout link if one is configured.
• Escalate the record to a human seller if the conversation goes outside its scope.
• Close the CRM record as won or lost when the outcome is determined.

The agent is capped at around 20 outgoing emails per 10 minutes to protect AI capacity consumption. It retries failed sends three times within an hour using exponential backoff, then retries over three days, then marks the record as failed. The follow-up cadence is four contacts spread over three weeks and is not configurable. Changing it requires a Microsoft support request.

Escalated records are saved in a dedicated view named <Entity> from Sales Close Agent inside Sales Hub.

The Sales Close Agent is one of three agents in a Microsoft Sales agent family alongside the Sales Qualification Agent and the Sales Opportunity Agent.

How to configure the Sales Close Agent

The configuration is pretty complex and it requires eight prerequisites; each one uses a different admin role.

The six connectors that need to be allowed in your DLP policy are: public-website knowledge, Copilot Studio, Dataverse, SharePoint/OneDrive knowledge, document knowledge, and Direct Line channels.

Step-by-step setup

Step 1: register an app in Microsoft Entra

In the Azure portal, create a new app registration. You need the Application Developer role in Entra to do this. Note the Application (client) ID and Directory (tenant) ID. You will need these when you configure the Dataverse app user.

Step 2: create the Dataverse app user and assign AISalesPerson

In the Power Platform admin center, go to Settings > Users + permissions > Application users. Create a new application user and paste in the Application ID from your Entra app registration. Assign the AISalesPerson security role to this user. This is the identity the agent uses to read and write CRM records.

If your sellers use custom security roles rather than the standard ones, note that those roles need explicit permissions or sellers will not be able to see records that the agent hands over. Microsoft lists six entities. On the standard tables, grant user-level permissions on Email Activity (email) and Contact (contact). On the agent tables, grant Global-level Read on msdyn_salesagentprofile (Sales Agent Profile), msdyn_salesagentrun (Sales Agent Run), and msdyn_salesagentconfigurationv2 (Sales Agent Configuration v2), and Basic-level Read and Write on msdyn_dcaengageagentresult (SCA Engage Agent Result).

Step 3: create and configure the shared mailbox

In the Microsoft 365 admin center or Exchange admin center, create a shared mailbox. This is the address the agent sends from. Give it a display name that will make sense to your recipients. Something like “D365 Sales Agent” is fine for a pilot.

Personal Note: Don’t disguise your agent as a real person. The agent will inevitably use AI tone and style when compiling emails and your prospects will notice. In sales, reputation and trust is essential. This does not mean you cannot use an agent for sales tasks, but you should do so without hiding behind a fake sales person. Use an email address and a signature that clearly shows the email is from an agent ensures transparency and trust.

Step 4: enable server-side synchronisation

In Dynamics 365, go to Settings > Email Configuration > Mailboxes, find the app user’s mailbox record, set the incoming and outgoing email to server-side synchronisation, and set the address to your shared mailbox. Then click Test & Enable Mailbox and wait for both tests to pass with a green result. If they fail, diagnose the email server profile before continuing.

Step 5: verify Copilot Studio capacity

The agent consumes Copilot Studio tenant capacity per record processed and per email generated. Check your capacity position in the Power Platform admin center before pointing the agent at a large segment. If you are on pay-as-you-go, ensure a billing policy is in place for the environment. More on this in the costs section below.

Step 6: configure the agent in Sales Hub

With prerequisites confirmed, open Sales Hub and navigate to the Sales Close Agent configuration area. Microsoft provides two setup paths:

AI Setup Assistant: a guided experience with three setup modes (quick, guided, or data-driven) that recommends configuration based on your CRM data. The assistant steps through target customer profile, product details, email delivery, email content, and knowledge sources. Best for a first deployment or when you want guardrails.

Manual configuration: a section-by-section form covering the same areas. Use this if you need precise control over every field or are importing an existing configuration via solution.

All sections must show a green check before the Start button becomes available. Do not click Start until you have run a simulation (see next section).

How to test before enabling the Sales Close Agent

The agent has a simulation mode that generates sample conversations against your configuration without touching CRM data or sending any real emails. Run a simulation for each record type you plan to use and review the output.

What to check in simulation:

• Are knowledge source responses accurate and appropriate for the tone you want?
• Is the escalation trigger firing in the right scenarios?
• Are the email subject lines and signatures correct for your shared mailbox identity?

If you are deploying across environments, move the agent configuration from sandbox to production via solution export and import. The agent configuration lives in a solution and travels cleanly through the standard ALM pipeline.

Six things to know before you deploy

These are the things that are technically in the Microsoft documentation but easy to miss because they are scattered across separate pages.

1. You cannot delete the agent once configured, only deactivate it. If you need to fully remove a Sales Close Agent instance, you must raise a Microsoft support ticket. Deactivation stops the agent from running but leaves the configuration in place. Plan your environment strategy before you start: test in sandbox, promote to production, and do not create agent instances in environments you expect to tear down.

2. One instance per agent type per environment. You cannot run two Sales Close Agent configurations in the same Dynamics 365 environment simultaneously. If your organisation has multiple sales motions that need different agent behaviour, you need separate environments or you need to accept a single shared configuration.

3. Editing certain sections after publish can break the agent state. Sections tagged “Avoid edits” in the configuration interface exist for a reason. Post-publish changes to these areas can put the agent into an inconsistent state that requires deactivation and reconfiguration to resolve. Take a solution snapshot before making any changes to a live agent.

4. Custom security roles need explicit table permissions. Out of the box, standard D365 roles work fine. But if your sellers are on custom roles (common in mature D365 deployments), they will not see agent-escalated records in their views unless the custom role has the explicit table permissions listed in Step 2. Confirm this in UAT before go-live.

5. DLP sign-off takes longer than the technical setup. Getting six connectors approved through your IT governance process, especially public-website knowledge and Direct Line channels, can take days or weeks in organisations with formal change management. Start this conversation with your Power Platform admin and IT security team before you begin any other setup steps.

6. PAYG capacity burn needs a billing policy before you scale. Pay-as-you-go capacity charges accrue per record processed and per message generated. During a pilot with 50 records, costs are negligible. Pointing the agent at a segment of 5,000 records without a billing policy and spend alert in place is a quick way to generate a surprise Azure bill. Set up the billing policy and a cost alert in Azure before you move beyond a controlled pilot.

How much does the Sales Close Agent cost?

The Sales Close Agent consumes Copilot Studio capacity, not a separate licence. Capacity comes in two forms:

Prepaid capacity: purchased in blocks of Copilot Studio messages. Predictable cost, easier to budget, the right choice for a consistent ongoing workload.

Pay-as-you-go: billed through Azure per message generated. No upfront commitment, but requires a billing policy attached to the Power Platform environment and Azure cost alerts to avoid overspend.

The 20 emails per 10 minutes throttle is not just a technical limit. It also functions as a cost control. The agent cannot burn through capacity faster than the throttle allows, which gives you a natural ceiling on consumption per hour.

The agent is currently in production-ready preview. Pricing terms may change at general availability. Monitor the Microsoft release notes and the source documentation, which carries an ms.update-cycle: 180-days tag.

FAQ

Can I delete the Sales Close Agent after I configure it? No. Once configured, the agent can only be deactivated, not deleted. Full deletion requires a Microsoft support ticket. This applies per environment, so plan your environment architecture before you begin configuration.

Can I change the follow-up schedule? No. The agent sends up to four follow-ups over three weeks, and this cadence is not configurable through the product interface. Changing it requires contacting Microsoft support.

Which record types does it work on? The Sales Close Agent works on Accounts, Contacts, Leads, and Opportunities. You configure the target record type as part of the target customer profile section during setup.

Is it generally available? As of June 2026, the Sales Close Agent is in production-ready preview. It is available in production environments but Microsoft still carries a preview designation. Expect changes to pricing, follow-up cadence, and possibly the connector requirements at GA. Refresh your configuration review at that point.

Related certification: AB-900: Copilot and Agent Administration Fundamentals.