All articles

Agentforce

Agentforce Coworker in Teams: plan the rollout

Evaluate Coworker in Microsoft Teams with permission checks, bounded workflows and a clear distinction between available and planned features.

Putting an agent in Teams changes where employees ask for work. It doesn’t remove the need to test what the agent can do.

Salesforce’s November 5, 2026 announcement lists Agentforce Coworker in Microsoft Teams for general availability during November. It separately describes Microsoft 365 connectivity and lists scheduled tasks as expected in December. Confirm availability in your org rather than treating the announcement as proof that every feature is enabled for every tenant.

Choose one employee task

A useful first pilot might prepare a renewal brief from permitted customer records and connected documents. Define the sources, expected output and which proposed actions require review.

Separate drafting from execution. Preparing a customer message, updating an Opportunity and sending the message are different permissions and outcomes. A polished brief doesn’t prove that a subsequent write is authorized or correct.

Keep the pilot’s task narrow enough that reviewers can check its evidence. Record which facts came from Salesforce, which came from Microsoft 365 and how conflicting or stale information should be handled.

Test identity across the connection

Use employees with different access, including someone who must not see a selected account or document. Verify that the connected experience preserves the intended access boundaries.

Also test a revoked connection, a missing document and an action the employee cannot perform. The response should explain a bounded failure without revealing protected data. Don’t use a shared administrator connection as evidence that ordinary employee access works.

Inspect where conversation history and operational logs are available, who can read them and how support will investigate an unsuccessful task. Those responsibilities cross the chat surface and the systems performing the work.

Budget for the actual task mix

The announcement includes a per-user pricing option, while Salesforce also offers consumption models elsewhere in Agentforce. Ask for the applicable SKU, prerequisites and included usage for your proposed deployment. Avoid comparing a seat price with another platform’s action price as though they buy the same workload.

Measure successful task completion, reviewer corrections, blocked requests and the platform usage attributable to the pilot. Keep those as observed results rather than borrowing another customer’s productivity figures.

Release to a limited employee group with a clear support owner. Expand only after the evidence shows that the chosen task works with ordinary permissions and realistic data. The AI-agent implementation service describes how to structure that evaluation.

Keep reading

All articles