Copilot Studio CRM Integration: Connecting Agents to Dynamics 365, Salesforce and HubSpot

For a Copilot Studio CRM integration, you connect the agent to your CRM through connectors or Model Context Protocol (MCP) servers. Dynamics 365 connects through Dataverse, Salesforce through Microsoft’s connector, and HubSpot through a third-party connector or HubSpot’s own MCP server. The agent then answers questions about customers, contacts and open deals directly in Teams or Microsoft 365 Copilot. We currently hear this question often from sales managers at mid-sized companies. As a first step, we recommend a sales assistant with read-only access. This guide compares the three CRM systems, shows the setup in six steps and explains the costs. All details as of 17 November 2026.

What a Copilot Studio agent can do in your CRM

A Copilot Studio agent in your CRM is an AI assistant that reads and summarises customer data. If you allow it, it also creates or updates records. Typical questions are: Which deals with customer X are open? When was the last contact? What was in the last quote? The answer comes in natural language, without anyone opening the CRM.

Technically, the agent uses two building blocks. A knowledge source searches CRM content and is best for answering questions. A tool calls the CRM directly, for example through a connector or an MCP server. Only tools can write records. You therefore decide for every tool whether the agent may only read or also change data.

Copilot Studio CRM integration: Dynamics 365, Salesforce and HubSpot compared

Dynamics 365 is the easiest to connect, Salesforce is mature, and HubSpot currently needs more testing. This comes down to the available connectors: Dynamics uses Dataverse in your own tenant, and Salesforce has a generally available Microsoft connector. For HubSpot, by contrast, there is only a preview connector or HubSpot’s MCP server.

FeatureDynamics 365SalesforceHubSpot
Recommended routeDataverse connector or Dataverse MCP serverSalesforce connector by MicrosoftHubSpot CRM connector or HubSpot MCP server
PublisherMicrosoftMicrosoftIndependent publisher (preview) or HubSpot
Connector tierPremiumPremiumPremium
Sign-inMicrosoft Entra IDSalesforce account (OAuth) or Entra SSOConnector per publisher; MCP with OAuth 2.1
As a knowledge sourceDataverse tables (Dataverse search required)Salesforce CRM connector for Microsoft 365 CopilotNo Microsoft connector
MaturityGenerally available; Dynamics 365 Sales MCP server in previewGenerally availableConnector in preview; test the MCP connection first

Dynamics 365: your data is already in Dataverse

With Dynamics 365, the data sits in Dataverse and therefore in the same Microsoft tenant. As a result, sign-in runs through Entra ID, and permissions from Dynamics continue to apply. The Dataverse MCP server offers search, read and write tools. According to Microsoft, it only deletes records after explicit confirmation.

Salesforce: connector for actions, Copilot connector for knowledge

For Salesforce there are two routes. The Salesforce connector retrieves data live and can write; it requires API access to be enabled. The Salesforce CRM connector for Microsoft 365 Copilot indexes accounts, contacts, opportunities and cases as knowledge and respects record-level sharing. Do not index fields protected by field-level security, because according to Microsoft that protection does not apply there.

HubSpot: third-party connector or MCP server

For HubSpot there is no connector from Microsoft or HubSpot, but one from an independent publisher in preview. Since April 2026, HubSpot has offered a generally available MCP server that works with the signed-in user’s permissions. In addition, Copilot Studio can connect to MCP servers. Even so, we test the HubSpot sign-in in every project before going further.

How to set up a Copilot Studio CRM integration in six steps

Setting up a CRM agent has a technical and an organisational part. Technically, it covers the environment, the connection, knowledge sources and tools. Organisationally, it covers data policies, permission reviews and, in Germany, coordination with the works council. The organisational part often takes longer. Follow this order:

  1. Step 1: Define the use case — Start with read-only access, for example a sales assistant for customer and deal questions. Writing comes later.
  2. Step 2: Prepare the environment and policies — Create a dedicated Power Platform environment. Assign the CRM connector to the “Business” group in your data policies.
  3. Step 3: Connect with user accounts — Let every user work with their own CRM account. Maker-provided credentials give all users the maker’s permissions.
  4. Step 4: Separate knowledge and tools — Use knowledge sources for questions and tools only for targeted queries. Name and describe tools clearly.
  5. Step 5: Secure write actions — For every tool that writes, turn on the tool’s Ask the end user before running option.
  6. Step 6: Test, publish, monitor — Test with real user accounts and publish in Teams or Microsoft 365 Copilot. Then monitor Copilot Credit consumption.

What does a Copilot Studio agent with CRM integration cost?

A CRM agent is billed through Copilot Credits: Microsoft’s German price list shows €173.30 per month for a prepaid Copilot Studio credit plan, excluding VAT. For example, a generative answer uses 2 Copilot Credits and an agent action 5 Copilot Credits (billing rates). Alternatively, pay-as-you-go billing through an Azure subscription is possible.

