# Copilotforce: what changes when Salesforce moves into Microsoft Copilot

> Salesforce is moving into Microsoft Copilot and Teams. Here is what is live, what is still preview, and what to fix in your org before your sellers start using it.

- Source: https://synconai.com/insights/copilotforce-what-it-changes
- Publisher: SynconAI (https://synconai.com)
- Desk: AI & Agentforce
- Author: SynconAI Agentforce Practice, AI agents & automation
- Published: 19 November 2026
- Reading time: 10 minutes
- Topics: Copilotforce, Microsoft Copilot, Teams, Data 360, Microsoft Fabric, Permissions

## Key points

- Copilotforce is a partnership with three integrations at three different stages: one public preview, one pilot, and Data 360 federation to Fabric OneLake, which is stated as generally available.
- Supported CRM writeback from Copilot needs explicit user confirmation and respects existing validation rules, which makes the quality of those rules part of your AI governance.
- No pricing or dates are published, and Salesforce states that packaging is subject to change.
- The decision that does not wait on any of it is access: who can see and change what, because Copilot and Teams now reach the same records.

---
On 17 November 2026, at Microsoft Ignite, Salesforce and Microsoft announced **Copilotforce** (you will also see it written as Copilot Force): a partnership and three integrations that bring Salesforce into Microsoft Copilot, put Sales Cloud into Microsoft Teams, and connect Data 360 to Microsoft Fabric. If you searched for *Salesforce in Microsoft Copilot* or *Salesforce Copilot integration*, this is the announcement behind both.

Coverage so far leans toward strategy: two giants agreeing to meet in each other's interfaces. We are not going to settle that. The question we are asked is narrower, *what does this mean for the org I look after*, and it has an awkward property. The announcement bundles pieces at very different stages of maturity under one name, so the first job is to take it apart.

Everything below comes from Salesforce's own announcement and the documentation it links. Where those are silent we say so.

## What was announced

Four things, because the Data 360 work counts twice.

**Salesforce in Microsoft Copilot.** Salesforce customer context and workflows inside Microsoft Copilot, powered by Salesforce's AIforce, its interface layer for external AI environments, with Work IQ as the intelligence layer behind Copilot. The three workflows named are customer meeting preparation, deal-health analysis, and pipeline review with action plans, the last working inside Word and PowerPoint. Salesforce lists it as public preview (beta), available through AgentExchange and the Microsoft Copilot plugin directory.

**Sales Cloud in Teams.** A Sales Cloud app for Teams that shows pipeline progress, with Agentforce Coworker letting sellers delegate work and act inside Teams, adaptive cards that update supported opportunity details, and shared deal rooms. Salesforce lists it as a pilot, introduced at Dreamforce.

**Data Federation to Microsoft Fabric OneLake.** Data 360 can query and analyse Microsoft Fabric OneLake data where it lives, without duplicate datasets or ETL pipelines to maintain. Salesforce lists this as generally available.

**Data 360 sharing into OneLake.** The reverse direction: sharing curated Data 360 data and context into OneLake for analytics, reporting and AI workloads. Listed as public preview (beta).

Salesforce adds that Accenture is the design and implementation partner and its "customer zero". The figures it gives for Accenture are more than 740,000 Copilot users, 55,000 active Salesforce users and 13 industries. The announcement also mentions an Informatica plugin for Copilot, but gives it no availability status, so we leave it out of this read.

| Piece | Stated status | What that means in practice |
| --- | --- | --- |
| Salesforce in Microsoft Copilot | Public preview (beta) | You can try it, and a preview is not a production commitment |
| Sales Cloud in Teams | Pilot | Select customers only, so plan for a conversation, not a rollout |
| Data Federation to OneLake | Generally available | The one piece you can design against today |
| Data 360 sharing into OneLake | Public preview (beta) | Useful to test, risky to build a pipeline on |

:::warn Read each status separately
Salesforce's page uses "public preview (beta)" and "pilot" for different pieces, and the wording is not perfectly consistent across the page. No dates are given for general availability of anything that is not already generally available. Salesforce states that pricing and packaging are subject to change, and advises customers to base purchasing decisions on capabilities that are commercially available today. If a conversation in your business assumes Copilotforce is one product that is simply available, correct it now.
:::

## The part that should change your week

A few lines in the announcement matter more to an admin than any of the strategy.

The first: supported writeback actions to the CRM require explicit user confirmation and respect existing validation rules. The second: the Teams app uses adaptive cards that update supported opportunity details. The third: Salesforce says the Copilot integration works through authenticated user access, preserving permissions, sharing rules and audit trails. That third line states the principle. It does not show you how it behaves in your org.

Put together, that means a seller can change an opportunity from a chat surface, and the only things standing between a sloppy sentence and your pipeline are a confirmation click and whatever your validation rules enforce. Not a flaw, since a confirmation step and rule enforcement is the right design. It does change what validation rules are for.

Until now a validation rule was a nuisance a seller saw on a page layout. From here it is a guardrail on an AI-assisted write path, and most orgs carry rules written for a different era: some too loose to catch anything, some so brittle that people route around them. Whichever you have, it is about to be exercised by a surface the original author never imagined.

The same goes for access. Copilot and Teams are two more doors into the same records, and an over-broad permission set means the same thing it always did, only reachable faster and in bulk. We wrote about how that debt accumulates in [permission set debt](/insights/permission-set-debt), and the argument has not changed. The wider [security and permissions practice](/insights/salesforce-security-permissions-best-practices) is the same homework, now with a more visible deadline.

## Where it earns its place, and where it does not

It helps to say which sellers this is for, because the honest answer is not everyone.

The strongest case is the seller who already spends the day in Microsoft 365: preparing for a customer meeting from a calendar invite, drafting a pipeline review in PowerPoint, replying in Teams. For that person, going to a separate CRM tab to look something up is friction, and bringing the record to them removes it.

The weakest case is the seller whose process depends on structure the chat surface cannot show: multi-step approvals, required related records, or a stage definition that needs a page layout to enforce. A card that updates a supported opportunity field is fine for a close-date nudge. It is a poor home for anything where the Salesforce screen was doing real work.

The practical test is to list the five things your sellers do most often in Salesforce, then ask of each whether a confirmed, rule-checked update from a chat is an improvement or a shortcut around a control. Most orgs will find a split, and that split is your pilot scope.

## Federation is the quiet one

Data Federation is the only generally available piece, and it will get the least attention, because it is a data architecture story rather than a demo.

Querying OneLake from Data 360 without moving the data means a Microsoft-side data estate can inform Salesforce-side segmentation, agents and insights without a copy that someone has to keep fresh. That is valuable, and it moves the governance question rather than removing it. The data is still governed somewhere, and the person asking in Salesforce may not be the person the Fabric administrator had in mind.

If you already run Fabric, ask who owns the connection, what is exposed through it, and what a Salesforce user can reach that they could not reach in Fabric directly. If you are earlier in your Data 360 journey, our [Data 360 implementation notes](/insights/data-360-implementation-best-practices) cover the groundwork that applies regardless of where the data lives.

## What is known, what is not, and what turns on it

The first column is what Salesforce states. The second is what we could not find published. The third is why the gap matters.

| Question | What the sources state | What is not published | Why the gap matters |
| --- | --- | --- | --- |
| Availability | Public preview, pilot and generally available, by piece | Dates for anything not already available, and which editions and regions | Decides whether this is a plan item or a note in the minutes |
| Writeback | Supported writeback needs explicit user confirmation, respects existing validation rules, and runs through authenticated user access | Behaviour with field-level security, sharing rules and flows that fire on update | Decides how much testing precedes any cohort |
| Commercials | Pricing and packaging subject to change, and availability and access governed by customer agreements | Any rate, unit or minimum, and what existing licences cover on either side | The only unknown large enough to change the adopt decision |
| Teams scope | A pilot with adaptive cards and shared deal rooms | Which opportunity fields are "supported", and how shared deal rooms handle access | Decides whether it fits a sales process with real approvals |
| Data movement | Query without data movement, and sharing into OneLake | Latency, cost on the Fabric side, and what is logged | The first question a data owner asks |
| Audit and retention | Audit trails said to be preserved in both environments | What is logged for a Copilot conversation, where it lives, and for how long | The usual reason a pilot stalls |

Two rows carry more weight than the rest. Commercials, because two vendors and two contracts is how a consumption line item acquires no owner. Audit and retention, because security will ask first, and arriving holding an announcement rather than an answer is how a pilot gets stopped by someone who was never against it.

## Two different Copilots

A small point of vocabulary that will cause avoidable confusion in meetings. The Copilot in Copilotforce is Microsoft's. When someone says "our Copilot rollout", ask which one they mean, and which of your users can reach which records through it.

The question underneath is the same whichever assistant your people use: through how many doors can they reach the same data. The answer is a property of your org.

## What it does not mean

**It does not make Agentforce redundant.** Sales Cloud in Teams uses Agentforce Coworker, and the underlying layer is Salesforce's own. If you are mid-rollout, the scoping and grounding work in [the grounding checklist](/insights/agentforce-grounding-checklist) is unaffected.

**It does not fix your data.** An assistant preparing a customer meeting or reviewing deal health reasons over the fields your team actually fills in. If stages are contested and close dates are optimistic, you will get a fluent summary of fiction.

**It does not mean you have to move quickly.** One piece is generally available and the rest are preview or pilot. Nothing degrades while you wait. The only item with a real clock is the access and validation review, and that was overdue before the announcement.

**It does not mean your Microsoft licensing question is answered.** What Copilot access, plugin entitlement or Fabric capacity you need on the Microsoft side is not covered by the Salesforce page.

## The questions to put to Salesforce and Microsoft

Take these to an account team rather than a search engine. Treat "we will come back to you" as information about maturity, not a failure of the conversation.

**Commercial.** What is billed on each side, by what unit, and does any current contract cover it. Is a Microsoft Copilot licence assumed for every user, or only some.

**Writeback.** Show, rather than describe, what happens when a validation rule fails, when a user can view but not edit a record, and when a flow fires on update.

**Teams.** Which opportunity fields can a card change, and who can see a shared deal room.

**Federation.** Who administers the connection, what is exposed through it, and how is access logged on both sides.

**Audit and retention.** What is logged for a Copilot conversation that touches Salesforce data, where, and for how long.

## Four things worth doing before it reaches you

1. **Review your validation rules as guardrails.** List the ones on opportunity and the fields a card or Copilot could touch. Ask of each whether it would catch a plausible mistake, and whether people already work around it.
2. **Run the access review you were putting off.** Not a tidy-up. An answer to "who can see and change what, and why", starting with the count of users with broad view or modify access.
3. **Name the owner.** One person across the Salesforce side, the Microsoft side and the Fabric connection, before any pilot, not after.
4. **Pick a narrow cohort with clean data.** One sales team whose pipeline hygiene you would show a customer.

## Our honest position

The direction is sensible. Meeting sellers inside the tools they already open, with writes that need a confirmation and respect your rules, is a better shape than most of what has shipped in this category, and federation that avoids another copy of the data is a real architectural gain.

It is also, outside the data piece, mostly preview and pilot. The things that would let anyone plan properly, price, dates, editions, audit and the behaviour of writes under real sharing rules, are not published.

What does not depend on any of that is the burden the design moves onto you. When the assistant writes through your rules and reads through your permissions, the quality of those *is* the quality of your AI governance. Orgs that kept them clean are in good shape whatever happens next. Orgs that did not have, once again, a reason a board will fund.

---

Sources: [Salesforce announcement, 17 November 2026](https://www.salesforce.com/news/stories/copilotforce-announcement/) · [Microsoft Copilot in Salesforce Help](https://help.salesforce.com/s/articleView?id=platform.what_is_microsoft_copilot.htm&type=5) · [Data 360 OneLake connector](https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-microsoftfabriconelake-connector.html) · [Share Data 360 data with OneLake](https://help.salesforce.com/s/articleView?id=data.c360_a_share_data_with_onelake.htm&type=5)

*Published 19 November 2026.* Availability, status labels, pricing and feature scope above reflect the Salesforce announcement and the documentation it links, as they read on that date. Where those sources were silent we have said so rather than filled the gap. Any of it may have changed by the time you read this, so confirm with Salesforce and Microsoft before you commit budget, a roadmap position, or a security sign-off on the strength of this piece.
