Can Microsoft Frontier Program Copilot Cowork Agent Delegate Tasks to Other Copilot Agents?
Hi everyone, I'm currently exploring the capabilities of Copilot Cowork that is available through the Microsoft Frontier Program, and I'm trying to understand whether a multi-agent orchestration pattern is officially supported. My Use Case I want users to interact with only a single, central Copilot Cowork agent. For example: User asks the Cowork agent to create or update a Jira ticket. Instead of Cowork handling the Jira operation directly, it delegates or hands off the task to a dedicated Jira Copilot Agent. The Jira agent performs the required actions and returns the result. The Cowork agent then presents the final response back to the user. Similarly, I would like to have specialized agents for: Jira ServiceNow Knowledge Management HR Operations Internal IT Support Other business systems The goal is to have Cowork act as an intelligent orchestrator/router while specialized agents handle domain-specific operations. Questions Is agent-to-agent delegation or handoff officially supported in Copilot Cowork (Frontier Program)? Can Cowork directly invoke another Copilot Studio agent? Is there any built-in multi-agent orchestration framework available today? If this is supported, what is the recommended architecture and implementation process? If it is not currently supported, what workarounds are people using? Power Automate? Agent as a tool/action? Custom APIs? Azure AI Foundry / Azure AI Agent Service? Other approaches? I'm specifically looking for guidance from anyone who has worked with Copilot Cowork in the Frontier Program, since the documentation and public examples seem to focus mostly on standalone agents. Any insights, architecture diagrams, documentation links, or real-world experiences would be greatly appreciated. Thanks!
Succession Planning in Microsoft 365?
Hi everyone. I'm looking to implement some of our core HR practices like performance management, talent reviews, natively inside our Microsoft 365. The one that challenges me the most currently is succession planning. Do you think I can set something up where managers can evaluate succession candidates through Copilot, build succession plans on SharePoint, etc? Does anyone have any experience with this? I am also open to suggestions for any succession planning apps or software if doing it manually could be too complicated. However in that case, it would have to be a pretty native integration.
Copilot in Edge needs direct export integration
While using Copilot in Microsoft Edge, I noticed a key limitation: there is no option to directly save or export text snippets or summaries to OneDrive, Word, or OneNote. Users must copy manually, which breaks the reading flow and reduces productivity. Competitor comparison: Claude → PDF export, integration with Notion and Drive ChatGPT → PDF/DOCX export, integration with Google Drive Gemini → Automatic export, integration with Google Drive Copilot (Edge) → Only copy/paste or browser PDF, no native integrationArchitectural: Copilot should detect missing source data, avoid inference, and surface uncertainty.
Users expect the AI to detect when it lacks source data, avoid inference, surface uncertainty, and adapt to environmental constraints like character normalisation. These behaviours materially improve trust and usability. I’ve been working with Copilot on structured data extraction from a PDF and noticed a behaviour that seems like an architectural gap rather than a simple bug. Copilot attempted to infer table structure from a template when it did not have access to the actual source data. It produced confident but incorrect output instead of signalling that the source was unavailable. Additionally, Copilot attempted to output TAB‑delimited data, but the MS365 environment silently normalised TABs to spaces, and Copilot did not detect or adapt to this constraint. Recommendation: Copilot should proactively: detect when it lacks source data avoid inference when accuracy is expected surface uncertainty explicitly detect environment‑specific formatting limitations (e.g., TAB stripping) adapt output formats automatically These behaviours would materially improve trust, reliability, and user experience.
Using Copilot meeting summaries for performance reviews - how?
Our HR team had this idea to use Copilot meeting recaps as input for performance reviews. Like, if a manager had 20 meetings with a direct report over the quarter, couldnt Copilot help surface key contributions and discussion themes? The problem is theres no way to aggregate multiple meeting summaries into something useful for a review. Each recap is a separate thing in each meeting. Has anyone figured out a workflow or workaround for this?
Got Copilot to use goal progress when drafting review feedback?
So I've been trying to experiment with how I use Copilot for performance management, reviews, goals, etc. When I manually feed goals, feedback results, etc into Copilot, it drafts pretty decent performance reviews. Now Im curious. Can I automatically feed these into copilot from any HR platform with API's or something? So it automatically views goal progress and drafts review feedback? I know if Viva Goals was still available, I would be able to do something along these lines. Anyone tried this?Copilot pulling last weeks 1:1 action items into this weeks agenda, possible?
Spent 3 hours yesterday trying to get Copilot to pull open action items from last weeks 1:1 OneNote page and turn them into this weeks agenda. Gave up. Is this a prompt problem or just not possible with the current connectors?
Copilot automation assumes OneDrive—hidden productivity cost in Google‑first environments
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } We’re a Google‑first organization with a limited Microsoft 365 tenant. After recent Copilot updates, automation suggestions appear everywhere and feel “easy,” but nearly all meaningful automation requires files to live in OneDrive or SharePoint. In a hybrid environment, this creates hidden costs: duplicate file management, copying between systems, increased version/corruption risk, and hours of admin work just to discover limitations mid‑workflow. Copilot looks capable, but the storage and identity prerequisites aren’t explicit up front, so users lose time and trust. Are there plans to better support hybrid scenarios (for example, Google Drive as a system of record), or to provide clearer in‑product guidance before suggesting OneDrive‑only automations?
Proposal for a Unified Copilot Architecture and Tiered AI Assistant Model
Submitted by: Craig D. Evans Detroit, Michigan Executive Summary This proposal outlines a strategic redesign of Microsoft Copilot that transforms it from a collection of isolated chat instances into a unified, persistent, account based artificial intelligence assistant. The proposed architecture positions Copilot as the central intelligence that operates all Microsoft Office applications, maintains long term memory, and follows the user across all devices. This model introduces a tiered pricing structure that creates a scalable revenue engine while strengthening Microsoft’s long term dominance in productivity software. The proposal also introduces the concept of a dual AI verification system, in which Copilot performs tasks and a secondary model provides independent review. This structure increases reliability, reduces errors, and enhances user trust. Problem Statement The current Copilot experience is fragmented. Each application instance behaves as a separate assistant with limited continuity, limited memory, and limited cross application intelligence. Users must repeatedly re explain context, re establish preferences, and manually coordinate tasks across Word, Excel, PowerPoint, Outlook, and other Microsoft 365 applications. This fragmentation reduces efficiency, increases cognitive load, and prevents Copilot from functioning as a true personal assistant. It also limits Microsoft’s ability to monetize Copilot at scale, because the product does not yet offer a unified, persistent experience that users would be willing to subscribe to at higher tiers. Vision The vision is a single, persistent Copilot identity that the user logs into, similar to any modern online service. This identity follows the user across all devices and applications, retaining memory, preferences, formatting rules, workflows, and ongoing projects. In this model, Copilot becomes the central intelligence that operates the Microsoft Office ecosystem. Office applications become the tools, and Copilot becomes the operator. This transformation elevates Copilot from a chatbot to a long term digital assistant that remains with the user for decades. Functional Overview 1. Persistent Copilot Identity A single Copilot account that retains: Long term memory User preferences Formatting rules Writing style Project context Cross application workflows Templates and document structures This identity behaves like any other modern login system, such as Amazon, Walmart, or email services. 2. Copilot as the Central Intelligence of Office Copilot should be capable of: Opening and managing Word documents Applying templates and formatting Building PowerPoint presentations Managing Excel formulas and data structures Organizing files and directories Coordinating tasks across applications Executing workflows on behalf of the user Office becomes the body. Copilot becomes the brain. 3. Cross Device Continuity The user logs into Copilot once, and the assistant follows the user across: Desktop Laptop Mobile Web Cloud environments This creates a seamless, continuous experience. Tiered Pricing Model A tiered structure creates a scalable revenue engine and aligns with Microsoft’s existing subscription model. Tier 1: Free Copilot Basic chat No memory No continuity Limited functionality This tier serves as the entry point that encourages users to upgrade. Tier 2: Copilot with Memory and Formatting Persistent memory Document formatting intelligence Writing style retention Basic cross application awareness This tier provides immediate value and will attract a large user base. Tier 3: Cross Device Copilot Identity Full continuity across devices Unified assistant experience Project level intelligence Long term context retention This tier becomes the premium personal assistant model. Tier 4: Copilot as Full Office Manager Complete control of Word, Excel, PowerPoint, Outlook Workflow automation File management Multi application coordination Enterprise grade productivity This tier becomes the flagship offering for professionals and businesses. Optional Tier: Dual AI Verification (Copilot + Reviewer Model) Copilot performs tasks. A secondary model independently reviews output for: Accuracy Formatting Logic Consistency This reduces errors and increases trust. It becomes a high value premium tier. Competitive Advantage This architecture provides Microsoft with several strategic advantages: A unified assistant that no competitor currently offers A multi tier revenue structure that scales with user needs A long term relationship between user and assistant Increased adoption of Microsoft 365 subscriptions Strong differentiation from competing AI products Reduced user churn due to persistent memory and continuity This model positions Microsoft as the leader in personal and professional AI assistance. Long Term Strategic Value A persistent Copilot identity ensures that users remain within the Microsoft ecosystem for decades. As the assistant accumulates memory, preferences, and workflows, the cost of switching to another platform becomes extremely high. This creates: Long term subscription stability Increased enterprise adoption Stronger user loyalty A durable competitive moat Copilot becomes not only a feature, but a lifelong digital partner. Closing Statement I respectfully submit this proposal as a long time user who believes that Microsoft has the opportunity to define the future of personal and professional artificial intelligence. A unified Copilot identity, combined with a tiered pricing model and a dual AI verification system, will create a powerful, scalable, and enduring platform that strengthens Microsoft’s leadership in productivity software. Submitted by: Craig D. Evans Detroit, Michigan
File Share Connector users not mapping
Hi everyone, In need of some help here. I've setup an on-prem file share connector following this guide: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/fileshare-connector I can see the indexed items in my test folder, but, we can't crawl that data because the users are not mapping for some reason. I've been testing using the NTFS file permissions option. Has anyone had any success with using this option to sync/map users to the connector? If so, what were the requirements? The users are AD to entra id connect synced and the group I created is also AD to entra id connect synced as well. I applied ntfs perms to the test folder directly using the synced identity and tried using the group and the full crawl still does not populate users. I am not using nested groups neither. I also tried removing built-in groups such as administrators, authenticated users, etc. I've had a ticket open for weeks with Microsoft now with no answers.