Feedback: Multiple Reliability and Consistency Issues Encountered with Copilot
Hello everyone, While using Copilot, I have noticed a few recurring issues: Occasional hallucinations, where incorrect information is presented as factual. Inconsistent reasoning, with answers sometimes contradicting earlier responses. Limited fact-checking before making assertions. Loss of context in longer conversations. Significant variations in answer quality for similar questions. I would appreciate improvements in fact verification, context retention, reasoning consistency, and transparency when information cannot be confirmed. Has anyone else experienced similar issues? Thanks for your feedback.Minimal visual system & fast message management for Copilot.
Hello, I create concepts — conceptART. The conversation with a language model becomes much clearer when you introduce two geometric markers. A blue circle for the user and a green triangle for the model. I believe these visual markers would make sessions with the model more readable and easier to navigate. One thing that frustrates me is the lack of fast message management inside a session. I write densely, metaphorically, in mental images. I have a very active inner speech, and I don’t need to look at the text while writing. I create quickly, and every session produces something valuable—something mine—and I would like a way to quickly save both my messages and the model’s messages. My idea is simple: Each message, both from the model and from the user, could have a small white triangle next to it, and next to that triangle a number — 1, 2, 3, 4, 5, 6. In Copilot settings, the user could define folder paths corresponding to these numbers. Each number would map to a specific folder. The user could name these folders, for example: important, to reflect on, essence, ideas, big concepts. After clicking the triangle with number 1, the program would automatically create a text file named note1. For clarity, messages saved from the model could be named note1_model, and messages saved from the user note1_user. I believe this would give users speed and clarity, and would interrupt the logical flow of thought only minimally. Thank you, S
How does ERP MCP determine F&O environment?
How does the Dynamics 365 ERP MCP Server determine the target Finance & Operations environment when multiple environments (SIT, UAT, and Production) have MCP enabled? In Copilot Studio, the MCP connection only shows the authenticated user and does not expose any environment selection or environment identifier. Is the target F&O environment determined by the underlying Power Platform connection, the MCP client registration, a connection reference, or another routing mechanism? How can administrators verify which F&O environment an MCP-enabled agent is actually connected to?
Are there any plans to bundle E7 licenses for trainers, or add Copilot to E5?
I find myself increasingly being asked to deliver courses on Copilot, and the only way I get access to the Pro version is via the labs. However, this doesn't give me time to set up demos of Graph, crawling across data and building context etc. Does Microsoft have any plans to give us MCT's any access to Copilot, through our E5 subscriptions or otherwise? Or are we expected to pay for it?Issue with Copilot
Issue Report: Plotting Engine Fails to Generate Charts Summary The chart‑generation feature in Copilot intermittently fails to produce output. When requesting visualizations such as radar charts, bar charts, histograms, or other plotted graphics, Copilot often returns an empty result with no error message or explanation. Observed Behavior Requests for plotted charts sometimes return "" (empty output). No error message is provided, making troubleshooting impossible. The failure occurs even with simple, valid datasets and straightforward instructions. Conceptual or AI‑generated diagrams work consistently; only plotted charts fail. Expected Behavior Copilot should reliably generate charts when provided valid data and instructions, or provide a clear error message if the request cannot be completed. Impact This issue prevents users from visualizing structured datasets and reduces confidence in Copilot’s ability to produce quantitative graphics. It also forces users to retry multiple times or switch to non‑chart visualizations. Request Please investigate the stability of the chart‑generation environment, particularly around sandbox execution and rendering reliability. Adding explicit error messages when chart generation fails would also significantly improve usability.
Work IQ
Hi Team, We wanted to utilize Work IQ rest APIs to search documents across m365 ecosystem. we have observed that it fetches the document with better accuracy when the document is placed on sharepoint, but at the same time it finds it difficult to search the document from outlook. We do get the document if we specify the source as outlook in the text string passed to the API. Can you please let us know if there is any setting or option through which we can give equal importance to search a document across m365 ecosystem ( Outlook, Sharepoint, Team, Onedrive) API - https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/work-iq/rest/copilotconversation-chat?pivots=work-iq-rest-prod
Which Accessible Source Can Reliably Return Current Date, Time, Timezone and UTC Offset?
Question for Microsoft 365 Copilot experts I am trying to implement a reliable "Current Time Validation" control inside a Microsoft 365 Copilot workflow. The requirement is to obtain a machine-readable and repeatable timestamp containing: - Current date - Current time - Time zone identifier - UTC offset For example: 2026-09-16T18:09:00+08:00 Timezone: Asia/Shanghai UTC Offset: +08:00 My goal is not a human-readable world clock page, but a source that Microsoft 365 Copilot can actually access and consume reliably during execution. Business context: The timestamp is used as a mandatory validation gate before generating operational reports. If the timestamp is wrong, downstream conclusions may become invalid because greetings, operating-hours logic, OOO/PTO analysis, and action ownership are all time-dependent. Problems encountered so far I have already tested several approaches and found multiple reliability issues: 1. Conversation context is not a reliable clock source. Copilot may retain or reuse a timestamp from the beginning of a conversation rather than reflecting the actual current time. 2. External "current time" web pages are problematic. Some sites appear to return cached/indexed content when accessed through Copilot, producing timestamps that are clearly inconsistent with real-world elapsed time. 3. Human-readable sources are insufficient. I need a source that returns structured data which can be validated programmatically. 4. Timezone information alone is not enough. The solution must provide: - current date - current time - timezone identifier - UTC offset 5. The source must be repeatable. Two consecutive queries should return updated timestamps reflecting actual elapsed time. Questions 1. Among the data sources that Microsoft 365 Copilot can realistically access today, which source can provide: - date - time - timezone - UTC offset in a machine-readable format? 2. Is there any Microsoft-native source (Microsoft Graph, Outlook, Exchange Online, mailbox settings, tenant settings, calendar services, etc.) that exposes this information directly? 3. Which source would be considered the most reliable and repeatable for workflow-validation purposes? 4. Has anyone implemented a trusted "current time authority" pattern for Microsoft 365 Copilot or Copilot Studio agents? 5. Does Microsoft 365 Copilot have access to a real-time clock source that is guaranteed to be refreshed at query time rather than returning indexed or cached timestamp information? The objective is to establish a trusted and auditable timestamp before generating business reports, task summaries, or workflow decisions. Thanks in advance.Copilot chats listed, but no longer available.
After installing the latest Copilot (September 2026) some of my chats have become corrupted. In the Android phone app, the Windows 11 app and on copilot.microsoft.com they are listed, but impossible to open delete or rename. I get : "This chat is no longer available". I have several older and newer chats that work just fine. I think the ghosts was created the same day as the new version was installed on my phone. The automatic installation process did not work well. Had to uninstall and manually reinstall from Google Play. I have chatted with Microsoft Support about it, and they admit it may be a server-side problem. Is there anybody with a similar problem? Or maybe somone has a solution? That would be great!
Request to Reconsider Russian Speech Recognition Support in Windows and Copilot
I would like to provide feedback regarding the absence of Russian speech recognition support in modern Windows and Copilot experiences. Russian is not limited to a single country and should not be viewed exclusively through a geopolitical lens. It remains one of the most widely spoken languages in Europe and is used daily by tens of millions of people across numerous countries, including EU residents, immigrants, international businesses, and users throughout Eastern Europe, the Caucasus, Central Asia, and other regions. As a Windows 11 Enterprise user, I was surprised to discover that Russian speech recognition is no longer available as a Windows Speech language package. On my Windows 11 Enterprise 25H2 installation, the Language.Speech~~~ru-RU package is not available at all, while speech recognition packages continue to exist for many other languages. As a result, Russian-speaking users are unable to fully use Voice Typing and certain voice-driven Copilot experiences. This creates a significantly worse user experience compared to competing AI platforms such as ChatGPT and Google Gemini, both of which currently provide high-quality Russian speech recognition without requiring additional configuration. From a business, accessibility, and user experience perspective, limiting support for a language spoken by so many people is difficult to justify. Regardless of political considerations, Russian remains a major international language used by customers, professionals, students, and businesses across many countries and regions. The current situation may unintentionally encourage users to choose competing platforms that offer broader language accessibility and voice capabilities. I respectfully ask Microsoft to reconsider its current approach and evaluate restoring or expanding Russian speech recognition support in Windows, Voice Typing, and Copilot services. Language support should be guided primarily by user needs, accessibility, inclusiveness, and product competitiveness. Thank you for your consideration.
