Scheduled Prompts rerun a saved Copilot request at a chosen time or frequency. They are useful when you need a fresh answer repeatedly, not a full workflow across several systems.
Scheduled Prompts require a Microsoft Copilot license and can be disabled through organizational settings.
A recurring question becomes a standing instruction
💬Write the promptMake the scope and expected answer clear without chat history.
🗓️Set the scheduleChoose when and how often the prompt should run.
🤖Copilot runs itEach run uses the information available at that time.
📬Review the responseOpen the scheduled chat or use an email notification.
Use it for recurring answers that change
🌅
Prepare for the day
Each weekday morning, summarize today's meetings, the preparation each one needs and any recent work context that changes the agenda.
📨
Surface follow-ups
Every Wednesday, find earlier commitments or messages that still need your attention instead of relying on memory.
🧾
Review the week
At the end of the week, summarize decisions, open actions and items that should move into next week's plan.
Scheduled Prompt or Cowork automation?
Choose
When it fits
What runs
Scheduled Prompt
The same contextual question should produce a fresh response.
One prompt and its generated answer.
Cowork scheduled task
The recurring job creates files or performs several Microsoft 365 steps.
A supervised multi-step task.
Cowork event trigger
The job should begin because a matching email or message arrived.
A task started by an enabled event condition.
Outlook / To Do reminder
You only need a fixed notification at a time.
A reminder, without a new AI-generated result.
Write for a future run
The scheduled prompt may run days later without the conversational context you have today. Avoid references such as “that client,” “the project” or “recently.”
📅
Use a moving time window
Say “since the previous Friday” or “in the last 24 hours” so the prompt stays meaningful at every run.
🎯
Name the object and audience
Identify the project, team, mailbox or meeting type instead of relying on what was obvious when the schedule was created.
🔇
Define what to omit
State what counts as unimportant and what Copilot should return when there is nothing material, so repeated answers do not become noise.
Create and test the schedule
Run the prompt in ChatConfirm that the request produces a useful answer first.
Choose Schedule this promptHover over the prompt and open its scheduling action.
Set timing and notificationChoose the cadence, run count and optional email notice.
Use Run nowTest the saved version before depending on the next scheduled run.
Every weekday at 8:00 AM, summarize today's calendar. For each meeting, explain its purpose, list anything I should prepare and note any attendee I have not met in the last 30 days. Put meetings that require preparation first. If no meeting needs preparation, say that in one sentence.
Keep the schedule intentional
🔟
Use the ten-prompt limit well
Microsoft currently allows up to ten scheduled prompts per user. Keep the routines that affect decisions and remove low-value repeats.
⏸️
Turn off instead of deleting
Pause a useful design when the business rhythm changes, then restart or edit it when the routine returns.
🔐
Each run uses current access
The answer depends on the information and permissions available when the prompt runs, so results can change even when the wording does not.
💡
Key insight
Schedule a prompt when the repeated value is a fresh answer. Use Cowork when the repeated value is completed work.