Scheduled prompt trigger not working for custom Copilot Studio Agent

Question

I have built an agent in Copilot Studio that is deployed to Teams/M365 Chat channel.

Which means, the same custom agent is available on Teams and M365 Copilot Chat.

Now, I had the prompt that I sent to the custom agent, scheduled in M365 Copilot, through the Schedule Prompt feature in Copilot Chat.

The schedule does triggered every day at the time that I had set it up for, but the agent doesn't get triggered by it and even though the trigger/schedule shows succeeded, that really did not trigger the agent.

Similar to 'schedule prompt' in M365 Copilot Chat, I used the Workflows feature in MS Teams to schedule the trigger. Again, the workflow schedule works consistently everyday, but it doesn't really trigger the custom agent that I'd built.

My goal is to automatically trigger the agent everyday at a schedule time. There is no action trigger, it is a schedule trigger. How do I get the M365 Copilot chat schedule/workflow schedule to actually trigger the agent?!

Or, is there an alternate solution?

Answer 1

The Scheduled Prompt feature in Microsoft 365 Copilot Chat and Teams Workflows can execute on a schedule, but they do not programmatically invoke a Copilot Studio conversational agent. A successful schedule execution only indicates that the scheduled task ran—it does not guarantee that the custom agent was launched or processed the prompt.

Currently, Copilot Studio conversational agents are designed to be user-initiated and there isn't a supported capability to automatically start a conversation with an agent on a recurring schedule.

If your objective is to automate business logic on a schedule, the recommended approach is to:

• Use a Power Automate scheduled cloud flow (or Logic App) to run the required automation directly.
• If your agent relies on Power Automate flows or backend APIs, schedule those flows/APIs instead of trying to trigger the conversational agent.

If your requirement is specifically to have the Copilot Studio agent itself run automatically every day without user interaction, this scenario is not currently supported.