Custom Agent Builder agent suddenly failing with "Oops, something happened" - no config changes
Hi All, We built a custom agent in Agent Builder (Microsoft 365 Copilot) that generates a Word risk assessment by grounding on a contract (either the document currently open via the Word Copilot add-in, or a file uploaded in the web browser chat), plus a fixed set of knowledge sources (guidance notes, playbooks). It worked reliably for about 5 days while I was testing it solo. We then rolled it out to appr. 20 users, and shortly after, it started failing consistently with a generic "Oops, something happened, try again" error, typically after a long delay, in both the Word add-in and the browser version. I can't confirm causation, but the timing lines up closely with when we expanded from single-user testing to ~20 concurrent users. I don't know whether this points to a tenant-level capacity/concurrency limit being hit, or its something else, just stating it in case others have seen a similar threshold effect. Is this a known concurrency/capacity limit for Agent Builder agents once usage scales up, or a separate backend regression affecting document grounding, and has anyone else seen this pattern after moving from single-user testing to broader rollout?
Need live support to get rid of Copilot and resolve billing
How do I contact a live support agent to get rid of Copilot and address billing issues? I need a passkey but cannot get one or contact a live support agent any other way the system has been running me around in circles. When I call the support number I need a passkey. But I cannot get a passkey under my admin support options. I subscribed directly through Microsoft and am the admin and sole user. I urgently need to get rid of Copilot from Word so I can use a specialized AI software for my business. It is designed to work in Word but has known conflicts with Copilot. The new software suggests change to my documents but cannot implement them because of Copilot. This interference is a known issue. Buying a second Business Standard subscription without Copilot and switching to that has not resolved the problem. I have tried logging out and in again, and clearing my cache. I am using the desktop version of Word. Billing and subscriptions are also an issue. My Business Standard plus Copilot subscription says "expired" and the three dots by the product don't give me any option to cancel or manage the subscription. But I also got a notice on June 18 that the annual subscription had been renewed, and that it will renew again in one year. I have not paid the most recent invoice. I don't want to test whether I would get more options by paying, since I don't want the copilot subscription and it is marked expired. I would appreciate any help on (1) disabling Copilot without disabling other connectors and (2) contacting a live person to address billing issues.
Feature Proposal: OS-level Intelligent Task Organizer (Windows + Copilot)
A Idea about Intelligent Tasks organizer, I have to remember a lot of things during the team meetings like what is been said (we'll schedule a call or follow up etc.,) and what has been communicated in the emails (I'll get back to you after 2 weeks, or call us after two weeks) , And notes that I took in the notepad, or notepad ++,or sticky notes, or word, or one note. I want to chronologically display tasks on the right hand side of the laptop screen just like sticky note and it shall display all tasks one by one, it shall remove tasks are already complete (email sent with confirmation). and arrange, adjust every few mins according to priority/time or user added priority. App shall display small icon (just like chat) upon clicking it shall display ordered list of tasks. and desktop apps like teams/note/word/notepad++,sticky notes can participate by default or other apps like notepad++ can be onboarded manually in to the app. You can use a local model which infers the meaning of “I’ll call you in two weeks” - who is “I”? you or them? “Let’s follow up later” - task or casual statement? “I sent it” - which task did this complete? You can use a local model such that Corporate Teams/Outlook access may allow by corporate policy. Need to put much emphasis on false positives if the app keeps inventing tasks. Do not need to bring big LLMs in to the picture for inference, because of corporate policies may not allow. Microsoft provides operating system,office 365, tools with copilot, the inference can be possible because of all apps/content can be accessible at os level. Problem: Users capture tasks across multiple tools: Teams meetings and chats Outlook emails Notes (OneNote, Notepad, Sticky Notes, Word) Tasks become fragmented, untracked, and often lost. Proposed Solution: A lightweight system-level task layer integrated with Windows + Copilot that: Core Features Automatic task extraction From Teams, Outlook, notes, and user text Example interpretations: “I’ll call you in 2 weeks” “Let’s follow up later” Context-aware inference (local model) Identify: Task owner (“I” vs “you”) Priority signals Deadlines Minimize false positives Chronological task timeline Tasks auto-organized by: Time Priority Recency Floating task panel (desktop UI) Docked widget (like Sticky Notes or chat bubble) Expand/collapse view Always visible option Automatic task lifecycle tracking Detect completion: “Email sent” “File shared” Remove or mark complete automatically Continuous re-prioritization Adjust every few minutes based on: New inputs Deadlines User behavior Privacy-first architecture Use local models (SLM) instead of large cloud LLMs Enterprise admin control for data access Why this matters: Millions of users manually track tasks across fragmented tools, losing productivity daily. This feature would unify task understanding across the OS and M365 ecosystem.What’s New in Microsoft 365 Copilot | May 2026
Welcome to the May 2026 edition of What's New in Microsoft 365 Copilot! Every month, we highlight new features and enhancements to keep Microsoft 365 admins up to date with Copilot features that help your users be more productive and efficient in the apps they use every day.
Architectural: 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.Is the Copilot model picker available in Word for the Microsoft 365 Premium (Individual) plan?
Hello, I would like to confirm whether the Copilot model picker is available in Microsoft Word for subscribers of the Microsoft 365 Premium Individual plan. Specifically, I am referring to the feature that allows users to switch between different AI models, such as: - Claude Opus 4.7 - GPT-5.5Copilot from a User's Perspective #2 — Types of Copilot and How to Choose
I'm a native Chinese speaker, and my English isn't strong enough to write an entire article from scratch. So I had Copilot Tasks translate this piece for me. If you find it reads smoothly — well, that's a testament to what Tasks can do. This is the second article in my Copilot from a User's Perspective series, focusing on the different types of Copilot. After reading the first article, if Copilot caught your interest, you're probably wondering: with so many Copilots everywhere, what's the difference between them? Are they actually useful? Are they really worth your time? By the end of this article, you should have a much clearer picture of how to think about the different Copilot experiences. There are a LOT of Copilot variants out there. I first started using Copilot on March 6th, and since then I've tried virtually every Copilot experience available to me (I'm a Microsoft 365 Premium subscriber). As of May 1st, my conversations have exceeded 9 million Chinese characters（including both my inputs and AI responses across all Copilot surfaces）. So I'll take the liberty of offering my own user-perspective classification of the current Copilot landscape. I believe the AI tools we regularly interact with can be broadly divided into four categories: Chat AI, Tool AI, Search Engine AI, and Agent AI. In my view, AI's core value lies in working alongside humans to boost productivity — and that's the lens through which I built this classification. One important caveat: due to account permissions and the nature of my work, I haven't had the chance to try the Windows system sidebar Copilot, GitHub Copilot, or Copilot Studio. Quick Analogies Before diving in, here's how I think about each type: • Chat AI — A knowledgeable, quick-thinking colleague who's a bit too talkative and not great at actually doing things. Great for brainstorming, but the moment hands-on work is needed, they vanish. • Tool AI — The notebook, sketchpad, and toolbox sitting on your desk. Specialized for specific tasks, with minimal conversation ability. • Search Engine AI — A filing cabinet that organizes your scattered documents so you can find things faster. • Agent AI — The most powerful and practical of all. A knowledgeable, sharp-thinking assistant who doesn't ramble and can actually get things done for you. Chat AI Where you'll find it: Web-based Copilot (copilot.microsoft.com), Edge sidebar Copilot, and the chat panels within M365 apps. What it does: This is the most popular, most accessible, and lowest-barrier type of AI. Chat AI typically can't take action on its own — the most it can do is generate images for you (though M365 Copilot Chat can also create files in Microsoft formats like Word documents and PowerPoint presentations). But don't underestimate it. You can ask it to check the weather, or have it research topics across the web — for example: "What are the most popular conversational AI tools on the market right now, and how are they reviewed?" My take: I've settled on the web-based Copilot as my primary chat AI. In my experience, M365 Copilot feels narrower in its reasoning — its responses are more conservative and contained, while the web version is more open and expansive. You can clearly sense they come from different design philosophies. One notable thing about M365 Copilot is that it integrates your conversation history across all M365 tools, suggesting that all the chat experiences within M365 share the same underlying foundation. Tool AI Where you'll find it: Copilot embedded in Excel, PowerPoint, Word, and other M365 applications. What it does: This type of AI is far more powerful than you'd expect. How much value you get from it depends entirely on how well you understand the underlying tools and how creatively you use the AI within them. With Copilot's help, my Excel productivity has improved by at least 70%. I'll dedicate an upcoming article specifically to using Copilot in Excel. My take: Incredibly powerful and massively underestimated. Stay tuned — I'll be showing you how to use these in future articles. Search Engine AI Where you'll find it: Copilot integrated into Edge's search experience (Bing AI). What it does: Its primary function is summarizing your search results. You might not even notice it's there, because it doesn't present itself as a conversation — it simply provides a summary alongside your results. You think you haven't given it any instructions, but the moment you type something into the search bar and hit Enter, it's already at work. There's not much to choose here — search engine AI is tied directly to your browser. Nobody switches browsers just for an AI summary feature, and the quality of its output depends entirely on what it finds. If the search results are noisy, the summary will be noisy too. So don't overthink this one — and certainly don't abandon a browser you're comfortable with just because a competitor added this feature. My take: The good news is that search engine AI is usually free — it's essentially a feature enhancement that search engines build into their browsers. That said, some AI-native search engines like Perplexity offer a noticeably better experience. Overall, this is a category where we can sit back, let the companies compete, and enjoy the improvements. Agent AI Where you'll find it: Copilot Tasks (on web-based Copilot) and Office Agents (in M365 Copilot). What it does: This type of AI goes far beyond a chat window. It connects to your email, calendar, browser, cloud storage, and other tools. Think of it as an AI that doesn't just talk with you — it takes action. Tell it "Check my meeting schedule for tomorrow and send a reminder email to my colleagues," and it will open your calendar, draft the email, and send it — instead of handing you a block of text and leaving you to do the work yourself. Tasks can even run in the background. Close the page and go about your day — it will notify you when it's done. For example, I've set up Copilot Tasks to automatically compile and send a daily report (with content I define) and to gather competitive analysis based on my requirements. That said, today's agent AI is more like an intern you need to keep an eye on than a seasoned employee you can fully trust. But even so, it's a massive leap forward from chat AI — at least it's willing to roll up its sleeves. My take: Choosing an agent AI is much more complex than choosing a chat AI, because an agent's core value isn't about how well it talks — it's about what it can connect to and what it can do. Agent AI is the category most worth learning about right now. Tool AI excels at specific points; agent AI covers the entire surface (though in certain vertical domains, tool AI may still deliver a better experience). It's the only category that's genuinely changing how humans and AI work together. This category is still young, and the experience isn't fully polished yet. When choosing, don't focus on which one feels the most mature — focus on which one fits your workflow. Even if someone told me Google's AI experience is the best, I still wouldn't abandon my Microsoft ecosystem. Closing Thoughts These are the four types of AI tools as I see them from a user's perspective. Chat AI is the quickest to try. Tool AI gives you the most tangible sense of how AI is changing the way we work. But if you're willing to invest time in learning and adapting, agent AI can deliver productivity gains that the other three categories simply can't match. I'll also be publishing a Tasks guide in the future (assuming you have access to it). Trust me — you'll be amazed at what Tasks can do. Next up: AI Tutorial — Surpass 90% of Excel Users in 5 Minutes
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
