Microsoft made Home, Office in Copilot and Copilot Managed Runtime generally available at Ignite on November 17, 2026. Autopilot is beginning its rollout to Frontier customers, while Copilot Code is scheduled to reach general availability in the following weeks. Salesforce support is arriving as a preview plugin. Those distinctions are central to understanding Microsoft’s Copilot announcement.
The larger change is how these AI products fit together. Microsoft is positioning Copilot as an operating system for work: a place to ask questions, create documents, build applications and delegate ongoing tasks. Workspaces supplies a shared collaboration environment, Microsoft IQ manages organizational context, and Agent 365 adds oversight and cost visibility.
For enterprise buyers, the useful takeaway is a deployment sequence. The everyday interface is generally available; autonomous work and some integrations require a more selective rollout.
Copilot Release Status at a Glance
Microsoft’s announcement combines shipping products, limited rollouts and previews. Here is the release map as of November 17, 2026:
| Capability | Announced status | Practical planning implication |
|---|---|---|
| Copilot Home | Generally available | Evaluate as the main entry point for Chat and Cowork. |
| Office in Copilot | Generally available | Evaluate document, spreadsheet and presentation workflows inside Copilot. |
| Copilot Managed Runtime | Generally available | Assess the managed environment for hosting and managing apps. |
| Autopilot | Beginning rollout to Frontier customers | Confirm access before scheduling an autonomous-agent pilot. |
| Copilot Code | General availability expected in the coming weeks | Treat broad availability as upcoming, without assuming a fixed launch day. |
| Salesforce in Copilot | Preview | Validate the connector and supported sales workflows before depending on it. |
| Today | Private preview in Copilot and Outlook | Keep it separate from Home’s generally available feature set. |
| Copilot Workspaces | Announced; the cited overview gives no explicit release stage | Verify availability before making it a rollout dependency. |
The main Copilot post supplies the release stages for Home, Office, Runtime, Autopilot, Code and Today. Microsoft’s Ignite overview confirms Salesforce’s preview status and describes Workspaces.
These are Microsoft’s published availability claims, not independent measurements of reliability or productivity.
Two distinctions deserve particular attention. Managed Runtime being generally available does not make Code generally available. The hosting environment and the app-building experience have separate release schedules. Likewise, Home’s general availability does not extend to Today, the proactive briefing experience inside it.
Home and Office Form the Generally Available Core
Copilot Home brings Chat and Cowork into one starting point. Employees can ask a question, review recent activity, resume work or hand off a more involved workflow.
Its single composer uses Microsoft’s Auto routing system to select models and the amount of processing effort for a task. Microsoft says the routing balances quality, speed and cost. For more complex requests, Auto may recommend moving from Chat to Cowork; the user agrees before the task transfers.
Employees can also manually select models from OpenAI or Anthropic, subject to organizational policies. Microsoft has not supplied independent comparative measurements in these announcements, so the routing description should be read as a product capability claim, not proof of better economics.
Office in Copilot brings Word, Excel and PowerPoint capabilities directly into the Copilot app. Microsoft says users can create, edit and coauthor files there, with Microsoft 365 permissions, sensitivity labels and compliance controls inherited from the start. See the Home and Office announcement for those details.
I’d start an enterprise evaluation here. These features cover familiar work and give administrators a clearer baseline for assessing access controls and collaboration before introducing agents that act over longer periods.
Today requires a separate decision. Microsoft describes it as a command center across mail, calendars, Teams, meetings and tasks, with prepared drafts and proposed follow-ups. Its private-preview status means organizations should not promise those capabilities as part of an ordinary Home deployment.
Autopilot Changes the Delegation and Security Model
Autopilot is designed for work that continues between prompts. Microsoft says it can monitor Teams channels, follow up on email, run recurring tasks and manage projects. Its supplier-review example includes building a schedule, preparing meetings and asking stakeholders for updates.
The important technical detail is its identity. Microsoft says each Autopilot:
- Lives in the customer’s tenant with its own identity, memory and tools.
- Has a Microsoft Entra Agent ID and a named manager.
- Can have its access scoped or be blocked by IT.
- Records sign-ins and actions under its own identity.
Those controls make autonomous activity attributable to a specific agent. They also give administrators a defined way to restrict or stop it. They are documented controls, however, not evidence that every delegated workflow will run correctly. Autopilot is only beginning to roll out to Frontier customers.
My view is that the named-manager requirement is especially consequential. A recurring agent needs someone responsible for its scope and continued usefulness. Giving it an identity makes auditing possible; assigning an owner creates somewhere for that accountability to land.
A sensible initial workflow would therefore have a bounded task, a clear owner and an agreed stopping condition. That is a deployment recommendation derived from Autopilot’s persistent operating model, not a Microsoft requirement stated in the announcement.
Workspaces Adds a Shared Place to Coordinate
Copilot Workspaces addresses collaboration between people and agents. In Microsoft’s published Ignite keynote, it is described as a shared environment where people, their agents and other colleagues work toward a common goal with shared context.

Autopilot and Workspaces serve different purposes. Autopilot performs ongoing work. Workspaces provides the collaborative setting in which people and agents can coordinate.
A project with several participants needs more than separate chat histories. Shared context can help participants work from the same project information, although the announcement does not provide enough implementation detail to assess synchronization behavior or conflict handling.
How Microsoft IQ and Agent 365 Fit Together
Microsoft’s product names describe several distinct layers. Keeping them separate makes the architecture easier to evaluate.
Work IQ supplies work context within Copilot. Microsoft describes it as understanding the people, relationships, documents, emails, meetings, chats and projects that shape an organization’s work.
Microsoft IQ is the broader enterprise context-management platform. Microsoft says it brings together information across Fabric, Foundry, Microsoft 365 and third-party sources. Business plugins package organizational knowledge into reusable context, skills and tools that can be shared across the business. The company presents this as a way to capture, govern and reuse institutional knowledge in .
Frequently Asked Questions
3 questions
1Which Copilot Features Are Generally Available?
Microsoft says Home, Office in Copilot and Copilot Managed Runtime became generally available on November 17, 2026. Code is scheduled for general availability in the following weeks.