Salesforce and Microsoft announced Copilotforce at Microsoft Ignite on November 17, a partnership that puts Salesforce customer context and sales workflows inside Microsoft Copilot and Microsoft Teams. Of the four pieces in the announcement, one is generally available today.
What Salesforce and Microsoft announced
In a joint release datelined San Francisco and Redmond, the two companies described Copilotforce as a partnership that brings Salesforce into Microsoft’s enterprise productivity tools, with new integrations across Microsoft Copilot, Microsoft Teams and Microsoft Fabric. Accenture is the design and implementation partner and is also “customer zero,” deploying the integrations in its own global sales organization.
The centerpiece is Salesforce in Microsoft Copilot. Sales and revenue teams will be able to ask natural-language questions, get grounded answers and take Salesforce actions without leaving Copilot. Work IQ, the intelligence layer that powers Copilot, combines Salesforce insights with content from Teams meetings, Outlook emails and documents in SharePoint and OneDrive. Salesforce says the integration is powered by AIforce, “the live interface layer that brings Salesforce capabilities into external AI environments.”
Salesforce names three daily workflows:
- Customer meeting preparation, which combines account history and meeting transcripts into a single executive brief.
- Deal-health analysis, which surfaces deal risks and customer sentiment before deals stall.
- Pipeline review and action plans, which turn pipeline data into close plans inside Word and PowerPoint.
Miguel Milano, President and Chief Operating Officer of Salesforce, framed it as a distribution move: “Through Copilotforce, we’re bringing Salesforce to the largest surface in enterprise software today,” he said in the release.
Four pieces, four stages of availability
The availability roadmap in the release separates what a seller can use from what is still coming:
- Salesforce in Microsoft Copilot: public preview (beta), available through Salesforce’s AgentExchange and the Microsoft Copilot plugin directory.
- Sales Cloud in Teams: pilot. The app, first shown at Dreamforce, gives sellers a view of pipeline and quota progress, active deal notifications and briefing materials, and lets them act through Agentforce Coworker, with updates syncing back to Salesforce.
- Data Federation: generally available. Joint customers can query supported Microsoft Fabric OneLake data inside Salesforce Data 360 while the source data stays in Fabric.
- Salesforce Data 360 Data Sharing: public preview (beta). Organizations can share curated Data 360 context into Microsoft OneLake without duplicating datasets.
The data half of the announcement deserves a line of its own. Salesforce describes the Data 360 and Microsoft Fabric connection as bidirectional zero-copy access, meaning organizations harmonize and activate data across the two platforms without maintaining duplicate datasets or running brittle ETL pipelines. Sales and service teams get a richer view of each customer, marketers can build segments from the combined data, and Agentforce can use it to answer questions and complete tasks.
The release gives no pricing. It states that pricing and packaging are subject to change and tells customers to base purchasing decisions on capabilities that are commercially available today. By that standard, the only piece a buyer can contract for now is the data link between Data 360 and Fabric.
Permissions and writeback
For a CRM owner, the governance paragraph carries the most weight. Salesforce in Microsoft Copilot runs through authenticated user access and preserves the permissions, sharing rules and audit trails set up in both environments. Supported writeback actions to the CRM require explicit user confirmation and respect existing validation rules. A seller who asks Copilot to update an opportunity therefore hits the same validation logic as a seller typing into a Salesforce form.
That detail changes what RevOps needs to review. The validation rules, required fields and picklists that keep pipeline data usable now govern a second entry point, one that sits inside a chat window.
Accenture as the first deployment
Accenture says it has scaled Microsoft Copilot to more than 740,000 people and has 55,000 active Salesforce users, which makes its sales organization the first test of both halves working together. Julie Sweet, Chair and CEO of Accenture, said in the release: “The combined strengths of our three companies will reinvent sales with AI, giving sellers more time with customers while trusted intelligence and agents work alongside them in the tools they already use.”
The release shares no results from that deployment. Accenture says it will share learnings to help customers reach value sooner, so the first usable evidence for sales leaders will come from Accenture’s own rollout.
What it means for the sales leader
In our reading, Copilotforce is Salesforce deciding that the seller’s first screen may belong to someone else, and that the CRM’s job is to be the system the assistant reads from and writes to. Salesforce made a related argument earlier this fall, when it said half of Slack messages now come from apps and agents. Microsoft’s side of the same pattern appeared when it shipped a sales MCP server, with HubSpot and Salesforce following.
Three questions are worth putting to your Salesforce and Microsoft account teams before the preview reaches your reps:
- Find out which sellers already work in Copilot or Teams all day. Those users decide whether the preview is worth a pilot, because a seller who lives in Salesforce gains little from a second door.
- Name an owner for the connection. Salesforce says access follows existing permissions, which means a permission model that is out of date will now be exercised through a new interface. The argument for a named owner is in A Sales Assistant Connector Is a Data Boundary RevOps Must Own.
- Pick the measures. Meeting-prep time and the share of opportunity updates made outside the CRM are two numbers you can capture before the pilot and compare after it.
Pricing stays open. Until Salesforce and Microsoft publish how the preview is packaged, plan the pilot around the capabilities listed in the roadmap and keep the budget conversation separate.
Source: Salesforce

