Typed input routing stops working after navigating back to Home topic via Action.Submit (Invoke)
We are building a Copilot Studio agent with this structure: Home topic (menu page with icons) FeatureTopicA / FeatureTopicB / FeatureTopicC / FeatureTopicD Routing based on typed text (e.g. “feature A”, “feature B”) using a topic with trigger “A message is received” Navigation between topics using Action.Submit buttons (Invoke), including a Home / Back icon Observed behavior On a fresh conversation: Typing keywords like feature A or feature B correctly routes to the expected topic. From any feature topic, clicking Home (Action.Submit → Go to Home topic): Home page loads correctly. After returning to Home, typing the same keywords: Routing does not happen The conversation remains on Home The “A message is received” router topic is not triggered Restarting the conversation makes typing work again — until Home is reached via button navigation. We already tried following Dedicated router topic with trigger “A message is received” and highest priority Clearing global/custom variables when returning to Home Forcing routing using global flags Ensuring Home topic has no message trigger and no phrases Using Invoke-only navigation topics Handling text via Recognizer.TriggeringMessage.Text, LastMessage.Text, etc. Core questions Is this expected behavior in Copilot Studio? After navigating to a topic via Action.Submit (Invoke), does that topic “own” subsequent typed messages? What is the recommended pattern if users must be able to: Navigate via Home / Back buttons Then type free-text on the Home page Have typed text routed reliably every time Is the intended design: Home topic acts as the router itself? Or only one global message-received router should exist? Or typed input should not be expected to work reliably after Invoke navigation? We want to allow users to: Use menu buttons for navigation Return to Home Still type free-text commands Have routing work consistently without restarting the conversation Any official guidance, known limitations, or best-practice patterns would be greatly appreciated.Copilot Agent ALM and Knowledge Source Management Across Environments
Hello everyone, I currently have an agent in a Dev environment and want to deploy it to a second environment (e.g., Test or Prod). During deployment, we need to change the references to the knowledge sources. I’ve seen some articles where environment variables are used within Conversational Boosting topics to handle this, but I wanted to check if there is a supported or recommended way to manage or update knowledge source references from the Knowledge section itself to make them dynamic by using Environment variable? Any guidance or best practices would help. Thankyou.Microsoft 365 Copilot access to planner tasks?
I try to get Microsoft 365 Copilit access to existing planner plans and it's tasks. Read and possibly write access. How would I do that? I only have basic plans that are used in our team. Do I have to convert them (if that is possible at all) to the plans with project manager? I tried Project Manager. That seems to be an enhanced plan. Can I migrate? Does it need additional licenses? Dan
Copilot Chat missing in Outlook Web and Outlook Classic
Hello, since recently we are experiencing a tenant wide issue with Microsoft Copilot Chat in Outlook. Environment: Microsoft 365 Business Premium Microsoft 365 Copilot Chat enabled Copilot Chat is pinned for all users via admin settings Copilot Chat works in other Microsoft 365 apps (e.g. Word) Copilot Chat is missing in Outlook Web (OWA) and Outlook Classic for all users in the tenant Key details: No recent admin, policy, or licensing changes were made Copilot Chat does not appear in OWA, which suggests a backend or service side issue The behavior is consistent for all users Questions: Is anyone else seeing Microsoft 365 Copilot Chat disappear from Outlook Web or Outlook Classic tenant wide? Has Microsoft changed the availability or scope of Copilot Chat in Outlook recently? Are there known dependencies or rollout changes that affect Copilot Chat visibility in Outlook specifically? Any confirmation from other tenants or additional technical insight would be helpful.
Copilot account banned without explanation – no response to appeals
Hello, My Copilot account was banned around March 2025, without any warning or explanation. I have submitted multiple appeals via the official https://copilot.microsoft.com site, but have not received any confirmation or reply. I also contacted Microsoft Support several times via live chat, but was repeatedly redirected to unrelated channels like the Privacy Portal and Community Forums. Eventually, a supervisor informed me that only the Online Safety Team can handle Copilot bans. I was advised to send a follow-up email to their support address, referencing my case numbers. Despite doing so and being a paying subscriber who relies on Copilot for professional work, I have received no clear response or resolution. If anyone has dealt with a similar situation or knows how to get through to the proper team, any help would be appreciated. Thank you!
M365 Copilot Chat Works for Cloud-Only Students, Not for AD-Synced Accounts
I want to make M365 Copilot Chat accessible for our students (13+), and according to this article, I have prepared everything: My tenant is correctly classified as K12. The student account has the attribute ageGroup set to NotAdult in Entra ID. Unfortunately, this only works with student accounts that are cloud-only. When I synchronize a student from the on-premises AD to Entra ID and set the ageGroup attribute to NotAdult in Entra ID, access to Copilot Chat does not work. Any ideas?How to enable/access Copilot Chat in Outlook for Mac (Version 16.106)
Hi Microsoft Support, I am looking for assistance on how to enable or access the Copilot Chat feature within the Outlook for Mac sidebar. Importantly, I can confirm that Copilot Chat is fully functional and visible when I use Outlook on the Web (OWA). This indicates that my license is active and correctly assigned, but the feature is missing from my desktop client. My Environment Details: Outlook Version: 16.106 (Build 25122912) Update Channel: [Beta Channel / Insider] Interface: "The New Outlook" for Mac License: Microsoft 365 [Business/Enterprise] with Copilot Problem Description: The Copilot Chat icon does not appear in the left-hand navigation bar in the desktop app. When I check the "More Apps" section to customize the sidebar, Copilot is not listed as an option to add. I would appreciate your help with the following: Since the feature works in the web version, why is it not syncing/appearing in the Mac Desktop app (Version 16.106)? Are there any specific "Connected Experiences" or local settings I need to toggle to force the Copilot app to appear in the sidebar? Is there a way to reset the local app configuration or cache to recognize my Copilot entitlement? Thank you for your assistance in getting the desktop integration working.Painful behavior of "slash" ("/") in chat prompts
I know about the /commands (/reset, /help, ...) in Copilot powered applications where hitting "/" triggers auto-completion suggestions. Here we are talking about Copilot chat (Teams or Web app for instance) Each time you hit the "/" key, it pops up a menu inviting you to upload files, preventing you from going on typing until you hit the <esc> key. That's too disruptive. That would be ok if the upload menu what acting like a suggestion -- You may select with arrow keys if you wish, or just go on typing if you just need a "/" in your prompts. Please consider disabling this "feature" or I at least enhancing it so the upload menu is not modal and gets dismissed when you go on typing. Comments positive or negative are welcome, thumbs up too 😉Add a "Print Conversation" Feature in Microsoft Copilot
I'm warming up to using Copilot for quick answers and support. It is even better, more detailed and more honest about Microsoft shortcomings than Microsofts forum and support staff. But one thing that’s noticeably missing in Copilot is a simple way to print or export parts of a conversation. Many apps and websites offer a “Print” button for selected sections, allowing users to easily create a PDF or paper copy of important content. In Copilot, this would be especially useful for saving guidance, troubleshooting steps, or creative content in a clean format immediately. Currently, the only way is to manually copy text and paste it into another app, which feels like unnecessary extra work. A built-in “Print” or “Export to PDF” option would greatly improve usability and workflow efficiency. (This feedback was formulated with help from Copilot. I amended some sentiments of Copilotbeing too full of it self. Still it is much nicer than I would have written it! ;) Thank Copilot for that!
📌 Enhancing Arabic Language Support and Multilingual Intent Accuracy in Microsoft 365 Copilot
Hello Microsoft 365 Copilot Team, I would like to submit a formal proposal requesting an enhancement to the Arabic language experience and the multilingual intent-handling capabilities within Microsoft 365 Copilot. This proposal is based on practical observations across real usage scenarios in environments where users actively switch between Arabic and English for daily productivity tasks. 1. Background and Context Microsoft 365 Copilot has demonstrated exceptional performance in English-language workflows. However, in regions such as the Middle East—where a significant portion of users operate in bilingual environments—there remain notable gaps in language interpretation, UI localization, and multilingual intent retention. Enhancing Arabic language capabilities would meaningfully improve accessibility and align Copilot with the linguistic diversity of Microsoft’s global user base. 2. Observed Challenges in Current Behavior While Copilot excels in English, several recurring issues appear when interacting in Arabic or mixed Arabic–English contexts, including: Limited accuracy in understanding complex Arabic phrasing Reduced reliability when maintaining intent after switching languages within a single prompt Lower naturalness and structure in Arabic text generation when compared to English output Restricted availability of Arabic UI options for Copilot-specific interfaces Occasional misinterpretation of instructions containing blended terminology (Arabic user phrasing + English technical terms) These challenges collectively impact productivity and consistency for users who depend on Arabic as a primary working language. 3. Proposed Enhancements To ensure a more inclusive and reliable multilingual experience, the following improvements are recommended: 3.1 Full Arabic UI Support Across Copilot Surfaces Enable comprehensive Arabic interface options in all Copilot experiences, including Word, Excel, Outlook, Teams, and online applications. 3.2 Improved Arabic Natural Language Processing Enhance Copilot’s ability to understand and process Arabic grammar structures, context, dialectal variations, and hybrid Arabic–English prompts. 3.3 High‑Quality Arabic Text Generation Ensure outputs are clear, natural, and aligned with the stylistic expectations of native Arabic-speaking users. 3.4 Intelligent Multilingual Context Preservation Implement mechanisms that allow Copilot to maintain accurate intent when users transition between languages within the same instruction. 3.5 User‑Controlled Language Preference Settings Provide configurable options enabling users to define preferred input and output languages on a per-application or global basis. 4. Anticipated Benefits Implementing these enhancements is expected to: Improve overall accessibility for Arabic-speaking users Strengthen productivity across bilingual workflows Expand the suitability of Copilot for enterprise and governmental organizations operating in Arabic-speaking regions Increase adoption and satisfaction within a key growth market Align Copilot’s capabilities with diverse global language expectations These improvements would strongly support Microsoft’s broader mission of delivering inclusive, globally relevant AI-driven experiences. 5. Closing Statement Thank you for taking the time to review this proposal. Advancing Arabic language support and strengthening multilingual intent handling would provide significant value to a large and growing segment of Microsoft 365 users. I appreciate your continued commitment to improving the Copilot experience for users worldwide.
