Microsoft Copilot’s Ignite updates bring Chat, Cowork and more Office actions into a connected work experience, while adding proactive briefs, app building and agent analytics. They matter to Microsoft 365 users exploring AI-assisted work, as well as administrators and business stakeholders weighing access, spending and oversight. M365 Copilot Connection demonstrates several of the experiences and describes where they stand.
The announcements span everyday Copilot use and broader organizational management. In Copilot Home, Chat and Cowork sit within centralized navigation; Chat can also plan a multi-step business process and suggest moving a task to Cowork. That suggestion gives users a choice rather than automatically handing the task off.
Office actions are also moving into Copilot Chat. The demonstration uses a workbook as context, then asks Copilot to create a status chart in a preview where the chart can be inspected and adjusted. The broader idea is to handle more file work without switching immediately into a dedicated Office app, though the experience does not replace those apps for every task.
Three other updates focus on work that happens around a prompt: Today is intended to surface priorities and proposed actions, Cowork task delegation can split work across sub-agents, and Autopilot is designed to continue work in the background. Workspaces provide a shared place for project context, files and activity. Copilot Code supports creating business applications, while Agent 365 Business Analytics is intended to help organizations examine AI use and value.
These changes concern both people using Copilot and the teams responsible for enabling and managing it. The clearest prerequisite in the demonstrated experiences is spending configuration: Cowork and Copilot Code are described as consumption-based, and users need an enabled spend policy. Users without one should check with their administrators before expecting to use those capabilities.
Today is in Frontier private preview. Autopilot and Agent 365 Business Analytics are also described as rolling out through Frontier, so access is not the same as a broadly available feature. Copilot Workspaces is identified in the research as part of Microsoft's Frontier early-access program. The updates therefore include a mix of experiences at different stages, rather than one change that every organization can turn on at once.
For administrators and business stakeholders, the practical questions include who can access consumption-based features and how the organization will assess their cost and value. The announced Business Analytics report is aimed at understanding AI use and value; it should not be confused with an indication that every organization already has access to the report.
In the demonstrated Copilot Chat experience, Chat and Cowork appear as choices in the prompt area. When a request looks like a longer, multi-step task, Chat can offer the option to send it to Cowork or continue in Chat. The user makes the decision. The demonstration also shows Chat planning a multi-step process, rather than presenting only a direct response.
Workspaces organize activity and shared context around a team project. The demonstrated interface includes an activity view, file access, and options such as Dashboard and Report; its chat panel can also be moved. Copilot Code follows a different path: a user describes an app or business solution, reviews the generated result and can inspect session files and source code. Its /cost skill can report an estimate for a Code session, as shown in the demonstration.
Today is designed to bring relevant work activity to the user, including context such as an email chain or a meeting that may need attention. Autopilot is described as a personal agent that can work in the background, with interactions in Outlook and Teams. Agent 365 Business Analytics is aimed at stakeholders looking to understand AI usage and value across an enterprise.
These capabilities do not remove the need to use the full Office apps. The demonstration notes that some tasks still require Word, Excel or PowerPoint, so users should check whether the requested action is supported in Copilot Chat before relying on it as their only editing surface. A preview of a workbook or a generated first draft is not the same as a finished, validated deliverable.
Access and costs also matter. Cowork and Code require consumption spending to be enabled, and preview-stage features such as Today and Autopilot may not be available to all users. Check the experience in your tenant and follow your organization's policies before assigning work to an agent or generating an application.
Finally, human review remains part of the workflow. The demonstration specifically advises users to revise drafted email text before sending. For generated charts, apps and other output, review the content and behavior, then continue in the dedicated Office application or refine the prompt when the in-Copilot result does not meet the need.
Yes. The demonstrated Cowork experience requires consumption spending to be enabled through a spend policy. Users should check with their administrator if they cannot access it.
Today is in Frontier private preview. It is designed to surface work priorities and proposed actions.
It can handle some actions, such as creating a chart from a workbook in the demonstrated preview. Some tasks still require Word, Excel or PowerPoint.
Copilot Code helps users create business applications from descriptions and review generated output and source files. It is a consumption-based experience requiring a spend policy.