Cowork tab appearing despite Admin settings
The Cowork tab in the Copilot App has started to appear for some of our Basic and Premium users. I'm not sure why this is happening as we have not setup any usage-based billing and explicitly disabled the following admin setting: Despite this, the users are able to click on the Cowork tab and enter a prompt. When it is submitted, Copilot tries to login, fails and continues trying to authenticate over and over again. I also cannot find the Copilot Cowork agent (1.3.0) in the Agent Registry to block it.
Microsoft Cowork (Frontier) Scheduled Runs Can't Access Custom Plugins/MCP Tools
Hi everyone, I'm currently building a ServiceNow incident handling automation using Microsoft Cowork (available through the Microsoft Frontier program) and have run into an issue that I haven't been able to resolve. Solution Architecture I have built: A custom FastAPI MCP backend hosted on Azure Web App MCP tools for: Fetching new ServiceNow incidents (state = new) Retrieving relevant ServiceNow Knowledge Base articles based on incident context Updating ServiceNow comments and work notes Performing Microsoft Entra ID automation (e.g., user profile updates requested through incidents) Custom plugins and skills deployed through the Microsoft 365 Admin Center What Works When I start the Cowork agent manually and provide instructions such as processing new incidents: It successfully discovers my custom tools. It fetches incidents from ServiceNow. It retrieves KB articles. It updates work notes/comments. It performs Entra ID actions when required. It processes incidents sequentially according to the workflow. So the overall integration appears to be working correctly. The Problem The issue occurs when I configure the Cowork agent to run on a scheduled basis (every hour). Instead of executing the workflow, the agent reports messages like: and after retries: From the Workspace panel, I can see the scheduled task is active, but during scheduled execution it behaves as if none of the custom plugins, skills, or MCP tools are available in the session. And when I go to the same scheduled session and manually enter the same prompt which I had provided in the scheduled part, then it is working as expected. Questions Are scheduled Cowork runs executed in a different runtime/session context than manual runs? Do scheduled runs currently support: Custom MCP servers? Custom plugins deployed through M365 Admin Center? Custom skills? Are there any additional permissions, trust settings, or plugin approvals required specifically for scheduled executions? Has anyone successfully used scheduled Cowork tasks with custom MCP tools or external systems such as ServiceNow? Is this a known limitation of the current Frontier preview? Any guidance or confirmation from others using Cowork + MCP integrations would be greatly appreciated. Thanks!Copilot and DLP policy behaviours
Hi Copilot Brain Trust, Looking for some real-world experiences with Microsoft 365 Copilot DLP enforcement. We've implemented a DLP policy targeting the Microsoft 365 Copilot location with the action to prevent Copilot from processing content that contains our sensitivity label (restricted). The implementation is based on the following Microsoft documentation: DLP for Microsoft 365 Copilot: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about Create DLP policies for Microsoft 365 Copilot: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot Microsoft documentation states that when a DLP policy blocks Copilot processing, protected content should not be processed or used in Copilot-generated responses (although citations may still appear). However, during testing we're observing scenarios where Copilot appears to access/process provide restricted snippet with file names from content that should be protected by the DLP policy. A few questions for anyone who has implemented this in production: Have you successfully validated DLP policies preventing Copilot from summarising sensitivity-labelled content? Are there any known delays between policy deployment and enforcement? Have you observed differences between Copilot Chat and Copilot experiences within Word, Excel, or PowerPoint? Are there any prerequisites, limitations, or known issues not currently reflected in the public documentation? I'm interested to hear whether others have seen similar behaviour or have successfully validated this scenario end-to-end. Thanks in advance.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
PowerShell: Export Microsoft 365 Copilot Agent Inventory and Availability Assignments
Hi everyone, I needed a way to export Microsoft 365 Copilot agent inventory and availability assignments from the Microsoft 365 Admin Center, but couldn't find a built-in export option. After investigating the admin portal's network traffic, I built a PowerShell script that uses the same internal API consumed by the Microsoft 365 Admin Center to export all Copilot agents to CSV. ### Features - Exports all Microsoft 365 Copilot agents - Automatically follows pagination (`nextLink`) - Exports: - Agent Name - App ID - Title ID - Publisher - Created By - Availability Settings - Allowed Users / Groups - Assignment Information - Deployment Information - Version Information - Timestamps - CSV output ### Tested The script has been tested against a tenant containing 482 Copilot agents and successfully exported the complete inventory. ### GitHub https://github.com/gwestergren/M365-Copilot-Agent-Inventory ### Notes - Uses an authenticated browser session cookie from the Microsoft 365 Admin Center. - Uses the same internal API currently consumed by the admin portal. - This is an undocumented API and Microsoft may change it at any time. Feedback, testing results, and improvements are welcome. Here are some screen shots: output to csv Successful run of the scriptCopilot 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.Copilot Chat vsus. Microsoft 365 Copilot. What's the difference?
While their names sound similar at first glance, Microsoft 365 Copilot and Microsoft 365 Copilot Chat, they differ in several aspects. And more importantly: one is built on top of the other. What is Copilot Chat (Basic)? First things first. Microsoft 365 Copilot Chat is often simply called Copilot Chat. Copilot Chat (Basic) generates answers based on web content, while Microsoft 365 Copilot (Premium) is also grounded on users' data, like emails, meetings, files, and more. Since early 2025, Microsoft 365 Copilot Chat has been available to all users in organizations, becoming the entry point to AI assistance for many organizations. Copilot Chat (Basic) is the foundational Copilot experience available at no extra cost for everyone with an eligible Microsoft 365 plan, including: Microsoft 365 E3 / E5 Microsoft 365 A3 / A5 Microsoft 365 Business Standard & Business Premium Copilot Chat (Basic) is secured, compliant, and it does not required the full Copilot add-on license. Copilot Chat (Basic) is able to ground responses on: Public web content. Content explicitly shared or work data manually uploaded to the chat by the user. On-screen content or content displayed on-screen in apps like Outlook, Word, Excel, PowerPoint, and OneNote. When it comes to agents, Copilot Chat (Basic) offers these features: You can create your own declarative agents grounded on public web content with Agent Builder. You can use agents built by your org grounded on organizational data with the pay-as-you-go method. There are Microsoft prebuilt agents available like Prompt Coach, however Microsoft premium prebuilt agents like Researcher or Analyst are not included. The screenshot below shows how Copilot Chat looks and highlights its main capabilities. Note the Upgrade button, meaning this is not Microsoft 365 Copilot, but the Copilot Chat (Basic) experience. Note that EDP (Enterprise Data Protection) is available in Copilot Chat (Basic). What is Microsoft 365 Copilot (Premium)? Microsoft 365 Copilot (Premium) is a paid add-on license that builds on top of Copilot Chat and unlocks Copilot's full power. It is available for selected Microsoft 365 plans, including: Microsoft 365 E3 / E5 Microsoft 365 A3 / A5 Microsoft 365 Business Standard & Business Premium With a Microsoft 365 Copilot license, users get everything Copilot Chat (Basic) offers, plus much more: Data grounding: Microsoft 365 Copilot (Premium) includes Copilot Chat grounded on web and/or on user's Microsoft 365 data like emails, meetings, chats, and documents. Office apps: It integrates deeply into Microsoft 365 apps like Outlook, Teams, Word, Excel, and more. The integration includes features like Edit with Copilot allowing Copilot to adjust live your documents or email based on your prompts. Custom agents: It brings the capability to create your own declarative agents grounded in organizational data and/or web data. You can create agent either using Agent Builder or Copilot Studio. MS prebuilt agents: Premium prebuilt agents like Researcher and Analyst are included in Microsoft 365 Copilot (Premium). The screenshot below shows the Copilot chat experience for users who have a Microsoft 365 Copilot license. Note that EDP or Enterprise Data Protection also applies here How can I access Microsoft 365 Copilot Chat? Today, Copilot Chat is accessible via https://m365.cloud.microsoft or https://copilot.cloud.microsoft using your Entra ID (work or school account). One important difference in day-to-day experience: Users with a Microsoft 365 Copilot license typically see Copilot prominently surfaced across Microsoft 365 apps. Users with Copilot Chat only may not see it pinned by default on the Microsoft 365 home page. To improve discoverability, Microsoft 365 Copilot administrators can pin Copilot Chat via the Microsoft 365 admin center, ensuring that users can easily access it without friction. Especially convenient is that if you use the M365 Copilot Chat app on Windows, you can open Copilot using the keyboard shortcut Ctrl + C. What’s the difference? The differences between Copilot Chat and Microsoft 365 Copilot mainly come down to: Licensing Data grounding (web-only vs. personal work data) Integration depth within Microsoft 365 apps I’ve listed the key differences in the comparison below. 👇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.
Is the Copilot model picker available in Word for the Microsoft 365 Premium (Individual) plan?
Hello, I would like to confirm whether the Copilot model picker is available in Microsoft Word for subscribers of the Microsoft 365 Premium Individual plan. Specifically, I am referring to the feature that allows users to switch between different AI models, such as: - Claude Opus 4.7 - GPT-5.5
