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.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.
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.
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.
