Hey Copilot Voice Function is not working
I am trying to use the "Hey, Copilot" feature in the Copilot app on my PC. It is not working because the voice assistant does not open when I say the wake phrase. I have already contacted technical support, and after going through all the troubleshooting steps, we were unable to find a solution. My microphone is working perfectly because if I launch the voice assistant manually, I can have a voice conversation without any issues. Microsoft Copilot version: 150.0.4078.96 (64-bit) Windows 11 installed "Hey, Copilot" is enabled Mic permissions are enabled Manual voice conversations work correctly Reinstalled Copilot and restarted the PC Issue: Saying "Hey, Copilot" does not activate voice mode.
Copilot pain points....
Guys… seriously… we need some improvements here. I’m not asking Copilot to solve quantum physics or decode alien transmissions. I’m asking a Microsoft program for help with a Microsoft program. You’d think that would be the one scenario where Copilot would shine, right? Like, “Ah yes, my home turf, allow me to demonstrate competence.” But no. I can’t even get Copilot to correctly explain how to do basic SharePoint tasks. BASIC. As in, “click the thing, then click the other thing.” Instead I get a TED Talk about SharePoint philosophy and a guided meditation on patience. And then there’s the folder comparison fiasco. I want Copilot to do something so simple it should practically be a reflex: Compare two folders on my hard drive and tell me if they’re identical. Copilot’s response? “Absolutely, I can do that!” Followed immediately by an ever‑expanding scavenger hunt of things I apparently need to do first. It’s like asking someone to hand you a screwdriver and they say, “Sure, but first you’ll need to assemble this IKEA shelving unit, install three dependencies, sacrifice a goat, and agree to a quest.” I’m glad to hear you’re merging all the copilots into one “super Copilot.” Great idea. Fantastic. But let’s be honest — I’m praying the one that survives is the personal Copilot, because Copilot 365… whew. That thing feels like it was built by a committee that communicates exclusively through interpretive dance. And don’t even get me started on the wrapper versions. Those are like Copilot wearing a Halloween costume of itself, but the costume is made of cardboard and disappointment. And by the way — I’m STILL waiting for Copilot to create an app or program that automatically files my Outlook emails into folders. This is not a moon landing. This is not a Mars rover. This is not a Nobel Prize category. This is a simple, everyday, normal-person task. Yet somehow Copilot treats it like I’ve asked it to build the next Windows release from scratch using only a spoon and positive thinking. Come on, guys. We love the vision. We love the potential. But the basics need to work before the magic tricks do.
Has Anyone Successfully Used the Fabric Data Agent Connector with Copilot Agent?
Hi everyone, I'm facing an issue with a published Copilot agent in the Microsoft 365 app channel. The agent is configured with the Fabric Data Agent connector along with documentation as knowledge sources. However, while the agent works as expected with the Power BI connector, it fails to return responses when using the Fabric Data Agent connector in the Microsoft 365 app I understand the Fabric Data Agent connector is still in preview, but I wanted to check: Has anyone successfully used the Fabric Data Agent connector with a Copilot agent in the Microsoft 365 Copilot app? Is this a current limitation of the Microsoft 365 app channel or the preview connector? Are there any known workarounds? Is there any estimated timeline for the Fabric Data Agent connector to reach General Availability (GA) and support the Microsoft 365 app channel I'd appreciate any insights or experiences from others who have tested this scenerio Thanks!
Does Microsoft 365 Copilot Agent Builder support OCR and image analysis for SharePoint?
Hello everyone, I am currently testing a Microsoft 365 Copilot Agent Builder agent that is grounded on SharePoint document libraries. During testing, I observed that the agent can successfully analyze and generate responses from text-based documents such as Word, Excel, PowerPoint, PDF, CSV, and TXT files. However, when folders contain image-based files (JPG/PNG), the agent sometimes reports incomplete analysis or is unable to extract information from those files. I would appreciate clarification on the following: Does Microsoft 365 Copilot Agent Builder officially support OCR (Optical Character Recognition) for JPG and PNG files stored in SharePoint? Can Agent Builder natively analyze image-based content, or is this capability only available through Copilot Studio with additional AI services? Are there any documented limitations regarding image processing compared to text-based document processing? Has anyone successfully implemented a SharePoint-grounded Agent Builder solution that can reliably analyze scanned images, photographs, or image-based documents? If OCR/image analysis is not currently supported, is there a recommended Microsoft solution or architecture for achieving this requirement?
The Windows App isn't viable at present
The Windows Copilot app is not viable for real work because it only stores three conversations. Edge Copilot and the mobile app preserve full history and sync across devices, which makes them usable for long‑term projects. The Windows app should match that behavior or be retired. The inconsistency breaks workflows for users doing multi‑month creative and strategic work.URGENT!!!! I NEED HELP WITH COPILOT ATT DESIGN TEAM!!!!!!!
I am reporting a serious and urgent issue with Microsoft Copilot. Over the past two weeks, I uploaded more than one thousand documents into a single Copilot conversation. These files were used for an ongoing, multi‑chapter historical and genealogical project. Without warning, the entire conversation disappeared from my chat history. Because Copilot ties uploaded files to the specific conversation thread where they were added, the disappearance of the thread has made every one of those files inaccessible. Nothing in the interface warned me that: conversations can be wiped or hidden without user action uploaded files do not persist outside the original thread losing a thread means losing access to all associated documents there is no recovery mechanism for deleted or missing conversations This resulted in the effective loss of two weeks of work and over a thousand uploaded documents. I need the design team to understand the severity of this issue. Users must have: A guaranteed way to preserve conversations that contain uploaded files A way to recover or restore deleted or missing threads A central location where all uploaded files can be accessed, regardless of thread Clear warnings that files are tied to a single conversation and will be lost if that thread disappears This is not a minor inconvenience — it is a critical data‑loss problem that affects trust, usability, and the viability of Copilot for long‑form or research‑heavy work. Please escalate this issue to the engineering and product teams. I need a way to recover my missing conversation or at least regain access to the files I uploaded. Thank you.
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.
