Recent Discussions
File Share Connector users not mapping
Hi everyone, In need of some help here. I've setup an on-prem file share connector following this guide: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/fileshare-connector I can see the indexed items in my test folder, but, we can't crawl that data because the users are not mapping for some reason. I've been testing using the NTFS file permissions option. Has anyone had any success with using this option to sync/map users to the connector? If so, what were the requirements? The users are AD to entra id connect synced and the group I created is also AD to entra id connect synced as well. I applied ntfs perms to the test folder directly using the synced identity and tried using the group and the full crawl still does not populate users. I am not using nested groups neither. I also tried removing built-in groups such as administrators, authenticated users, etc. I've had a ticket open for weeks with Microsoft now with no answers.
Copilot in Word can't read chat attachments; Word for web file picker shows “no token obtained”
Summary of the issue I am seeing a persistent failure with Copilot attachments specifically inside Microsoft Word. Copilot in Word desktop and Word for the web can recognize an uploaded chat attachment by filename or OneDrive URL, but it cannot read the file contents. It reports the uploaded file as empty, corrupted, or in a format it cannot process. The same files are successfully read by standalone Microsoft 365 Copilot Chat using the same Microsoft account, and file uploads also work in Excel Copilot and PowerPoint Copilot. Failure started 10 days ago, with no obvious changes in settings on my end. The most useful diagnostic clue so far is that Word for the web’s Copilot attachment/file-picker path has also failed before any file was selected, showing “Something went wrong, please try again or refresh the page, no token obtained.” In Chrome, Word for the web produced a SharePoint-style error page with a correlation ID. This makes the issue look less like a bad file or local Word installation problem and more like a Word Copilot attachment-picker, OneDrive/SharePoint authorization-token, or file-handoff problem. Environment and scope Windows 11, Pro. Microsoft Word desktop: issue reproduced after updating Office and Windows. Word for the web: issue reproduced in Edge, Edge InPrivate, and Chrome. Standalone Microsoft 365 Copilot Chat / copilot.microsoft.com / m365.cloud.microsoft/chat: uploaded files can be read successfully with the same Microsoft account. Excel Copilot and PowerPoint Copilot: uploaded files work. OneDrive in Chrome: upload/download and file access work normally with the same account. Same Microsoft account used throughout. File types tested include tiny TXT files, PDFs, and DOCX files, including a complex DOCX. Copilot in Word can read the active Word document normally; the failure is limited to files uploaded as Copilot chat attachments inside Word. Observed behavior In Word desktop, Copilot chat accepts or recognizes the attachment metadata, including filename and sometimes a OneDrive URL, but when asked to read or summarize the file it says the file appears to be empty, corrupted, or in a format it cannot process. This happens even with a very small TXT test file. In Word for the web, the same general failure occurs. In one clean test, I created a brand-new blank Word document in Word for the web, opened Copilot, attached a tiny TXT file, and asked what the uploaded TXT file said. Copilot responded: “The uploaded file ingestion_test_731_1915.txt appears to be empty, corrupted, or in a format I can’t process, so I can’t read any text from it.” In another Word for the web test, clicking Copilot’s “+” attachment button and choosing either “My Files” or “Recent” opened a mostly blank window saying: “Something went wrong, please try again or refresh the page, no token obtained.” This occurred before any file was selected. In Chrome, Word for the web produced this error when trying to use the Copilot attachment flow: “Sorry, something went wrong. An unexpected error has occurred. Technical Details: Troubleshoot issues with Microsoft SharePoint Foundation.” The error included Correlation ID 64062ea2-3083-8000-a0f7-fbf4f6bb617d and Date/Time 8/4/2026 12:21:38 PM. Evidence matrix Test Result Standalone Microsoft 365 Copilot Chat / copilot.microsoft.com DOCX, PDF, and TXT uploads can be read successfully with the same account. OneDrive in Chrome Upload, download, and file access work normally. Excel Copilot Uploaded files work. PowerPoint Copilot Uploaded files work. Word desktop Copilot Attachments are recognized but reported as empty, corrupted, or unprocessable. Word for the web in Edge/InPrivate Tiny TXT attachment reported as empty, corrupted, or unprocessable. Word for the web attachment picker “No token obtained” message before file selection. Word for the web in Chrome SharePoint Foundation-style error with correlation ID 64062ea2-3083-8000-a0f7-fbf4f6bb617d. Word Copilot reading the active document Works normally. Troubleshooting already tried Updated Microsoft Office / Microsoft 365 desktop apps. Updated Windows. Restarted Word multiple times. Restarted the computer multiple times. Signed out and signed back in. Confirmed that the same Microsoft account is being used; there is only one Microsoft account involved. Toggled connected experiences off and back on, including restarts between changes. Started Word in Safe Mode. In Safe Mode, Copilot chat opened but did not activate properly; the Copilot pane appeared to cycle in the background and sub-windows were blank/unusable. Tested with a brand-new blank Word document in Word for the web. Tested in Edge, Edge InPrivate, and Chrome. Tested with very small TXT files as well as PDF and DOCX files. Confirmed OneDrive itself works normally in Chrome by uploading and accessing files successfully. Confirmed standalone Copilot and Excel/PowerPoint Copilot can process uploaded files successfully. Why this does not look like a local file or browser problem The same uploaded files work in standalone Microsoft 365 Copilot Chat, and OneDrive upload/download works normally. The issue also reproduces across Word desktop and Word for the web, across multiple browsers, and with a brand-new blank Word document. Because Word Copilot can read the active document but cannot acquire or process uploaded chat attachments, the failure appears isolated to the Word-integrated Copilot attachment picker, authorization-token acquisition, or OneDrive/SharePoint file-handoff path. Most likely failure area My current working theory is that Word-integrated Copilot is failing to obtain or pass the required SharePoint/OneDrive authorization token for Copilot chat attachments. The “no token obtained” message and the SharePoint Foundation correlation ID point toward the file-picker or backend handoff path rather than file contents. It may be account-specific, feature-flight/routing-specific, or a Microsoft-side regression affecting Word Copilot attachment handling. Request for help Has anyone seen Word Copilot attachments fail in this way while standalone Copilot, OneDrive, Excel Copilot, and PowerPoint Copilot all still work? Are there known Word Copilot attachment-picker, OneDrive/SharePoint token, or feature-routing issues that can affect only Word-integrated Copilot? If Microsoft support or engineering can trace backend logs, the most relevant correlation ID I have is 64062ea2-3083-8000-a0f7-fbf4f6bb617d from 8/4/2026 at 12:21:38 PM in Word for the web in Chrome. I would especially appreciate suggestions for anything beyond the standard local troubleshooting already tried. At this point, the pattern suggests the next useful step is probably backend investigation of the Word Copilot attachment/file-picker authorization flow rather than more file-format testing or local repair.
Co-Pilot in Outlook
Hello Microsoft Support, I have an active Microsoft 365 subscription with Copilot. Copilot is working successfully in Word and PowerPoint on my Mac using the same Microsoft account. However, in Outlook for Mac (version 16.110.2), Copilot displays the message: "Copilot is not supported for the account <email address>" My BTInternet email account is configured in Outlook as an IMAP account. This is also the email address associated with the Microsoft account I use to sign in to Microsoft 365. I have verified that Word and Outlook show the same signed-in Microsoft account. I reviewed Microsoft documentation indicating that Copilot access in Outlook can be be shared across connected email accounts, including certain third-party providers, when using an eligible Copilot subscription. Because of this, I would like clarification on why Copilot is unavailable for my BTInternet account and whether there is a configuration, licensing, or provisioning issue affecting my account. Could you please investigate and advise on the steps required to enable Copilot in Outlook for this account? Thank you for your assistance. Kind regards, Steve Bowen
Problem that copilot is unable to see all my emails in outlook
Copilot returns incomplete http://outlook.com/ email search results while Outlook Desktop and Outlook Web return complete results Product Microsoft Copilot (Windows App) Microsoft Copilot (Web) http://outlook.com/ Outlook Desktop Outlook on the Web Issue Summary Copilot is returning incomplete email search results from my http://outlook.com/ mailbox. The same mailbox searched directly in Outlook Desktop and Outlook on the Web returns complete and accurate results, but Copilot only returns a subset of the matching emails. The issue occurs in both the Copilot Windows application and Copilot on the web, suggesting the problem is not device-specific. Environment Microsoft Account Personal Microsoft account http://outlook.com/ mailbox Microsoft 365 Personal trial currently active Devices Windows laptop Completely rebuilt from scratch to troubleshoot this issue Internal storage wiped Fresh Windows installation performed All current Windows updates installed All current Microsoft 365 / Office updates installed Applications Tested Outlook Desktop (latest version) Outlook on the Web Microsoft Copilot for Windows Microsoft Copilot on the Web Account Status Same Microsoft account used for Outlook and Copilot Mailbox accessible and functioning normally Mail synchronization appears healthy Outlook search functioning correctly Problem Description On Monday 3 August 2026, my Inbox contained 12 messages. Examples included: Tesco http://amazon.co.uk/ eBay Yahoo Microsoft Account Team Microsoft 365 When I asked Copilot to list emails received on 3 August 2026, Copilot returned only a subset of those emails. Copilot was able to locate: Tesco order confirmation Tesco order amendment Microsoft 365 trial activation Microsoft account password change However, Copilot did not return several emails that were visibly present in the Inbox, including Amazon, eBay, Yahoo and other Microsoft account notifications. Expected Result Copilot should return all emails matching the requested date range, consistent with Outlook Desktop Search and Outlook Web Search. Actual Result Copilot returns only a partial subset of the matching emails despite the emails being clearly present in the mailbox. Diagnostic Testing Performed Outlook Desktop Search Result: ✅ Returns all expected emails. Outlook Web Search Result: ✅ Returns all expected emails. Copilot for Windows Result: ❌ Returns only a subset of emails. Copilot Web Result: ❌ Returns the same subset of emails. Operating System Result: ✅ Fresh Windows installation completed. Office Installation Result: ✅ Fully updated. Mailbox Access Result: ✅ Mailbox functioning normally. Why I Believe This Is a Copilot Search Service Issue The issue reproduces: Across multiple Copilot clients On a freshly rebuilt device While Outlook Desktop Search works correctly While Outlook Web Search works correctly Since both Outlook clients return complete results and both Copilot clients return incomplete results, the evidence suggests a discrepancy in the mailbox search/indexing layer used by Copilot rather than a problem with Windows, Office, Outlook indexing, or the local device. Request Please investigate: Whether Copilot is using a different mailbox index from Outlook Search. Whether my mailbox has been only partially ingested into the Copilot search service. Whether there are known issues affecting http://outlook.com/ personal accounts and Copilot email retrieval. Whether Microsoft can trigger a reindex, resynchronization, or repair of the mailbox content used by Copilot. Whether there are any diagnostic tools available to compare Outlook Search results versus Copilot Search results. Evidence Available I can provide: Screenshots showing 12 emails present in Outlook Inbox on 3 August 2026. Screenshots of Outlook Desktop search results. Screenshots of Outlook Web search results. Screenshots showing Copilot returning only a subset of those emails.
Copilot Studio consistent System Error issue
I have built an agent that invokes a Power Automate flow as a tool. Inside the flow, I'm using the Execute Agent and Wait activity, which calls another agent. This execution takes around 10–15 minutes to complete, after which the flow returns the result using Respond to Agent (asynchronous response). Although the flow completes successfully and the downstream agent finishes its execution, the calling agent still receives a System Error instead of the expected response. Why I'm using a Flow instead of directly connecting the agent Normally, I would connect the agent directly. However, the agent being invoked is already connected to another agent. Since agent → agent → agent chaining is not supported in Classic mode, I used a Power Automate flow as an orchestration layer to work around this limitation. Looking for someone who have faced this issue and has any solution to this.
Copilot Studio agents problems connecting to Sharepoint knowledge source
Hello, Since last week users in my tenant are experimenting issues regarding the connection between copilot studio agents and Sharepoint. The agents are not able to extract information from Sharepoint sites, printing there is not information in the Sharepoint site regarding the user's question when that information is in Sharepoint. These agents used to work well till last week. Does have been any update in Microsoft 365 services that can be affecting these agents ability to retrieve information from Sharepoint?Microsoft Copilot for IT Administrators: The Complete Enterprise Deployment Guide
Artificial Intelligence has moved beyond being an experimental technology and has become an essential part of modern enterprise productivity. Among Microsoft’s AI-powered offerings, Microsoft Copilot stands out as one of the most transformative tools for businesses. It helps employees automate repetitive tasks, improve collaboration, generate content, analyse data, and make faster decisions using natural language. https://dellenny.com/microsoft-copilot-for-it-administrators-the-complete-enterprise-deployment-guide/Microsoft Copilot for Project Management: A Complete Guide to Smarter Planning
Project management has always been about balancing priorities, managing deadlines, coordinating teams, and making informed decisions. As projects become increasingly complex, project managers are expected to do more with less—less time, fewer resources, and tighter budgets. Fortunately, artificial intelligence is transforming the way teams work, and Microsoft Copilot is leading that transformation. https://dellenny.com/microsoft-copilot-for-project-management-a-complete-guide-to-smarter-planning-faster-decisions-and-better-team-collaboration/Copilot Studio Agent for Excel Macro Modernization — Anyone Tried This?
Anyone built a Copilot Studio agent to analyze macro-enabled Excel workbooks (.xlsm) and recommend a modernization path — e.g., migrating logic to Power Automate or rebuilding as Power BI dashboards? Curious about real-world attempts: what worked, what didn’t, and where the ROI actually showed up. Would love to compare notes before diving in myself. #CopilotStudio #Excel #PowerAutomate #PowerBI #PowerPlatformFile processing capabilities in new Copilot Studio
In the classic version of Copilot Studio there is an option in settings to enable file uploads by users. This setting does not appear to be present in the new Copilot Studio settings and I have noticed that I am unable to upload a file to the agent when public via the MS365 Copilot channel. Has anyone else experienced this issue with the new Copilot Studio?Is Copilot Notebook Replacing OneNote? What I Tell Concerned Users
Copilot Notebook and OneNote both use the word notebook, so it is easy to assume that one is replacing the other. That is not what is happening. OneNote remains a useful place to capture notes, organize information, and develop content over time. Copilot Notebook serves a different purpose. It brings selected sources together so Copilot can help you work toward a specific project, topic, or outcome. You may use both tools within the same workflow. However, there are also times when Copilot Chat or SharePoint may be all you need. In my full article, I compare Copilot Notebook and OneNote, explain the licensing considerations, share workplace examples, and provide a simple way to choose the right Microsoft 365 tool for the work. https://traccreations4e.com/copilot-notebook-vs-onenote/ #MSFTOneNotePartner #traccreations4e-p26 8/3/2026Looking for ideas: Reducing "Allow" prompts when using SharePoint Knowledge
Hello community members! I'm hoping to get some advice from people who may have come across a similar challenge with their Copilot Studio "SharePoint knowledge retrieval" agents 🤞 Current setup Agent set up in Copilot Studio and published to channels - M365 Copilot and Teams Agent is connected to 4 SharePoint folders (I'm using Method#1 - see below screenshot for reference). This is essential because the documents inside the folders contain both text and image-based content. This is the only method that brings results Users have permissions to access the content in these folders Problem We are currently preparing to roll out this agent but we've hit a user experience issue that is becoming a blocker for moving forward. When a user interacts with the agent for the first time, they are asked to click "Allow" ... 4 times .. one for each of the folder that the agent is connected to This experience feels heavy for users (based on our pilot feedback) and people give up after the first or second time because they think it is not working. In spite of comms and a video about having to repeat this action until done. We want the first time experience to be as smooth as possible to drive adoption. Also, we are going to expand the solution to include more folders soon - so there is also a concern that number of consent prompts could grow further. What I've tried Used Method#2 to connect to SharePoint folders. While this didn't pop up the "Allow" prompts, as indicated earlier, this approach doesn't work because it doesn't return any results from documents as they contain both text and image content. Tried Method#1 to connect to the library (and use instructions to indicate necessary folders) - this didn't work because the method doesn't allow to connect to libraries. Note - I cannot restructure the library and put all the documents into one folder because that's the way the documents have been maintained for a long time & direct links to the folders are being used across the organization via. emails, decks etc. Looking for advice Has anyone found a way to reduce or eliminate these consent prompts? Are there any other recommendations on using SharePoint as a knowledge source that respects user permissions without these consent prompts? Does anyone know why Method#1 and Method#2 have different user experiences where the first one prompts for consent and the second doesn't?
Deterministic way to mark generative answer output as AI-generated - AI Act
Hi all, We have a text-based RAG agent in Copilot Studio using the Azure AI Search connector as the knowledge source. It's customer-facing. We need every generated turn to carry a machine-readable marker identifying it as AI-generated, not just a visible disclaimer line. Instructing the model to append something isn't acceptable for us, because it's non-deterministic and can be prompt-injected away. Has anyone found a cleaner pattern? Like how to do it?
All Copilot Studio Workflow Tools Suddenly Returning HTTP 403 Before Execution
Hello Copilot Studio Community, I am experiencing an authorization issue with multiple workflows connected to an agent built using the Copilot Studio new experience and new Workflows experience. These workflows worked successfully for multiple users yesterday. Today, all workflow tools connected to the agent began returning an immediate HTTP 403 authorization error. I did not intentionally change the agent, workflows, environment, or workflow permissions before the issue started. Error message: You don’t have permission to use this tool. You’re signed in, but access to this resource is blocked. Error details: Authorization - 403 Example error information: Status: Failed Error message: Flow returned HTTP 403 Error code: Http403 Inner error code: NotSpecified Tool duration: Approximately 93 milliseconds Configuration: - Copilot Studio new agent experience - Copilot Studio new Workflows experience - Agent and workflows are in the same Power Platform environment - Workflows use the "When an agent calls the workflow" trigger - Each workflow includes a "Respond to the agent" action - Workflows are saved and published - Agent is saved and published Observed behavior: The problem affects several independent workflows, including: - New-request submission - Current-user identity resolution - Approval decisions - Requester justification - Executive decisions - Fulfillment updates For every affected workflow: - The agent fills the workflow inputs correctly. - The tool call fails almost immediately. - No corresponding run appears in the workflow Activity history. - The workflow trigger is never reached. - No workflow actions execute. Because no workflow run is created, the rejection appears to occur before workflow execution, possibly within the Copilot Studio agent-to-workflow authorization or invocation layer. Troubleshooting already completed: - Confirmed that all workflows are published. - Confirmed that the agent is published. - Tested in a completely new conversation. - Removed an affected workflow tool from the agent. - Saved the agent. - Added the same published workflow back to the agent. - Reconfigured and verified the tool inputs. - Republished the agent. - Confirmed that no workflow Activity run is created. - Confirmed that the issue affects multiple workflows rather than one specific workflow. Removing and re-adding the workflow did not resolve the problem. Questions for the community: 1. Is anyone else currently experiencing HTTP 403 errors when Copilot Studio agents invoke workflows? 2. Is this a known issue or regression in the new Workflows experience? 3. Is there an environment-level or tenant-level permission that controls agent-to-workflow invocation? 4. Could a tenant policy, Conditional Access change, service principal, connection reference, or workflow-sharing configuration cause all workflow tools to fail simultaneously? 5. Where can an administrator find detailed authorization logs when the workflow never creates a run? 6. Has anyone found a workaround for this issue? Any guidance or confirmation from others experiencing the same behavior would be appreciated. I can provide screenshots, complete error details, timestamps, and additional configuration information if needed. Thank you.Is My Code Safe with GitHub Copilot? A Practical Guide for Developers and Businesses
Artificial intelligence has transformed software development, and one of the biggest names leading this change is GitHub Copilot. It helps developers write code faster, generate functions, explain unfamiliar code, and even suggest complete implementations based on natural language prompts. While the productivity gains are impressive, one question continues to surface among developers, engineering managers, startups, and enterprise organizations: https://dellenny.com/is-my-code-safe-with-github-copilot-a-practical-guide-for-developers-and-businessesURLs not accessible when running python script in sandbox
I have a script: import requests try: r = requests.get("https://google.com", timeout=10) print("Status:", r.status_code) print("Headers:", dict(r.headers)) print("Body:", r.text[:300]) except Exception as e: print(repr(e)) When I run it with an agent, it gives me this error: I have no idea how to make the URL valid for the conversation and it doesn't work with any URL I have provided so far.Scout Not Working After Upgrade from 0.23.331 to 0.23.578
I have been using Scout actively and after upgrading to 0.23.578 the device registration with GitHub has stopped working. I get to the point where it asks me for the device ID, GitHub accepts it then shows "sign-in could not be completed". I'm wondering if anybody else has experienced this. I'm inclined to think it is a new bug since the added the Enterprise host in this version.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.365 on iPhone cannot access work data
Microsoft 365 Copilot on iPhone recognizes that work data is connected. Enterprise Search can access my work content, and grounding works in Safari and on my other devices. However, Copilot Chat on this 1 phone does not return grounded results and behaves as if enterprise grounding is unavailable. Reinstalling, signing out/in, and resetting network settings did not resolve the issue.
Events
Register Here: https://aka.ms/MTC/CopilotRoadmapEvent
Keep up with the latest in Microsoft 365 Copilot, all in one place. This Roadmap webinar series is your central hub for the latest Copilot inno...
Online
Recent Blogs
- We want to inform the community that the Domain Exclusion for Microsoft 365 Copilot feature described in this post, More control over web grounding with Domain Exclusion for Microsoft 365 Copilot, ha...Aug 04, 2026
- Over the past two months, we’ve been previewing a new capability within Copilot Studio that lets you build agents capable of taking on more complex business processes. Today, we’re excited to share t...Aug 03, 2026