For people with a Microsoft 365 Copilot licence, using internal agents comes at no additional cost. The condition is that the agent runs with the user’s own identity, and fair-use limits apply (licensing on Microsoft Learn). Power Automate cloud flows, however, use Power Automate licensing. For the Copilot licence options, see our guide Copilot Business vs Enterprise.

Which route suits which company?

Dynamics 365 suits companies that already work in the Microsoft tenant, Salesforce suits teams with API access enabled, and HubSpot is currently best for a read-only pilot. The choice therefore depends on the CRM you already use and on how much testing time you can plan. Switching CRM just for the agent rarely pays off. Three rules of thumb help:

  • Dynamics 365: A good fit if you already work in the Microsoft tenant and want to start quickly. Permissions and sign-in come from Entra ID.
  • Salesforce: A good fit if API access is enabled and you want to combine live queries with indexed knowledge.
  • HubSpot: For now, mainly a fit for a read-only pilot until the connector or MCP connection has been tested in your tenant.

Benefits of a CRM agent for mid-sized companies

A CRM agent mainly saves search time, because sales and service query customer data in a chat instead of in forms. This matters especially in mid-sized companies, where a few people look after many customers. In addition, the CRM remains the system of record; the agent is just an extra interface. In practice, we see three benefits:

  • Faster preparation: Before a customer meeting, the agent summarises open deals, recent contacts and tickets.
  • Better data quality: People who use data in the chat also notice gaps sooner and fill them.
  • No system change: Your CRM stays as it is. The agent adds a natural-language interface in Teams.

Common mistakes in a Copilot Studio CRM integration

The most common mistake is a connection that uses the maker’s credentials, often an admin account. Every user then sees everything that account sees. This bypasses the CRM’s role-based permissions and usually breaches GDPR requirements too. Further mistakes cost trust or budget:

  • Writing from day one: Without confirmation, the agent creates records that nobody has reviewed.
  • A preview connector in production: A HubSpot connector in preview has no guaranteed stability.
  • No data policies: Without a policy, an agent can pass CRM data to unvetted services.
  • Consumption not monitored: Agent actions cost more than answers and add up quickly.
  • Forgetting the works council: In Germany, a CRM agent also generates usage data that is subject to the works council’s co-determination rights. See our article on the works agreement for Copilot (in German).

What AURUM does for you

AURUM has already built integrations with Dynamics 365 and with HubSpot. A first pilot with a read-only sales assistant usually takes two to four weeks with us. We cover the workshop, setup, testing and handover. You can find details on our page on AI integration and CRM connectivity (in German).

  • Use-case workshop: Together with sales and IT, we choose the questions the agent should answer.
  • Connection and permissions: We then set up the connector or MCP server, user sign-in and data policies.
  • Pilot and evaluation: We test with your team and measure usage and credit consumption.
  • Extension: On request, we add secured write actions or workflows.

We advise on the right licences but do not resell them. You can find more on our Power Platform consulting (in German) and our Microsoft and AI consulting services. For a first conversation, you can get in touch directly.

Frequently asked questions about Copilot Studio CRM integration

Do I need premium connectors for the CRM integration?

Yes. The connectors for Dataverse, Salesforce and HubSpot are premium connectors. The Copilot Studio licence allows premium connectors; the agent’s answers and actions are billed in Copilot Credits. Power Automate cloud flows need Power Automate licensing.

Can a Copilot Studio agent write data to HubSpot?

Technically yes, through the independent publisher’s connector or HubSpot’s MCP server. The connector is in preview, and you should test the MCP connection first. To start with, we recommend read-only access.

Does the agent respect permissions in Salesforce?

Largely, yes. The Salesforce connector works with the signed-in account. The Salesforce CRM connector for Microsoft 365 Copilot respects record-level sharing. You should not index fields protected by field-level security.

More questions about the CRM agent

What does a CRM agent cost for Microsoft 365 Copilot users?

For licensed users, internal use with their own identity comes at no additional cost, within fair-use limits. For other users, the agent consumes Copilot Credits; Microsoft’s German price list shows €173.30 per month for a prepaid credit plan.

How long does a pilot for a CRM agent take?

At AURUM, a pilot with a read-only sales assistant usually takes two to four weeks. The duration depends mainly on permissions, policies and the data quality in the CRM.

Conclusion: start read-only, then extend step by step

Copilot Studio connects agents to Dynamics 365, Salesforce and HubSpot, but the effort of a Copilot Studio CRM integration differs considerably. Start with a read-only sales assistant, individual user sign-ins and clear data policies. Add write actions only once the pilot has proved value and consumption.

Post teilen: