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!
Need live support to get rid of Copilot and resolve billing
How do I contact a live support agent to get rid of Copilot and address billing issues? I need a passkey but cannot get one or contact a live support agent any other way the system has been running me around in circles. When I call the support number I need a passkey. But I cannot get a passkey under my admin support options. I subscribed directly through Microsoft and am the admin and sole user. I urgently need to get rid of Copilot from Word so I can use a specialized AI software for my business. It is designed to work in Word but has known conflicts with Copilot. The new software suggests change to my documents but cannot implement them because of Copilot. This interference is a known issue. Buying a second Business Standard subscription without Copilot and switching to that has not resolved the problem. I have tried logging out and in again, and clearing my cache. I am using the desktop version of Word. Billing and subscriptions are also an issue. My Business Standard plus Copilot subscription says "expired" and the three dots by the product don't give me any option to cancel or manage the subscription. But I also got a notice on June 18 that the annual subscription had been renewed, and that it will renew again in one year. I have not paid the most recent invoice. I don't want to test whether I would get more options by paying, since I don't want the copilot subscription and it is marked expired. I would appreciate any help on (1) disabling Copilot without disabling other connectors and (2) contacting a live person to address billing issues.
Prevent Copilot capacity pack from being consumed by Copilot Cowork
I’m looking for guidance on how to prevent a Copilot capacity pack from being used by Copilot Cowork while keeping the pack available for Copilot Studio agents and Power Apps. From what I understand, the prepaid Copilot capacity can be applied through billing or capacity settings, but I want to make sure it is not consumed by the Cowork or Microsoft 365 Copilot. I’m looking for the correct admin-side configuration to exclude that service, or to detach the capacity pack from it without breaking other usage. Additionally, I noticed that when mapping the capacity pack to an Azure subscription, there is no option to select a resource group. Is there any way to select a subscription? Ref. Link: https://learn.microsoft.com/en-us/microsoft-365/copilot/usage-based-billing-overview-copilot-credits Any official guidance or practical steps would be appreciated. Thanks in advance.
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.📣 Microsoft Copilot Studio and Agent Roadmaps Have a New Home
Microsoft Copilot Studio and Agent Roadmaps Have a New Home Starting July 2, 2026, feature updates for Microsoft Copilot Studio, Sales Agent, Finance Agent, and Service Agent, will be published on the Microsoft 365 Roadmap. This creates a single destination to discover what capabilities are coming next across Microsoft 365 core apps, Copilot, agents, and more. As part of this transition, Release Planner will no longer be a source for feature information for these products. Future updates will be available through the Microsoft 365 Roadmap, making it easier to stay informed, plan ahead, and leverage AI-powered experiences that can discover and consume information more effectively. What you need to know No immediate action is required Update any saved Release Planner bookmarks to the Microsoft 365 Roadmap Begin using the Microsoft 365 Roadmap as your primary source for feature updates Share this change with stakeholders who currently rely on Release Planner Resources: Stay up to date on what’s new and what’s next: Microsoft 365 Roadmap Microsoft 365 Copilot release notes Microsoft 365 Copilot Roadmap Webinar - Register today Get started with AI-powered change insights: Microsoft MCP Server for Enterprise - Gives MCP-compatible AI tools secure, read-only access to your organization’s Message Center and Service Health data, enabling personalized summaries, impact analysis, and stakeholder communications based on your existing permissions and security controls. Microsoft Release Communications MCP Server - Provides free, natural-language access to official Microsoft 365 Roadmap and Azure Updates information, enabling AI agents to answer questions about upcoming features, rollout timelines, and product changes. We're excited to bring roadmap information together in one place to deliver a more consistent, accessible, and AI-ready experience for planning what's next.
[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.
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!
