Skip to content
Let’s talk

Salesforce Updates · 20 November 2026

Copilotforce: Salesforce meets Microsoft Copilot

What Salesforce’s Copilotforce announcement means for Microsoft 365 users: availability, practical use cases and a sensible pilot plan.

Salesforce cloud and a Copilot-inspired ribbon linked by a green glass bridge in a sunlit stone atrium

Customer work across Salesforce and Microsoft 365

For a business using Salesforce alongside Outlook and Teams, the useful question is simple: can your team act on customer information without spending the day moving between applications? Copilotforce is a new reason to examine that question—and to check the underlying processes before adding another AI tool.

What Salesforce announced

On 17 November 2026, Salesforce and Microsoft announced Copilotforce. Salesforce in Microsoft Copilot brings CRM context into conversational sales work, including meeting preparation, opportunity analysis and supported actions. The announcement also covers Teams workflows and connections between Data 360 and Microsoft Fabric.

Salesforce describes authenticated access that preserves permissions and audit trails. Supported CRM writebacks require explicit confirmation and respect validation rules. These are product commitments to verify in your own pilot, not a substitute for access testing. Read the official announcement.

What is available—and what is still being tested?

Availability stated in the 17 November announcement
CapabilityAnnounced status
Salesforce in Microsoft CopilotPublic preview / beta
Sales Cloud in TeamsPilot
Fabric OneLake data federation into Data 360Generally available
Data 360 sharing into Microsoft OneLakePublic preview / beta

Pricing, packaging, regional availability and access conditions may change. Confirm eligibility and contractual terms before purchasing or promising a rollout. Source: Salesforce’s availability roadmap.

Where could this help your team?

Adaptal’s view: start with the handovers that already cause friction. A new interface is most useful when it removes a specific piece of work, rather than giving everyone another place to ask the same question.

Preparing for a customer meeting

Consider an account manager who currently opens an opportunity, searches email, reads the previous meeting notes and asks a colleague about delivery. A sensible pilot would compare that manual preparation with an assisted brief. The test is whether the brief identifies the correct customer, separates confirmed facts from assumptions and links back to useful evidence.

Measure the time spent checking the answer as well as the time spent generating it. A brief that arrives quickly but needs extensive correction may not improve the workday.

Following up a deal review

In a second pilot, ask a sales manager to review a small, representative set of opportunities. Compare the assistant’s suggested priorities with the manager’s assessment. Include a stale close date, a missing next step and a deal with conflicting notes. These examples reveal more than a demonstration built around perfectly maintained records.

Keeping a shared decision consistent

If the team discusses a next step in a collaboration tool, decide where the final decision belongs. Salesforce should have an agreed owner and source field for that decision. Otherwise, adding AI can multiply conflicting versions of the same customer story.

Five checks before a Copilotforce pilot

  1. Name the workflow. Choose one outcome, such as a reviewed customer brief. Record the current steps and the time they take.
  2. Check customer data. Review account ownership, opportunity stages and missing fields. Resolve duplicate records that could confuse the result.
  3. Test ordinary-user access. Use representative roles, including someone who should not see a sensitive account or document. Verify both allowed and denied access.
  4. Define approval. Agree which outputs remain drafts, who checks proposed changes and how an incorrect update is corrected. Include validation failures in the test.
  5. Set a budget and stopping rule. Confirm the licences, consumption terms and support responsibilities. Decide what evidence would justify expansion—or a pause.

Do not test only with an administrator account. A pilot should reflect the permissions and working habits of the people who will actually use it. Our guide to AI agent security in Salesforce covers the access and review questions in more detail.

A practical first-pilot scorecard

This is a proposed Adaptal evaluation method, not a vendor benchmark. Select a manageable batch of real tasks and have a person review every result. Keep the task selection consistent when comparing the manual and assisted approaches.

MeasureWhat to record
AccuracyIncorrect facts, missing context and unsupported conclusions
TimePreparation, generation, checking and correction time
AccessWhether restricted records and documents stay restricted
ActionsApproval, validation and the final record change
CostApplicable licence and usage costs per accepted outcome

Review the exceptions with the people responsible for sales operations and system administration. Agree what must improve before inviting more users. Do not treat a polished answer as proof of accuracy or assume that a successful demonstration establishes a business case.

Prepare the process before expanding the tools

If your team already uses Microsoft 365 and Salesforce, Copilotforce deserves a focused evaluation. Start by identifying where customer information is hard to find, where handovers fail and where staff repeat the same administrative work.

Some of those problems may be better solved through clearer fields, a useful report or a reliable Salesforce Flow. Others may benefit from AI interpreting a conversation or assembling a draft. Our Salesforce and Claude cost guide explains that distinction.

Adaptal can help scope the workflow, review the existing configuration and define a pilot with measurable outcomes. Explore our Salesforce implementation services or ongoing Salesforce support.

Published 20 November 2026. Announcement details checked on that date. Examples and evaluation guidance are Adaptal’s analysis. Cover artwork is an original AI-generated concept illustration, not an official Salesforce or Microsoft product image.

Planning Salesforce with Microsoft 365?

Let’s choose a useful workflow, check access and define a pilot your team can measure.

Questions and answers

What should we check before starting a Copilotforce pilot?

Confirm access to the relevant capability, your licences and the current availability terms. Choose one workflow, identify its data and permissions, and agree how a person will review the results before expanding access.

Does connecting Salesforce remove existing permissions?

The announcement describes authenticated access that preserves permissions. Verify this with ordinary user roles in your pilot: check both the records people should see and those they must not access.

Should every Salesforce process use a conversational assistant?

No. A report or a Salesforce Flow may be a better fit for a fixed, repeatable process. Use an assistant where interpreting information or preparing a draft adds value, and measure the checking effort as well as the time saved.

How do we know whether the pilot is worthwhile?

Compare accuracy, total time, access controls and applicable costs against the current process. Include incomplete records and validation failures. Agree in advance what results would justify a wider rollout.

← Explore more insightsBack to top ↑