Solutions Architect, YouTuber, Team Lead
Microsoft Copilot’s announced Autopilot, plugins, Today experience and Microsoft IQ bring scheduled agent work, specialized capabilities and company context into a more proactive workflow. These changes matter to Microsoft 365 and business-app users, architects and administrators evaluating how agents might act across organizational data and services. Sean Astrakhan (Untethered 365) demonstrates examples of these experiences in a YouTube video.
Autopilot is presented as an agent that can run routines in the background and perform recurring work. The examples include keeping a spreadsheet current and sending a Teams message when a change is discussed. A user can also interact with an Autopilot later, including asking an example agent connected to Salesforce to update a record based on a colleague’s reply.
Routines are described as scheduled agent jobs. They can be paired with guardrails: in one example, the agent drafts a client follow-up but waits for approval before anything goes to the client. That distinction is significant for teams considering agent-driven work: the example separates preparing an action from authorizing it.
Plugins are positioned as specialized capabilities for Copilot, rather than as agents themselves. They combine skills, connectors and tools. Skills provide instructions; connectors link to systems such as Dataverse, Excel or SharePoint; tools define actions the connection can take, such as reading data or updating records. The demonstration says Copilot can invoke plugins as relevant to an operation.
The Today experience is shown as a place where Copilot suggests work instead of waiting for a user to start with a blank prompt. In the example, it draws on Dynamics 365 Sales information and proposes a task related to sales goals and pipeline opportunities. Starting the task opens Cowork, which uses plugins to gather information and prepare further work.
Microsoft IQ is presented as a shared home for organizational knowledge, including company rules and decisions that agents can refer to. The example combines that knowledge with Work IQ, Fabric IQ and Foundry IQ to surface similar insurance claims. A coworker’s judgment about handling a claim is then saved for future use. The intended value is reusable business context rather than repeatedly configuring each agent with the same rules.
The examples are aimed at people who coordinate recurring work, manage customer or sales activity, or design how agents should use company systems. Sales teams are one clear audience: the Today demonstration uses Dynamics 365 Sales data and a sales plugin. Teams using spreadsheets, SharePoint, Outlook, Dataverse or Salesforce also appear in the examples.
The demonstrations depend on access to connected business information and systems. They show an agent working with services such as Teams, SharePoint, Outlook, Dynamics 365 Sales and Salesforce, but do not establish a particular license or tenant prerequisite. Microsoft IQ is documented by Microsoft, but the examples should not be treated as a complete deployment guide; organizations will need to assess which connections and actions are appropriate for their environment.
For a plugin, the design concept is to combine relevant instructions, connections and permitted tools. That gives Copilot context about both what it should know and what it can do. For Microsoft IQ, the example’s aim is to make company rules and prior decisions available to agents when a similar situation arises.
Several important design questions remain in the demonstrations. The presenter asks whether users can customize Today’s suggestions, remove unsuitable ideas or add different ones; the demonstration does not explain how. It also raises the question of how an organization can correct or undo a saved decision in Microsoft IQ if that decision is wrong or should not become lasting guidance.
Those questions matter before teams rely on proactive suggestions or reusable decisions. Review which actions an agent may take, where approval is required, and how the organization wants to handle inaccurate or outdated guidance. The approval example offers one practical control for customer-facing actions, but it does not describe a complete governance model.
The absence of Power Platform discussion in the keynote segment should not be read as a statement that Power Platform has been discontinued. The demonstration frames the focus as Copilot and workplace collaboration, while noting that tools such as Dataverse, SharePoint and Fabric remain relevant. Teams evaluating these experiences should distinguish the new agent workflows from the existing apps and automation they already operate.
Autopilot is presented as an agent that runs scheduled Routines to handle recurring tasks. It can also be configured to request approval before an action, such as sending a client follow-up.
A plugin combines skills, connectors and tools. Skills provide instructions, connectors connect to systems, and tools define actions Copilot can take through those connections.
Microsoft IQ is described as a shared place for company knowledge, rules and decisions that agents can reference. The example combines it with Work IQ, Fabric IQ and Foundry IQ.
The demonstration raises this as an open question and does not explain whether users can remove or add suggestions.