Copilot Connectors >Azure DevOps Work Items >Add Property
Hi I have setup the Azure DevOps Work Item connector and all is working OOTB. However when I try to 'Add a new source Property' and add for example 'TargetDate' when I publish the schema change it errors with: Schema failed to publish with error [Removal existing property is not allowed.] I havent removed anything just added. Anyone else experienced this? Many thanks
Copilot Down - June 1st
I used Copilot this morning and everything was working smoothly. All of a sudden when I open the app on Windows I get this message "Couldn't load the app. Wait a bit, then try again." I tried using the version on Edge but I get a "503 Service Unavailable Error." I tried restarting my laptop and I get the same error. Checked on my phone app and indeed, it confirmed the service is down. Does anyone know when this will be resolved?Has anyone seen Excel workbooks become corrupt after using M365 Copilot to summarize data?
We’ve run into an issue twice where a user opened an existing Excel sales workbook, used Microsoft 365 Copilot in Excel to summarize/analyze the data, received the response successfully, and then later could no longer open the original workbook because Excel reported it as corrupt. Internally, this has been reported as happening on some files but not all, and it has occurred twice so far. I’m trying to determine whether this is: a known issue with Copilot in Excel a workbook-specific problem related to file location/sync/versioning or something tied to workbook structure I did find public reports of related Excel Copilot issues — including Copilot crashing in Excel, failures that seem specific to certain workbooks, and Copilot-created Excel files being reported as invalid/corrupt — but I have not yet found a clear Microsoft-hosted thread describing this exact scenario with the original existing workbook becoming corrupt after summarization. If anyone has seen this, I’d appreciate any insight on: whether Microsoft has acknowledged a known issue whether this points to specific workbook features/structures whether there are logs or diagnostics that help isolate root cause whether there are best practices to reduce the riskCopilot Employee Self-Service Agent
I’m looking for some clarity regarding the rollout of the https://adoption.microsoft.com/en-us/ai-agents/employee-self-service-agent/ and whether others are seeing it in their environments yet. I’ve been following this closely and initially understood that a formal request was required to gain access. However, the Microsoft Learn documentation now provides specific, step-by-step instructions on how to enable and access it directly. Despite following those instructions to the letter, the agent is still not appearing within my tenant. I’ve verified my configurations against the guide, but the options simply aren't visible. A few questions for the community: Has anyone else successfully enabled the agent using the self-service steps in the documentation? Is there or was there ever a manual "request-for-access" process that overrides the published steps? I’d appreciate any insights or if anyone from the product team could clarify if the documentation is slightly ahead of the actual deployment.
Prompt Lab: Three Critical Bugs That Make It Unusable as a Prompt Management Tool
Product: Microsoft 365 Copilot — Prompt Lab (accessed via ... button in Copilot Chat) Date: June 1, 2026 Environment: M365 Copilot, Web (Edge), Work IQ mode Bug #1: Empty State Crash Steps to reproduce: Open Prompt Lab via the ... button in Copilot Chat Ensure "Your saved prompts" contains zero prompts (either as a new user or by deleting all saved prompts) Observe the result Expected behavior: An empty state placeholder (e.g., "You haven't saved any prompts yet.") Actual behavior: The entire Prompt Lab panel throws a red error banner: "Something went wrong. Please close the dialog and try again later." The "Your saved prompts" category does not render at all. The panel only shows Microsoft's preset categories (Prompt topics, Agent prompts). Why this matters: An empty container is a valid state — it is literally every new user's initial state. A UI component should never crash because a list has zero items. This is a null/empty array handling failure that should have been caught by basic QA. Bug #2: Search Does Not Index User's Saved Prompts Steps to reproduce: Save a custom prompt with a distinctive title (e.g., "AI每日新闻") and body containing the keyword "AI" Open Prompt Lab Use the search box at the bottom to search for "AI" Expected behavior: Search results include the user's saved prompt alongside Microsoft's preset prompts. Actual behavior: Only Microsoft preset prompts matching "AI" are returned (e.g., "Stay on top of AI," "Prompt Compliance"). The user's own saved prompt — whose title and body both contain "AI" — does not appear in the results. Why this matters: The search box creates a false expectation that it searches all prompts. In reality, it only indexes Microsoft's template library. This means as a user accumulates more saved prompts, the only way to find one is manual scrolling. A search function that excludes user-created content is fundamentally broken by design. Bug #3: Saved Prompts Lost During Migration Context: The standalone Copilot Lab / Prompt Gallery app was retired on July 15, 2025, and its functionality was merged into the built-in Prompt Lab within Copilot Chat. What happened: All previously saved prompts from the old Copilot Lab app are gone. They do not appear in the new Prompt Lab's "Your saved prompts" section. There was no migration notice, no export tool for end users, and no recovery path. Why this matters: Users invested time curating and refining their prompt libraries. Silently dropping that data during a platform migration — without warning, backup, or migration tooling — is a breach of user trust. Summary These three issues compound into a single conclusion: Prompt Lab is currently non-functional as a prompt management tool. Capability Status Reliable storage ❌ Data lost during migration Empty state handling ❌ Crashes when empty Search / retrieval ❌ Does not index user content Displaying Microsoft templates ✅ Works The only feature that works correctly is showcasing Microsoft's own preset prompts. For a tool whose entire purpose is to help users save, organize, and reuse their own prompts, this is an unacceptable state of quality. I'd strongly recommend the team prioritize: (1) proper null-state handling, (2) including user prompts in the search index, and (3) investigating whether migrated prompt data can be recovered from Substrate.
Location of custom skills - cannot find them in OneDrive
I'm using Copilot Cowork to create skills, and Cowork insists the skills are being saved in OneDrive>Documents>Cowork>skills but I cannot find them in there. I cannot find the raw MD files anywhere in OneDrive, and Cowork can only surface them when I ask to see them. Anyone else experienced this and have the answer? I need to be able to create Cowork Skills and store them in a central repository for the team to use. #coworkArchitectural: Copilot should detect missing source data, avoid inference, and surface uncertainty.
Users expect the AI to detect when it lacks source data, avoid inference, surface uncertainty, and adapt to environmental constraints like character normalisation. These behaviours materially improve trust and usability. I’ve been working with Copilot on structured data extraction from a PDF and noticed a behaviour that seems like an architectural gap rather than a simple bug. Copilot attempted to infer table structure from a template when it did not have access to the actual source data. It produced confident but incorrect output instead of signalling that the source was unavailable. Additionally, Copilot attempted to output TAB‑delimited data, but the MS365 environment silently normalised TABs to spaces, and Copilot did not detect or adapt to this constraint. Recommendation: Copilot should proactively: detect when it lacks source data avoid inference when accuracy is expected surface uncertainty explicitly detect environment‑specific formatting limitations (e.g., TAB stripping) adapt output formats automatically These behaviours would materially improve trust, reliability, and user experience.Cowork Custom Instructions Not Autoloading
When you tell Cowork "remember this for next time" or "always do X," Cowork suggests (or just goes ahead and makes) an update to copilot-instructions file. It tells you the preference has been saved and the file does get written. However, it doesn't automatically load the custom instructions file at the start of new sessions. You have to specifically mention it in a prompt. Once you do, it will load the and use the file to guide its responses for the remainder of the session. I feel like one of two things are happening here: 1. I'm missing something 2. The Cowork dev team missed implementing what I would consider a basic feature, even for a "Frontier" feature. Can anyone else confirm that this is the behavior they experience?
All scheduled prompts failing — "couldn't be completed" error — Power Platform provisioning issue?
I'm hoping someone from Microsoft or the community has seen this. All my scheduled prompts are failing at execution time with this error: "This scheduled prompt couldn't be completed. It will be retried during the next scheduled run." Key facts: M365 Copilot license on a direct Business subscription The same prompts run correctly in Copilot Chat Even the simplest scheduled prompt fails: "List emails I received in the past 5 days. No analysis needed — just the list." The scheduling UI works fine — prompts appear in the Active list with correct schedules Failure is at execution time. Retries also fail. Admin-side investigation already completed: Power Platform environment: Ready No DLP policies in the tenant No admin toggle for scheduled prompts exists in M365 admin center (noted as unusual) Org-level optional connected experiences: enabled User-level optional connected experiences toggle absent (consistent with org locking it On) The absence of an admin toggle for scheduled prompts in the M365 admin center is the one thing that stood out — I wonder if this indicates the feature wasn't fully provisioned when the Copilot license was applied. Sharing here in case this is a known issue or others are experiencing the same. Any insight from Microsoft engineers or others who've resolved this would be appreciated.
