Microsoft wants Copilot to go beyond being just a place for generating ideas, summaries, or responses, and become also the space where real work is performed. The company has announced new capabilities so that agents in Microsoft 365 Copilot can integrate business applications directly into the conversation, reducing the constant switching between tabs, tools, and contexts that still characterizes much of daily work in organizations.
The proposal addresses a very familiar problem: a user asks Copilot to prepare a campaign but then needs to open a design tool; a salesperson summarizes an opportunity but must log it into the CRM; a manager reviews a request but approves it in another system. Microsoft suggests that its agents can bridge that gap between recommendation and action by bringing applications like Adobe Express, Figma, Miro, monday.com, Optimizely, Wix, Base44, Box, or Coursera into the very conversational flow of Copilot.
From responder assistant to acting agent
This announcement reinforces a clear trend in Microsoft’s strategy: Copilot is no longer viewed solely as a query interface but as a platform for agents connected to business tools, data, and processes. In this model, the user doesn’t just ask what to do but can initiate actions from the same chat, interact with embedded visual components, or instruct the agent to execute a task under supervision.
This distinction is significant. Until now, many AI productivity experiences focused on content creation or information summarization. While helpful for saving time, they didn’t fully address subsequent friction: moving data between applications, recreating context, copying information, opening external tools, and manually completing workflows. Microsoft aims for Copilot to serve as a common entry point for that operational work.
According to Microsoft, connected applications within Microsoft 365 Copilot can display visual and interactive experiences within the chat. For example, users can generate and edit creative assets, create diagrams, review documents, update records, or manage campaigns without leaving the Copilot environment. While promising, this should be approached cautiously: it doesn’t eliminate the need for governance, permissions, integration, and human oversight, but it can significantly reduce the context-switching that hampers productivity.
Which applications are coming to the Copilot flow
Microsoft has highlighted several examples already available or announced within the Microsoft 365 Agent Store. The range shows the company isn’t limiting agents to traditional office tasks but expanding into areas like creativity, collaboration, training, project management, marketing, data, and application building.
| Application | Use within Microsoft 365 Copilot |
|---|---|
| Adobe Express | Create, preview, and edit creative assets directly from chat, with future integration of Acrobat workflows. |
| Box | Preview Box files and prepare MCP-based flows, such as creating hubs or extracting data. |
| Coursera | Access professional learning and training connected to work tasks and priorities. |
| Figma | Turn conversations into FigJam diagrams generated with AI. |
| Miro | Create boards, diagrams, timelines, notes, and visual flows from a conversation. |
| monday.com | Display interactive boards and items to understand project status and act in context. |
| Optimizely | Create campaigns, generate and edit images, analyze experiments, and run agents. |
| Wix | Create and manage websites using natural language. |
| Base44 | Build applications from a conversation with Copilot. |
These examples illustrate Microsoft’s goal: for Copilot to be less an isolated AI layer and more an integrated work interface connected to the software companies already use. For instance, with Adobe Express, users can work on creative assets directly within the Copilot experience, make edits, and keep the workflow within Word, PowerPoint, or Excel documents.
MCP, Agent Store, and developers’ role
A key part of the announcement is the mention of MCP Apps and Apps SDK. Microsoft positions these tools as a way for development teams to connect Copilot with applications, workflows, and systems tailored to each organization. This is crucial because the true value of agents won’t just be in integrations with well-known providers, but in their ability to interface with internal processes, vertical tools, and proprietary enterprise software.
The use of MCP aligns with a broader industry trend: creating a common layer that enables models and agents to connect to external tools more systematically. Practically, this opens the door for Copilot to do more than understand documents or emails—it can operate with business systems, provided there are appropriate permissions, connectors, and controls.
For developers, the opportunity is twofold. They can create agents that bring existing applications into Microsoft 365, or craft new native experiences where chat is the primary interface and the application is embedded as an action, visualization, or approval component. This could transform how many internal tools are designed: reducing standalone screens and enabling more integrated workflows within conversations.
Productivity with enterprise control
This announcement also clearly addresses IT administrators’ concerns. Microsoft emphasizes that administrators will be able to deploy and manage these experiences via the Microsoft 365 admin center, with visibility and control to safely scale agents across the organization. This aspect is as vital as the user experience because, in enterprise environments, it’s insufficient to allow any agent to connect to any application.
The risks are evident: unauthorized data access, automated actions without oversight, context errors, process duplications, loss of traceability, or over-reliance on misconfigured agents. Therefore, the success of this model depends less on the demo’s wow factor and more on permissions management, auditing, application approval, identity management, and compliance.
Microsoft’s approach is precisely to enable AI’s integration into actual workflows without sacrificing control. If they balance user convenience with IT governance, Copilot could become a highly resilient operational layer within the Microsoft 365 ecosystem.
A new era for business applications
This evolution fundamentally shifts the relationship between user, application, and agent. Previously, workers opened an app to perform a task. Now, the task can begin within a conversation, and the application appears as a contextual capability within that chat. Business software isn’t disappearing—it may just become less visible as the main destination.
This shift could have major implications for enterprise software vendors. Applications that integrate well with Copilot will be closer at decision time to the user, while those that don’t risk being left out of the new conversational workflow. Essentially, Microsoft isn’t just improving Copilot; it’s redefining the showcase through which many business tools are accessed.
The concept of “working without switching windows” isn’t new, but agents give this idea a new dimension. No longer just about embedding buttons or connectors but enabling conversations to evolve into concrete actions within enterprise systems. If this approach matures, Microsoft 365 Copilot could transition from a universal assistant to a kind of smart desktop for corporate productivity.
Frequently Asked Questions
What are agents in Microsoft 365 Copilot?
They are Copilot extensions linked to specific applications, data, or processes. They allow performing particular tasks within the chat, such as generating content, querying information, updating records, or starting workflows.
What applications are integrated with Copilot via agents?
Microsoft has highlighted integrations with Adobe Express, Box, Coursera, Figma, Miro, monday.com, Optimizely, Wix, and Base44, among others available or announced in the Microsoft 365 Agent Store.
What is the benefit of working with applications inside the Copilot chat?
Mainly, it reduces context switching. Users can go from an idea or inquiry to a specific action without opening multiple tools, copying info, or manually reconstructing context.
Can organizations create their own agents for Copilot?
Yes. Microsoft indicates that development teams can use MCP Apps and Apps SDK to build integrations and agents that connect Copilot with internal tools, data, and workflows.
via: microsoft