Custom Agent Builder agent suddenly failing with "Oops, something happened" - no config changes
Hi All, We built a custom agent in Agent Builder (Microsoft 365 Copilot) that generates a Word risk assessment by grounding on a contract (either the document currently open via the Word Copilot add-in, or a file uploaded in the web browser chat), plus a fixed set of knowledge sources (guidance notes, playbooks). It worked reliably for about 5 days while I was testing it solo. We then rolled it out to appr. 20 users, and shortly after, it started failing consistently with a generic "Oops, something happened, try again" error, typically after a long delay, in both the Word add-in and the browser version. I can't confirm causation, but the timing lines up closely with when we expanded from single-user testing to ~20 concurrent users. I don't know whether this points to a tenant-level capacity/concurrency limit being hit, or its something else, just stating it in case others have seen a similar threshold effect. Is this a known concurrency/capacity limit for Agent Builder agents once usage scales up, or a separate backend regression affecting document grounding, and has anyone else seen this pattern after moving from single-user testing to broader rollout?Cowork tasks not accessible - where are my cowork results?
I've been using cowork for several tasks/sessions, and I was impressed. When I was using it, I could switch between tasks/sessions and had always access to the results. Documents, and conversation. I even could continue and improve results a week later. Now, when I go to the cowork section in copilot, I still can see the list of cowork tasks at the left side. But each of them is completely empty. I mean white space, nada, nothing there.. not even a textbox to enter something. I tried with the M365 App, Edge, Firefox, new design. old design.. nada. So, what happened to my conversations and the generated documents? Is it a bug or expected behaviour? If it's expected, cowork is becoming less interesting for me. It means that I have to save my work/cowork all the time manually outside of the conversation (which I did for most of the generated documents, but not all) Help--- can I get the conversations and documents of each cowork session back, please? Dan
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!
Copilot file creation failing
When I am trying to create a file in m365 cloud environment I am getting an error saying that the file creation is failing. Here is a screenshot of it I don't know how to fix it. When searching with copilot it mentions about an entitlement issue but when I talked to an engineer in chats he said that wouldn't help and to post it here to see if anyone can help.
M365 Copilot shows Basic via group-based licensing, Premium via direct assignment
Hello, I wanted to share an issue we experienced with Microsoft 365 Copilot licensing and the workaround that resolved it, in case it helps others or Microsoft can confirm whether this is a known backend entitlement synchronization issue. We assigned a Microsoft 365 Copilot license to an existing user through group-based licensing. The user also had Cowork permission enabled. However, Copilot kept showing as Basic instead of Premium in the Microsoft 365 Copilot experience. We verified the license assignment through Microsoft Graph. The user had the Microsoft_365_Copilot SKU assigned, and all Copilot-related service plans were showing as Success. The relevant service plans were: M365_COPILOT_APPS: Success M365_COPILOT_BUSINESS_CHAT: Success M365_COPILOT_TEAMS: Success M365_COPILOT_SHAREPOINT: Success M365_COPILOT_INTELLIGENT_SEARCH: Success GRAPH_CONNECTORS_COPILOT: Success COPILOT_STUDIO_IN_COPILOT_FOR_M365: Success There were no visible licenseAssignmentStates errors, and the Microsoft 365 admin center also showed the Copilot license as assigned. We tried removing the user from the Copilot licensing group, waiting until the Copilot license was fully removed from the user, adding the user back to the same group, confirming that the Copilot license and service plans were assigned again, and testing again in a clean browser session and private browser session. The issue persisted. Copilot still showed as Basic. However, when we removed the user from the group-based licensing assignment and assigned the same Microsoft 365 Copilot license directly to the user from the Microsoft 365 admin center, the issue was resolved. Copilot changed from Basic to Premium, and Cowork became available. The effective workaround was to remove the user from the group-based Microsoft 365 Copilot licensing group, wait until the group-based Copilot license was removed, assign the Microsoft 365 Copilot license directly to the user, sign out or refresh the session, and then Copilot changed to Premium. This seems to suggest that the Microsoft 365 Copilot license was technically assigned through group-based licensing, but the downstream Copilot entitlement or Premium experience was not being correctly refreshed for that existing user. Direct user-based assignment appears to have triggered the Copilot entitlement refresh correctly. Has anyone else seen this behavior with Microsoft 365 Copilot and group-based licensing? Specifically, Microsoft Graph shows the Copilot license and all Copilot service plans as Success. Microsoft 365 admin center shows the license as assigned. The user still sees Copilot as Basic. Removing and re-adding the user to the licensing group does not fix it. Directly assigning the same Copilot license to the user fixes it. This looks like a possible group-based licensing to Copilot entitlement synchronization issue, especially for existing users. Any confirmation, known issue reference, or recommended remediation from Microsoft would be appreciated.
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?
[Japan region] Copilot Cowork not showing in the agents list despite all settings enabled
Hello, I'm based in Japan and my tenant region is Japan. I'm trying to enable the now-GA Copilot Cowork for my tenant, but Cowork does not appear in the agents list in the Microsoft 365 admin center, so I can't deploy it. Environment: Location / tenant region: Japan License: Microsoft 365 Copilot (assigned to target users and the admin account) All prerequisites appear to be in place and verified: Anthropic (AI provider acting as a Microsoft subprocessor): enabled Usage-based billing (Copilot Credits): enabled Discovery setting "AI experiences enabled by usage-based billing": set to allow users to discover and use Issue: Even with all of the above enabled, searching for "Cowork" under Integrated Apps → All agents returns no result. It also does not appear under Copilot → Settings → View all. As a result, I cannot deploy it to users, and Cowork does not show up for users at m365.cloud.microsoft either. Questions: Is there any additional setting required to make Cowork appear in the agents list? For a tenant in the Japan region, if there is a delay before the Cowork agent is provisioned after GA, what is the typical timeframe, and is there a way to check the rollout status for my tenant? Is there a specific admin role (e.g., AI Administrator) I should double-check on the account performing these steps? If anyone in the Japan region has resolved the same issue, I'd appreciate hearing how. Thank you.
