Copilot Feedback - Power User Experience Improvements
As a frequent Copilot user for technical discussions, architecture, governance, Microsoft 365, Power Platform, and problem-solving activities, I would like more control over the user experience. Copilot has become a daily productivity tool, but several UI and usability improvements would significantly benefit advanced users. 1. Allow Disabling Suggested Follow-Up Prompts The suggested replies shown below every response may be useful for new users, but for experienced users they often add little value and consume screen space. Please provide an option to: Disable suggested prompts entirely Adjust their frequency or aggressiveness Enable them only for new conversations or learning scenarios 2. Make '/' and '@' Shortcuts Configurable The automatic triggering of slash commands and @ mentions while typing can be disruptive and may interrupt or replace text unexpectedly. Please allow users to: Disable these shortcuts Configure alternative trigger characters Require a keyboard shortcut before activating them 3. Add a Power User Mode Consider introducing a dedicated Power User Mode featuring: No suggested prompts Reduced UI clutter Compact layouts Fewer interruptions while typing Advanced customization options A productivity-focused experience 4. Compact Conversation View Long technical conversations can become difficult to navigate due to excessive spacing and scrolling. Please provide: A compact view option Reduced vertical whitespace More conversation content visible on screen 5. Conversation Search Many conversations contain valuable information that users want to revisit later. Please add the ability to: Search within a conversation Search code snippets and formulas Search by date or topic Quickly jump to matching results 6. Pin Important Messages Allow users to pin key answers, code snippets, formulas, decisions, or reference messages within a conversation so they can be easily found later. 7. Enhanced Copy Experience For technical users working with Power Apps, Power Automate, SQL, PowerShell, and other technologies: One-click copy for all code and formulas Preserve formatting during copy operations Support copying multiple related blocks together 8. User-Defined Response Profiles Allow users to create and switch between response styles such as: Technical Troubleshooting Power User Learning Mode Executive Summary Architecture Review This would reduce the need to repeatedly explain personal preferences. 9. Memory Transparency and Management Allow users to: View all stored memories and preferences Edit or delete individual memory items Temporarily disable specific memories Understand which memories are influencing responses This would improve transparency and trust. Summary Copilot is evolving from a simple chat tool into a professional productivity platform. Providing greater control over the interface, shortcuts, suggestions, memory, and conversation management would allow experienced users to tailor the experience to their workflow while preserving the current experience for those who prefer more guidance. Thank you for considering these improvements.
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?
[Japan region] Copilot Cowork not showing in the agents list despite all settings enabled
Hello, I'm based in Japan and my tenant region is Japan. I'm trying to enable the now-GA Copilot Cowork for my tenant, but Cowork does not appear in the agents list in the Microsoft 365 admin center, so I can't deploy it. Environment: Location / tenant region: Japan License: Microsoft 365 Copilot (assigned to target users and the admin account) All prerequisites appear to be in place and verified: Anthropic (AI provider acting as a Microsoft subprocessor): enabled Usage-based billing (Copilot Credits): enabled Discovery setting "AI experiences enabled by usage-based billing": set to allow users to discover and use Issue: Even with all of the above enabled, searching for "Cowork" under Integrated Apps → All agents returns no result. It also does not appear under Copilot → Settings → View all. As a result, I cannot deploy it to users, and Cowork does not show up for users at m365.cloud.microsoft either. Questions: Is there any additional setting required to make Cowork appear in the agents list? For a tenant in the Japan region, if there is a delay before the Cowork agent is provisioned after GA, what is the typical timeframe, and is there a way to check the rollout status for my tenant? Is there a specific admin role (e.g., AI Administrator) I should double-check on the account performing these steps? If anyone in the Japan region has resolved the same issue, I'd appreciate hearing how. Thank you.PowerShell: Export Microsoft 365 Copilot Agent Inventory and Availability Assignments
Hi everyone, I needed a way to export Microsoft 365 Copilot agent inventory and availability assignments from the Microsoft 365 Admin Center, but couldn't find a built-in export option. After investigating the admin portal's network traffic, I built a PowerShell script that uses the same internal API consumed by the Microsoft 365 Admin Center to export all Copilot agents to CSV. ### Features - Exports all Microsoft 365 Copilot agents - Automatically follows pagination (`nextLink`) - Exports: - Agent Name - App ID - Title ID - Publisher - Created By - Availability Settings - Allowed Users / Groups - Assignment Information - Deployment Information - Version Information - Timestamps - CSV output ### Tested The script has been tested against a tenant containing 482 Copilot agents and successfully exported the complete inventory. ### GitHub https://github.com/gwestergren/M365-Copilot-Agent-Inventory ### Notes - Uses an authenticated browser session cookie from the Microsoft 365 Admin Center. - Uses the same internal API currently consumed by the admin portal. - This is an undocumented API and Microsoft may change it at any time. Feedback, testing results, and improvements are welcome. Here are some screen shots: output to csv Successful run of the scriptCopilot Employee Self-Service Agent
I’m looking for some clarity regarding the rollout of the https://adoption.microsoft.com/en-us/ai-agents/employee-self-service-agent/ and whether others are seeing it in their environments yet. I’ve been following this closely and initially understood that a formal request was required to gain access. However, the Microsoft Learn documentation now provides specific, step-by-step instructions on how to enable and access it directly. Despite following those instructions to the letter, the agent is still not appearing within my tenant. I’ve verified my configurations against the guide, but the options simply aren't visible. A few questions for the community: Has anyone else successfully enabled the agent using the self-service steps in the documentation? Is there or was there ever a manual "request-for-access" process that overrides the published steps? I’d appreciate any insights or if anyone from the product team could clarify if the documentation is slightly ahead of the actual deployment.
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.
Cowork Custom Instructions Not Autoloading
When you tell Cowork "remember this for next time" or "always do X," Cowork suggests (or just goes ahead and makes) an update to copilot-instructions file. It tells you the preference has been saved and the file does get written. However, it doesn't automatically load the custom instructions file at the start of new sessions. You have to specifically mention it in a prompt. Once you do, it will load the and use the file to guide its responses for the remainder of the session. I feel like one of two things are happening here: 1. I'm missing something 2. The Cowork dev team missed implementing what I would consider a basic feature, even for a "Frontier" feature. Can anyone else confirm that this is the behavior they experience?
UX Improvement Proposal: Visual Indicator Showing Which Copilot Environment Is Active
I would like to propose a small but highly impactful UX improvement for Microsoft Copilot. Suggestion: Add a small icon, badge, or color indicator in each Copilot chat session to clearly show which Copilot environment is currently active (Copilot Web, Copilot Pro, Copilot for Microsoft 365, Copilot in Teams, Copilot Studio, Windows Copilot, etc.). Reason: Each Copilot environment has different capabilities, permissions, connectors, and tools. When users switch between environments—or when two people compare results from different Copilots—it becomes confusing to understand why certain features work in one place but not in another. Real example: At my university, a professor could not understand why Copilot “wasn’t doing something it had done before.” The issue was simply that he was using a different Copilot environment without realizing it. This is a common scenario for students, educators, and professionals. Benefit: A simple visual indicator would: Reduce confusion and support requests Improve clarity for non‑technical users Help users understand available capabilities at a glance Provide better context awareness across devices and platforms This is a small UI change with a big impact on usability and learning. Thank you for considering this improvement.Copilot Chat vsus. Microsoft 365 Copilot. What's the difference?
While their names sound similar at first glance, Microsoft 365 Copilot and Microsoft 365 Copilot Chat, they differ in several aspects. And more importantly: one is built on top of the other. What is Copilot Chat (Basic)? First things first. Microsoft 365 Copilot Chat is often simply called Copilot Chat. Copilot Chat (Basic) generates answers based on web content, while Microsoft 365 Copilot (Premium) is also grounded on users' data, like emails, meetings, files, and more. Since early 2025, Microsoft 365 Copilot Chat has been available to all users in organizations, becoming the entry point to AI assistance for many organizations. Copilot Chat (Basic) is the foundational Copilot experience available at no extra cost for everyone with an eligible Microsoft 365 plan, including: Microsoft 365 E3 / E5 Microsoft 365 A3 / A5 Microsoft 365 Business Standard & Business Premium Copilot Chat (Basic) is secured, compliant, and it does not required the full Copilot add-on license. Copilot Chat (Basic) is able to ground responses on: Public web content. Content explicitly shared or work data manually uploaded to the chat by the user. On-screen content or content displayed on-screen in apps like Outlook, Word, Excel, PowerPoint, and OneNote. When it comes to agents, Copilot Chat (Basic) offers these features: You can create your own declarative agents grounded on public web content with Agent Builder. You can use agents built by your org grounded on organizational data with the pay-as-you-go method. There are Microsoft prebuilt agents available like Prompt Coach, however Microsoft premium prebuilt agents like Researcher or Analyst are not included. The screenshot below shows how Copilot Chat looks and highlights its main capabilities. Note the Upgrade button, meaning this is not Microsoft 365 Copilot, but the Copilot Chat (Basic) experience. Note that EDP (Enterprise Data Protection) is available in Copilot Chat (Basic). What is Microsoft 365 Copilot (Premium)? Microsoft 365 Copilot (Premium) is a paid add-on license that builds on top of Copilot Chat and unlocks Copilot's full power. It is available for selected Microsoft 365 plans, including: Microsoft 365 E3 / E5 Microsoft 365 A3 / A5 Microsoft 365 Business Standard & Business Premium With a Microsoft 365 Copilot license, users get everything Copilot Chat (Basic) offers, plus much more: Data grounding: Microsoft 365 Copilot (Premium) includes Copilot Chat grounded on web and/or on user's Microsoft 365 data like emails, meetings, chats, and documents. Office apps: It integrates deeply into Microsoft 365 apps like Outlook, Teams, Word, Excel, and more. The integration includes features like Edit with Copilot allowing Copilot to adjust live your documents or email based on your prompts. Custom agents: It brings the capability to create your own declarative agents grounded in organizational data and/or web data. You can create agent either using Agent Builder or Copilot Studio. MS prebuilt agents: Premium prebuilt agents like Researcher and Analyst are included in Microsoft 365 Copilot (Premium). The screenshot below shows the Copilot chat experience for users who have a Microsoft 365 Copilot license. Note that EDP or Enterprise Data Protection also applies here How can I access Microsoft 365 Copilot Chat? Today, Copilot Chat is accessible via https://m365.cloud.microsoft or https://copilot.cloud.microsoft using your Entra ID (work or school account). One important difference in day-to-day experience: Users with a Microsoft 365 Copilot license typically see Copilot prominently surfaced across Microsoft 365 apps. Users with Copilot Chat only may not see it pinned by default on the Microsoft 365 home page. To improve discoverability, Microsoft 365 Copilot administrators can pin Copilot Chat via the Microsoft 365 admin center, ensuring that users can easily access it without friction. Especially convenient is that if you use the M365 Copilot Chat app on Windows, you can open Copilot using the keyboard shortcut Ctrl + C. What’s the difference? The differences between Copilot Chat and Microsoft 365 Copilot mainly come down to: Licensing Data grounding (web-only vs. personal work data) Integration depth within Microsoft 365 apps I’ve listed the key differences in the comparison below. 👇
Feature Request: Add Search Functionality in Copilot Chat History
Hi everyone, I’d like to suggest a feature for Microsoft Copilot that I believe would significantly improve usability and productivity: searching within chat history. Currently, users cannot search past conversations inside Copilot. This makes it difficult to retrieve previous answers, references, or technical instructions—especially in long or complex chats. Adding a search bar or keyword filter would allow users to quickly locate relevant messages without scrolling manually. This feature would be especially helpful for developers, IT professionals, and anyone using Copilot for technical troubleshooting or documentation. It would also reduce repeated questions and improve continuity across sessions. Please consider adding this capability in future updates. If others agree, feel free to upvote or share your use cases. Thanks!
