3.4 Scheduling Prompts

Microsoft AI Business Professional AB-730

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 About the AB-730 Exam 0.2 How to Use This Study Guide

2 Chapter 1: Understand Generative AI Capabilities Across Microsoft 365

1.1 How Copilot Works: LLMs, Microsoft Graph & the Security Boundary 1.2 Context & Grounding: Work Files, Web Data and App Context 1.3 Chat Experiences vs. Agent Experiences 1.4 When to Create Your Own Agent 1.5 Copilot Capabilities Across Microsoft 365 Apps

3 Chapter 2: Responsible AI & Data Protection Practices

2.1 Generative AI Risks: Fabrications, Prompt Injection & Over-Reliance 2.2 Verification Steps: Citation Checks & Human Review 2.3 Recognizing & Mitigating Risks to Sensitive Data 2.4 How Data Protection Restricts Prompt Results

4 Chapter 3: Creating and Managing Prompts

3.1 Creating an Effective Prompt: The GCSE Framework 3.2 Selecting Resources to Reference in a Prompt 3.3 Saving and Sharing Prompts in Copilot Prompt Gallery 3.4 Scheduling Prompts

5 Chapter 4: Managing Conversations and Notebooks

4.1 Finding Previous Conversations 4.2 Renaming and Deleting Chats 4.3 Adding a Conversation to a Copilot Notebook

6 Chapter 5: Creating and Managing Microsoft 365 Copilot Agents

5.1 Agent Store vs. Creating a New Agent 5.2 Creating an Agent from a Template 5.3 Configuring an Agent That Has Knowledge 5.4 Configuring Instructions, Capabilities & Suggested Prompts 5.5 Sharing an Agent with Team Members

7 Chapter 6: Drafting and Analyzing Business Content

6.1 Creating a New Document from a Prompt 6.2 Generating a Document from an Existing Document 6.3 Generating a Management Summary 6.4 Moving Data & Insights Between Microsoft 365 Apps 6.5 Drafting Communications with Copilot in Outlook

8 Chapter 7: Meetings, Collaboration and Personalization

7.1 Using Copilot for Meetings: Setup & Live Intelligence 7.2 Meeting Recap, Transcripts & Catch-Up 7.3 Copilot Pages for Collaboration 7.4 How Copilot Uses Memory & Instructions

3.4 Scheduling Prompts

Key Takeaways Explain This Topic AI

Schedule a prompt by hovering over it, selecting Schedule this prompt, setting when and how many times it runs, then selecting Save.

Each user can create up to 10 different scheduled prompts.

Scheduled prompt responses appear in the Chats section on the left side of the Copilot window, with an optional email notification.

Manage scheduled prompts from the ... Settings and more menu at the top right of the Copilot app, then Scheduled prompts.

Scheduling requires a Microsoft Copilot license and works in Copilot Chat, Copilot in Microsoft Teams, and Outlook for web and desktop.

Last updated: August 2026

3.4 Scheduling Prompts

Quick Answer: Hover over a prompt and select Schedule this prompt . Choose when the prompt will run , how many times it will run , and whether you want an email notification when the response is ready, then select Save . You can create up to 10 different scheduled prompts. Responses appear on the left side of the Copilot window in the Chats section.

Scheduling is the blueprint's own bullet, separate from saving and sharing, and it is tested as a procedure. Know the command name, the three options, the limit, and where the output lands.

Where Scheduling Works

Scheduled prompts run in Copilot Chat , Microsoft Copilot in Microsoft Teams , and Microsoft Outlook for the web and Desktop . A Microsoft Copilot license is required .

Question Answer
What is the command called? Schedule this prompt
What can you configure? When it runs, how many times it runs, email notification on completion
How many can one user have? Up to 10
Where do responses appear? The Chats section on the left of the Copilot window
Where do you manage them? … Settings and more → Scheduled prompts
Creating a Scheduled Prompt

Go to Copilot Chat and sign in with your Microsoft 365 account.

Hover over the prompt and select Schedule this prompt .

