Forum Discussion
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!
1 Reply
- LdecubaCopper Contributor
Hi Fahran,
as far as i can tell from documentation it doesn't run in a different runtime, Custom MCP, Custom Plugins and Custom Skills are supported. No extra permissions needed or separate config. I haven't tried this out with Custom MCP but several people are reporting that scheduled sessions are starting up without MCP connectors registered in the tool set. Sorry i can't be of more help just sharing what i've heard on this topic.