Microsoft used this year's Ignite conference to push Copilot from an assistant layered on top of Office apps toward the connective tissue of enterprise software, announcing Copilot SDK 2.0 and a new Salesforce partnership called Copilotforce on November 17, 2026.
The two announcements target different halves of the same bet: Microsoft wants Copilot to be the runtime that enterprise agents run on, and the surface where a company's existing systems of record — starting with the world's best-known CRM — become actions an agent can take. For more context on this story, see our ongoing latest AI developments.
Copilot SDK 2.0: rebuilt for multi-tenant scale
The SDK, previously called the GitHub Copilot SDK, has been rebuilt around a runtime Microsoft says can host many isolated agent sessions inside a single process. "We enhanced the Copilot runtime to support multi-tenanted, high-performance architectures," Microsoft wrote in its Command Line blog, as reported by Paul Thurrott. "It gives you direct, programmatic access to the Microsoft Copilot harness powering products across our entire portfolio for coding, non-coding, and creative apps, platforms, and services. It can be used to build agents that run anywhere and can use any inference."
The change matters because of how the first version worked. In the initial release of the GitHub Copilot SDK, every agent ran in a single container, which meant every session required a container whether or not it needed that level of isolation. With Copilot SDK 2.0, the runtime can host multiple sessions within one process, each with its own state, credentials, tools, files and history. Sessions are isolated from one another, creating a session no longer starts a container, process or virtual machine, and each session can run independently of the identity of the user who requested it — a meaningful shift for server-side products acting on behalf of many users at once.
To keep the runtime lean, Microsoft built it in Rust, the memory-safe systems language it has increasingly used for performance-critical infrastructure. The reported gains are substantial: creating a session through the TypeScript CLI previously took 5.25 seconds and now takes 55.3 milliseconds, and ten clients consumed 1.4 GB of RAM before versus 126 MB now.
For developers, the pitch is straightforward: the same harness that powers Copilot across Microsoft's portfolio becomes embeddable, with any inference backend, anywhere from a SaaS product to a command-line tool.
The rename itself carries weight. Moving the SDK out of the GitHub namespace and into the Copilot brand signals that Microsoft sees agentic development as a company-wide platform rather than a developer-tools feature — and that the interface partners like Salesforce build against is expected to outlive any single product it currently powers.
Copilotforce: Salesforce data comes to Copilot
The second announcement brings Microsoft and Salesforce — years-long rivals in CRM and enterprise software — into a formal partnership. Copilotforce, unveiled at Ignite, puts a Salesforce plugin for Microsoft Copilot into public preview with more than 38 prebuilt sales skills.
The integration works by combining two context stores. Microsoft's Work IQ, the intelligence layer that powers Copilot, supplies workplace context from Teams meetings, Outlook emails and documents in SharePoint and OneDrive. The Salesforce side contributes customer records and supported actions through authenticated Salesforce MCP access, letting sellers retrieve customer information and take actions with that combined context — a recorded account history assembled from meetings, messages and files alongside CRM data.
The governance model is split deliberately. Salesforce keeps control of customer data and actions, while Microsoft governs communications and documents. Supported writebacks to Salesforce require explicit user confirmation and must respect Salesforce's validation rules, a design choice aimed at the trust problem that has slowed agent adoption in revenue-critical workflows.
Accenture is deploying Copilotforce internally as a reference customer, with 55,000 Salesforce users expected to work through the integration.
A rivalry becomes a distribution deal
The partnership is striking given the companies' history. Microsoft Dynamics competes directly with Salesforce in CRM, and the two have spent the past several years racing to define what an AI sales assistant does. Copilotforce effectively splits that question: Salesforce's data and actions live inside Microsoft's agent surface, because that is where enterprise workers already spend their day.
For Salesforce, the deal meets customers inside Copilot rather than waiting for them to open a CRM tab. For Microsoft, each integration like this strengthens the argument that Copilot is the front door to enterprise software generally — not just to Microsoft's own applications.
What to watch
Both announcements are early-stage: the Copilotforce plugin is in public preview, and the SDK's multi-tenant runtime is newly shipped. The open questions are operational. Whether the Rust runtime's performance numbers hold under real multi-tenant production load, how enterprises govern agents that write back to systems of record, and whether sellers accept confirmed agent actions in their CRM will determine if either announcement changes daily work — or remains conference-stage material.
What is already clear is the direction: the Copilot platform is being repositioned from an Office companion to infrastructure other companies build on, and Microsoft is willing to partner with its oldest CRM rival to prove it.
---
Stay Ahead of AIGet the latest AI news, analysis, and breakthroughs — all in one place.
Read more AI news →