Guide
Copilotforce readiness: get your Salesforce org ready for Microsoft Copilot
Copilotforce brings Salesforce into Microsoft Copilot and Teams. Copilot can only see and change what each user’s Salesforce access allows, and every change it writes back has to pass your validation rules. So your org’s permission sets, sharing and validation rules are now the security model for Salesforce in Copilot. Getting ready means making sure they say what you mean.
By VanguardOps, written by a Salesforce architect with 13+ years in enterprise orgs. Updated November 18, 2026.
What is Copilotforce?
Salesforce and Microsoft announced Copilotforce at Microsoft Ignite on November 17, 2026. It has three parts, and they are at different stages.
| Part | What it does | Status |
|---|---|---|
| Salesforce in Copilot | What it does: A plugin that brings Salesforce data and prebuilt sales skills, such as pipeline and deal reviews, into Microsoft Copilot | Status: Public preview, no general availability date |
| Sales Cloud in Teams | What it does: Work with Sales Cloud inside Microsoft Teams, with updates synced back to Salesforce | Status: Pilot, with an open beta planned |
| Data 360 and Microsoft Fabric | What it does: Zero-copy access between Salesforce Data 360 and Fabric OneLake | Status: Querying OneLake from Data 360 is generally available; sharing Data 360 data into OneLake is in public preview |
Why does your Salesforce setup decide what Copilot can do?
Because Salesforce in Copilot runs on each user’s own access. Three parts of your org’s setup carry straight over.
- Access. Profiles, permission sets, sharing and field-level security decide what each person can see in Copilot. If a sales rep can see every account in Salesforce today, Copilot can summarize every account for them tomorrow. Access that was too broad but hard to find becomes easy to find.
- Validation rules. Every change Copilot writes back needs the user’s approval and has to pass your existing validation rules. Rules that are missing let bad updates in. Rules that are tangled or vague block good updates and leave the seller guessing why.
- Automation. A change written back from Copilot is still a change to a Salesforce record, so the flows and triggers on that object run as usual. Several automations stacked on the same object make the result harder to predict, wherever the change started.
Copilotforce readiness checklist
Eight checks an admin can run in Setup before turning Salesforce in Copilot on for anyone. Start with the objects sellers touch most: accounts, contacts, opportunities and activities.
- Org-wide defaults. In Setup, open Sharing Settings. Any sales object set to Public Read/Write or Public Read Only is visible to every internal user, and so to Copilot on their behalf. Make sure that is what you intend.
- Sharing rules. On the same page, review the sharing rules on accounts and opportunities. Old rules written for one team often reach far more people than they were meant to.
- View All and Modify All. Find the profiles and permission sets that grant View All Data, Modify All Data, or View All and Modify All on sales objects, and count who holds them.
- Permission sets nobody can explain. Remove permission sets nobody holds, and add a description to each one that stays, saying who it is for.
- Field-level security on sensitive fields. Check who can read fields such as discounts, margins, contract terms and personal details. If people shouldn’t see them in Copilot, they shouldn’t see them in Salesforce.
- Validation rules on sales objects. Confirm the rules that protect your data are active, split up rules that are long or deeply nested, and rewrite error messages so they say exactly what to fix.
- Automation on sales objects. For opportunities and accounts, list every flow, Apex trigger and workflow rule that fires when a record changes. Where several stack on the same event, consolidate them before more updates start arriving from Copilot.
- Connected apps. In Setup, open Connected Apps OAuth Usage. Look for apps with the ‘full’ OAuth scope, no IP restrictions, or tokens nobody has used in months, so the new connection isn’t sitting among old ones nobody owns.
What does a VanguardOps scan check today?
A scan reads how the org is built, never its customer records, and covers most of this checklist automatically. It counts the people who hold broad access without reading who they are. Every finding comes with a fix cost and a 3-year cost.
| Area | What the scan flags | Checklist item |
|---|---|---|
| Org-wide sharing | What the scan flags: Accounts, contacts, opportunities, leads or cases set to Public Read/Write, so every user can edit every record. Public Read Only is shown in the report but not flagged | Checklist item: 1 |
| View All and Modify All | What the scan flags: Modify All Data held by more than 5 active users, View All Data by more than 10, or Modify All on accounts, contacts, opportunities, leads or cases by more than 10 | Checklist item: 3 |
| Permission sets | What the scan flags: Custom permission sets nobody holds and that aren't in a permission set group; permission sets with no description | Checklist item: 4 |
| Validation rules | What the scan flags: Rules whose error message runs past 200 characters. The scan doesn’t read rule formulas today, so check long or deeply nested formulas by hand | Checklist item: 6 |
| Automation | What the scan flags: Two or more flows, Apex triggers or workflow rules firing on the same object and record event, plus Process Builder processes and workflow rules still active | Checklist item: 7 |
| Connected apps | What the scan flags: Apps with the 'full' OAuth scope, no IP restrictions, refresh tokens unused for 180 days, or no description | Checklist item: 8 |
Permission sets and validation rules are also two of the areas in the Agentforce readiness score, so the same cleanup counts twice.
What doesn’t the scan check?
Checklist items 2 and 5. A VanguardOps scan does not read sharing rules, the role hierarchy, field-level security, or system permissions other than View All Data and Modify All Data today. It also doesn’t inspect the Copilot plugin or your Microsoft 365 settings. Run those checks by hand with the list above.
Common questions
- What is Copilotforce?
- Copilotforce is a Salesforce and Microsoft partnership announced at Microsoft Ignite on November 17, 2026. It brings Salesforce customer data and sales workflows into Microsoft Copilot and Teams, and connects Salesforce Data 360 with Microsoft Fabric.
- Is Copilotforce available now?
- Partly. As reported on November 18, 2026, the Salesforce in Copilot plugin was in public preview with no general availability date, Sales Cloud in Teams was in a pilot with an open beta planned, and no pricing or licensing had been announced. Check the Salesforce announcement for the current status.
- Can Microsoft Copilot see Salesforce data a user can't?
- No. Salesforce in Copilot works through each user's own authenticated access, so Copilot can only see and change what that user's Salesforce permissions and sharing allow. That also means any access that is too broad in Salesforce is too broad in Copilot.
- Can Copilot change Salesforce records?
- Yes, with the user's approval. Any change written back to Salesforce needs the user to confirm it, and it has to pass the org's existing validation rules.
- Does VanguardOps check Copilotforce readiness?
- It checks most of it. A scan flags accounts, contacts, opportunities, leads and cases that every user can edit, more people than an admin team needs holding View All Data, Modify All Data or Modify All on those objects, permission sets nobody holds or nobody has described, validation rules with very long error messages, automations stacked on the same object and event, and connected apps with the 'full' OAuth scope, no IP restrictions or unused refresh tokens, and puts a dollar cost on each finding. It does not read sharing rules, the role hierarchy or field-level security today, so check those by hand.
- How is Copilotforce readiness different from Agentforce readiness?
- Agentforce runs agents inside Salesforce; Copilotforce lets people work with Salesforce from inside Microsoft Copilot and Teams. Both lean on the same foundations: access that matches each person's job, validation rules that catch bad updates, and automation that behaves predictably when a record changes.