Agentforce and Microsoft Copilot Studio both let you build AI agents, but they live in different places. Agentforce runs inside Salesforce and works on CRM records with Salesforce permissions, so it fits customer-facing service, sales and CRM workflows. Copilot Studio is Microsoft's low-code agent builder for Microsoft 365, Teams and the Power Platform, so it fits employee productivity and workflows built on Microsoft data such as SharePoint, Outlook and Dataverse, though it can also publish customer-facing agents to websites and messaging channels. Companies that run both platforms rarely choose one; they decide which agent owns which job and how the two share data without bypassing either system's access rules.
How do they compare?
| Question | Agentforce | Microsoft Copilot Studio |
|---|---|---|
| Where it runs | Inside Salesforce, including service channels, the console, Slack and Experience Cloud sites | Microsoft 365, Teams, websites and Power Platform |
| Primary data | CRM records, Data 360 and Salesforce knowledge | SharePoint, OneDrive, Outlook, Dataverse and connected sources |
| Who builds | Salesforce admins and developers with Agentforce Builder, Agent Script and flows | Business makers and Power Platform developers |
| Actions | Flows, Apex, CRM actions and connected APIs | Power Automate flows, connectors and APIs |
| Access model | Salesforce profiles, permission sets and sharing | Microsoft Entra ID permissions and the source systems' sharing |
| Best first uses | Case handling, lead response, account summaries, service self-help | Internal knowledge questions, request intake, document-heavy employee tasks |
When should Agentforce own the job?
- The agent talks to customers or partners through service channels, portals or messaging.
- The work reads or updates Salesforce records such as cases, leads, opportunities or accounts.
- Answers must respect Salesforce sharing rules, for example which advisor or territory may see an account.
- Sales and service teams already work in Salesforce or Slack all day.
When should Copilot Studio own the job?
- The users are employees working mainly in Teams, Outlook and Office documents.
- The knowledge lives in SharePoint or other Microsoft sources rather than the CRM.
- The workflow already runs on Power Automate or Dataverse.
- The agent's job is internal: HR and IT questions, policy lookups, request intake.
How do companies run both?
The common split puts customer-facing and CRM work in Agentforce and employee productivity in Copilot Studio. Where an employee in Teams needs CRM context, connect the two through governed integration, such as APIs or connectors that call Salesforce as the signed-in user, rather than syncing records into Microsoft storage. Keep one owner for each agent, one place where its instructions live and one log of what it did.
What governance applies to both?
- Clean up over-broad access first: SharePoint sites shared with everyone and Salesforce profiles with View All both turn into AI exposure.
- Define which data each agent may use and which actions it may take, in writing.
- Keep a person approving outbound customer messages until accuracy is proven.
- Test with real questions and edge cases before launch, and monitor answers after.
- Measure a specific outcome, such as time to resolution or request volume handled, against a baseline.
We work across both ecosystems: Agentforce and Claude on the Salesforce side, and Copilot Studio and Microsoft 365 Copilot on the Microsoft side. The useful first step is a short inventory of the jobs you want agents to do and where the data for each one lives.