Select options for when the prompt will run , how many times it will run , and whether you'd like to get an email notification when the response is ready.

Select Save .

The prompt then runs on your schedule without you opening anything. Because it executes in your security context, it can only reach content you could already reach — a scheduled prompt is not a way to widen access, and a colleague's schedule will produce different results from yours over the same query.

Managing Existing Schedules

Select the … Settings and more menu at the top right of the Copilot app, then select Scheduled prompts . From that collection you can:

Run a prompt immediately rather than waiting for its next occurrence.

Edit the schedule to change timing or frequency.

Turn a prompt off without deleting it.

Delete it entirely.

The ten-prompt ceiling makes this housekeeping matter. Scheduled prompts accumulate: people automate a report for a project that ends, then find they cannot add a new schedule. Turning off or deleting obsolete schedules is the fix.

What Is Worth Scheduling

Automation earns its keep when a question is recurring , time-boxed , and answerable from data that changes on its own .

Good candidate Why it works
A start-of-week summary of what changed on a project The underlying content changes weekly without you
A recurring digest of messages you were mentioned in Volume is unpredictable; the cadence is not
A pre-meeting brief before a standing weekly sync The meeting recurs on a fixed schedule

Poor candidate Why it fails
A one-off research question Nothing recurs; just ask it
Anything needing a fresh source each run The prompt's references go stale
A question whose answer you would not read Automation produces unread output, not value

On the Exam: If an option describes scheduled prompts running with elevated permissions, reaching another user's mailbox, or bypassing sensitivity labels, it is wrong. Scheduling changes when a prompt runs, never what it is allowed to see .

Realistic Business Scenario: The Monday Programme Brief

A programme manager spends the first forty minutes of every Monday asking Copilot the same three questions about status changes across her portfolio. She consolidates them into one prompt, tests it, and saves it.

She then hovers over the saved prompt, selects Schedule this prompt , sets it to run weekly, and enables the email notification so she knows the response is waiting. Each Monday the answer is already sitting in the Chats list when she opens Copilot.

Two months later the programme closes. Rather than leaving the schedule running against a dormant portfolio, she opens … Settings and more → Scheduled prompts and deletes it, freeing one of her ten slots for the next programme.

Save, Schedule, Share — Three Different Bullets

The blueprint lists save a prompt , schedule a prompt and share a prompt as three separate sub-topics, and items exploit the overlap. Keep the verbs distinct:

Action What it changes Where it lives afterwards
Save Keeps the prompt text for your own reuse Your Prompts in Copilot Prompt Gallery
Schedule Makes the prompt run on its own, on a cadence Scheduled prompts under the … Settings and more menu
Share Makes the prompt available to colleagues Team prompts in Copilot Prompt Gallery

Saving does not schedule. Scheduling does not share. Sharing a prompt hands over the text , not the schedule — a colleague who wants it to run automatically has to schedule it themselves, against their own ten-prompt allowance and their own permissions.

Writing a Prompt That Survives Automation

An interactive prompt can be vague, because you are there to correct it. A scheduled prompt runs when you are not, so it has to stand alone.

No deictic references. "Summarise the attached deck" has no meaning at 7 a.m. on a Monday with nothing attached. Name the source explicitly.

State the output format. Without one, the same question returns a paragraph one week and a table the next, which makes the results hard to skim.

Bound the time window. "Changes since last week" ages correctly; "changes since the kickoff" does not.

Keep it answerable from data that moves on its own. Automation adds value when the underlying content changes between runs.

Troubleshooting a Scheduled Prompt

Symptom Most likely cause

Schedule this prompt does not appear You are on an unsupported surface, or you lack a Microsoft Copilot license

The option is greyed out and you already have several You have hit the 10 scheduled prompt ceiling; turn off or delete an obsolete one

The run produced a thin or empty answer Permissions or sensitivity labels on the referenced content, not the schedule itself

You never noticed the response The email notification was not enabled; the response is still in the Chats list, bolded with an icon

Results drifted over weeks The prompt referenced a moving target such as "this quarter" without an explicit window