Forum Widgets
Latest Discussions
Removal of Copilot Chat Availability in M365 Apps?!?
Received a post in Message Center today and would like clarification as to what capabilities Copilot Chat will retain as it is unclear from the message. This is a huge impact to users who have already adopted Copilot Chat in Word, Excel, PowerPoint and OneNote as well as training materials (both our own and those provided here by Microsoft). Will users be able to access Copilot Chat (basic) via pinned app in M365 apps? Will users only be able to access via web browser? The section below noted in red is very confusing (from the Microsoft message) -- who gets what features as both are mentioned in same paragraph? ---------------------------------- Microsoft 365 Copilot Chat – Updates to Copilot in Word, Excel, PowerPoint, and OneNote Starting April 15, 2026, Copilot will no longer be available in Word, Excel, PowerPoint, and OneNote for Copilot Chat users. To ensure a high-quality experience, we are reserving the full Copilot experience in these apps—with advanced reasoning and model choice—for users with a paid Microsoft 365 Copilot license. There are no other changes for users without a Microsoft 365 Copilot license. Copilot Chat still offers secure, AI web chat and the Word, Excel, and PowerPoint agents for chat-first content creation within the Microsoft 365 Copilot app. Additionally, users still get Copilot in Outlook with inbox and calendar grounding.
Cowork can't send emails?
Hi, all. I've been playing around with Copilot Cowork and really loving it, but with one problem. When it tries to send an email to anyone but myself, it can't. It tells me to approve, but I never get the approval prompt. I get errors like this: "Good question. The approval step typically appears as a confirmation dialog right here in our conversation before an email is sent. It worked fine for the test email to your own address, but when I tried sending to [otherperson], the system blocked it before the approval dialog could reach you" and "The platform is blocking the send to an external recipient and the approval dialog isn't surfacing properly." and "All three return the same error: the platform requires an approval step before executing any outbound send action, but that approval dialog isn't rendering in your session. The test email to yourself worked because self-sends appear to be auto-approved. This is a platform-level issue — not something I can fix from my side." Any thoughts? I'm not even sure where to start troubleshooting this.
Can my agent use flows as tools when I'm a licensed M365 Copilot user?
I tried to create an agent in Copilot Studio which drafts responses to emails I receive in Outlook. There is no "draft a reply" tool, there is only "Send a reply" or "Draft a message". I don't want an AI agent to immediately send out email replies, I want to review them first, but I also would like to review them in the context of the original message (as opposed to having a bunch of messages in the drafts folder with no visible connection to the original email I received - like the "Draft a message" tool does). So I "added a tool" (which would be a "Flow") to the agent which just does 2 HTTP calls to the outlook graph api (one creates the reply, the second adds the generated content to the body). The flow checker tells me: More Copilot Credits are needed for this flow to run. Runs from agents by M365 Copilot users and testing don't consume credits. I am a "M365 Copilot user", so I'd expect this to work, and manually testing the flow works. However, when the agent tries to run the flow, it's being blocked with the error: The environment 'Default-<...>' does not have sufficient Copilot Credits to run workflows. So, can an agent by a M365 Copilot user run flows? Alternatively: is there a way to draft email responses which in Outlook end up visually connected to the original message?
Suggestion: Allow users to customize the UI name of MS Copilot (with “Powered by Microsoft 365”)
Background Microsoft Copilot is an extremely capable assistant, but its current visual identity is completely fixed (the name “Copilot” is always shown), even though users interact with it daily as a personal or team assistant. From a user experience perspective, this creates a small but important gap between using a tool and working with an assistant. Proposal Allow users to customize the visible name of their Copilot assistant, while maintaining a clear and consistent Microsoft branding indicator, for example: Holiday (name that the user creates for calling Microsoft Copilot 365 IA) Powered by Microsoft 365 Copilot (Text that Microsoft uses to reflect that it's already Microsoft Copilot). This proposal does not aim to change the underlying model, security, governance, or responsibility. It only affects the identity/presentation layer of the assistant. Why this matters (UX & adoption) Allowing users to name their assistant creates: Psychological ownership (“my assistant” instead of “the assistant”) Higher trust and willingness to delegate complex tasks Stronger long-term adoption and recurring usage In daily work, users naturally refer to assistants by name (“Ask Friday to review this document”), which helps integrate Copilot into real workflows instead of keeping it as an external tool. Enterprise perspective In organizational environments, a named assistant feels like part of the team rather than a generic external service. This improves internal communication, clarity, and acceptance of AI-assisted workflows. Importantly, the “Powered by Microsoft 365 Copilot” label keeps: brand visibility transparency technical and legal responsibility clearly with Microsoft This follows well-established patterns such as “Powered by Azure” or “Powered by Microsoft Security”. Strategic fit Microsoft already enables named and branded assistants through Copilot Studio. Extending this concept to the core Copilot experience feels like a natural next step with: Low technical risk (presentation-level feature) High UX impact No compromise on governance or brand integrity Closing Naming the assistant transforms the relationship from using AI to collaborating with AI. This small change could have a disproportionally positive effect on trust, adoption, and everyday productivity. Thanks for considering this feedback.Copilot in Outlook Can Now Reschedule Conflicting Meetings Automatically | Microsoft 365 AI
📅 Microsoft Copilot just made Outlook meetings smarter. A new Copilot feature in Outlook can now automatically detect conflicting meetings and propose a reschedule — no more manual calendar juggling. Copilot analyzes: ✔ Your calendar ✔ Existing conflicts ✔ Availability of participants …and suggests the best new time, directly in Outlook. For busy professionals and teams, this is a big productivity win and another step toward truly AI‑assisted workdays. I’ve just published a short video showing how it works in practice 👇 https://youtu.be/xhTkvF8rCq8 Would you trust Copilot to manage your meetings? #MicrosoftCopilot #Outlook #Microsoft365 #AIProductivity #FutureOfWorkHow Copilot Automates Enterprise Workflows (Technical Breakdown)
In today’s enterprise landscape, automation is no longer just a competitive advantage it’s a necessity. However, traditional automation approaches like RPA (Robotic Process Automation) and custom scripting often require significant development effort, rigid rule definitions, and ongoing maintenance. Enter Microsoft Copilot a generative AI-powered assistant that transforms enterprise workflow automation by combining natural language processing, contextual understanding, and deep integration with business systems. This article goes beyond surface-level benefits and explores the technical architecture, real-world scenarios, and implementation strategies that make Copilot a powerful automation engine. https://dellenny.com/how-copilot-automates-enterprise-workflows-technical-breakdown/Cowork (Frontier) OneDrive/SharePoint document read errors
We've recently managed to start using the Cowork (Frontier) agent in M365 Copilot and some of the fantastic capabilities it provides. We're seeing an issue where right now the agent it failing to read data from withing documents such as Word documents in SharePoint and OneDrive. We see errors in the detail such as "ReadFileContent tool keeps failing with auth expired" and "Auth expired. Let me retry - the system should have refreshed the token.". Other agents appear to be able to access SharePoint/OneDrive content without error and people trying to access those documents definitely have full permissions (their own OneDrive as an example). Works when files are manually attached to the prompt. We've enabled model sub-processing which is the only dependency I can see for Cowork. Wondering if a widespread known issue or something specific to my environment?Running Copilot Retrieval Searches with the Microsoft Graph PowerShell SDK
The Copilot Retrieval API is a Microsoft Graph API that apps can use to search Microsoft 365 locations to find information to ground user prompts. Grounding means that the apps use the information found by Copilot to add context to the queries they submit to a generative AI engine for processing. Although I don’t have an immediate purpose for the API, it provides a nice insight into how grounding works. https://office365itpros.com/2026/04/14/copilot-retrieval-api/
AI-generated feedback summaries for managers - is this a thing yet?
Our managers are responsible for 10-15 direct reports each and the biggest complaint I keep hearing is that writing individual feedback for every person takes forever. Copilot can help draft emails and summarize meetings but I cant figure out how to get it to look at someone's goals progress, recent feedback, and 1:1 notes all together and suggest talking points or review comments. Is anyone using Copilot in any form to help managers write better, more data-backed feedback?
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
