Copilot Studio Agent vs SharePoint subfolders
Hi community, We are exploring the Copilot Studio Agents and are running into some issues. When we add the root library of a SharePoint site the agent is able to search the documents within, however when using only a subfolder of the site as a knowledge source it can't find any documents. The agent response is: "I have searched the available knowledge base but could not find any instructions on "Subject XXX". I read it can take up to 24 hours to build the index for subfolders, however after 3 days of waiting the agent still can't find any documents. I've tried making a new agent directly adding the subfolder as a source. The permissions of the user configuring the agent are also correct and the user has full access to all the files. I've also tried working with subagents with no success either. Has someone else experienced the same and is it correct agents can't work properly yet with subfolders of SharePoint sites?
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.
"Draft with Copilot" in Sales Hub Email Activity
Hi everyone, could anyone help me out how to add "Draft with Copilot" option in Sales Hub Email. I have enabled the copilot features in the environment and also enabled Contextual email drafting with AI in the application settings. In my personal tenant account that is working fine, but not here. How do I get that Draft with Copilot option / Modern version of drafting emails?
Chat icon disappears in the M365 Copilot Chat
Hi, We are an Education tenant and have an issue where the "Chat" icon disappears from the left hand navigation in the M365 Copilot Chat app (or Web) after you click on e.g. "Search". The only way to get the Chat icon back is to restart the app or refresh the web page. This only happens to unlicensed users while users with a paid license don't have this issue. Version we are running is: bizchat.20251030.51.4 Anyone else experiencing this issue? ** Screenshots ** 1. When starting the M365 Copilot Chat app the "Chat" icon is present 2. Clicking the "Search" (or any other icon) then "Chat" disappears and will not come back until you restart the app. Same behavior in Web.
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 😉Adaptive Cards Input.Date shows mm/dd/yyyy on sample site but renders as “September 20, 2017”
Hi all, I’m using Adaptive Cards Input.Date in Microsoft Teams / Copilot Studio (Teams channel). I noticed the same card renders the date differently depending on host: On the Adaptive Cards Inputs sample page, the Due Date field shows mm/dd/yyyy (e.g., 09/20/2017). But when I copy the same JSON into Adaptive Card Designer (and similarly inside Teams), the date shows as a long format (e.g., September 20, 2017). Reference page (shows mm/dd/yyyy): https://adaptivecards-release-ci.azurewebsites.net/samples/Inputs.html I want the date displayed as mm/dd/yyyy in Teams (and ideally allow typing in that format), e.g. 12/20/2025. { "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "text": "Due Date" }, { "type": "Input.Date", "id": "DateVal", "value": "2017-09-20" } ] } Questions Is it possible to force the display format of Input.Date to mm/dd/yyyy via Adaptive Card schema/JSON? Or is the display format always controlled by the host (Teams) / locale and cannot be overridden? If it cannot be forced, what’s the recommended workaround in Teams? Example: use Input.Text with validation? or show helper text under the field? Environment: Adaptive Cards in Teams via Copilot Studio. AshishTyped 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.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!
