Microsoft and Salesforce announced Copilotforce on 17 November, connecting customer records with Microsoft’s workplace AI. The important boundary is between accessing information and changing it: supported CRM writebacks require explicit user confirmation and existing validation rules.
Salesforce in Copilot is in public preview, with more than 38 sales skills and access governed by existing Salesforce permissions. Sales Cloud in Teams is a pilot, with open beta planned later this year. These are not equivalent to a completed enterprise-wide rollout.
The data connections also have different statuses. Querying supported Fabric OneLake data from Salesforce Data 360 is generally available; sharing curated Data 360 intelligence into OneLake remains in public preview. Accenture is a design and implementation partner and pilot customer. Regional access depends on customer agreements.
The MM read: A useful purchasing test is to separate three questions: what can the assistant see, what can it propose, and what can it commit? A convincing demonstration of the first does not settle the other two.
Before expanding a pilot, buyers should test a disputed customer record, a rejected update and an employee without permission. Those cases reveal more about operational fit than a smooth demonstration alone. Measure accepted work, review time and correction effort rather than assuming fewer application switches automatically produce savings.
Source: Microsoft and Salesforce joint announcement, 17 November 2026. Product availability is company-reported; the purchasing questions above are MM analysis.






Leave your thoughts