Copilot Scheduled Prompts Retire Dec 31: 7-Step Guide

TL;DR: Copilot scheduled prompts that run on Power Platform retire on December 31, 2026 and stop running after that date. Microsoft says anyone who wants to keep a schedule must recreate it as a scheduled task, managed under the Scheduled tab. Inventory the old schedules now, tell their owners and rebuild only the ones worth keeping.

On December 31, 2026, every Copilot scheduled prompt that still runs on Power Platform stops. The Monday briefing, the Friday wrap-up and the daily inbox summary your early adopters rely on will stop arriving. This guide gives IT and adoption leads seven steps to find those schedules, move the useful ones and set rules for scheduled tasks before the deadline.

Microsoft confirmed the change in Message Center post MC1550533 on November 12, 2026. Start now. In the last week of December, the people who built those schedules are on vacation.

Who is this guide for, and what will you have at the end?

This guide is for Microsoft 365 admins, Copilot adoption leads and help desk managers in organizations where people already schedule Copilot prompts. At the end you will have an inventory of legacy schedules, each one rebuilt or retired, and a short set of rules for scheduled tasks.

A Copilot scheduled task is a prompt that Microsoft 365 Copilot runs automatically at a set time and frequency, even when the person is away, and returns to the conversation it belongs to. Scheduled tasks replace scheduled prompts. According to Microsoft's guidance on managing scheduled prompts for Copilot, they no longer use a Power Platform environment, and their data is processed and stored inside the Microsoft 365 compliance boundary.

The move is part of the same shift that brought Office in Copilot: more of the work now starts and finishes inside the Copilot app. Here is what changes.

Source: 2toLead, based on Microsoft Learn and Message Center post MC1550533.

What do you need before you start?

You need Microsoft 365 Copilot licenses for the people who schedule tasks, one admin with the Power Platform Administrator role and PowerShell 7 for the inventory. Nothing here needs new spend.

If your license mix is changing this quarter, check our guide to the Microsoft 365 Copilot licensing changes for December 2026 first, so you move schedules only for people who keep a license.

How do you move Copilot scheduled prompts before December 31?

Move Copilot scheduled prompts in seven steps: confirm your rollout window, get access, export the inventory, tell owners, triage, recreate and verify. Steps 1 to 4 belong to IT. Steps 5 to 7 belong to the person who owns each schedule.

1. Confirm your rollout window. Open Message Center post MC1550533 in the Microsoft 365 admin center and note when the Scheduled tab reaches your tenant. Microsoft lists Frontier tenants from November 11 and the worldwide rollout from November 30 to December 31, 2026, and says timing may change. If you manage preview groups, our release rings guide explains who sees changes first. Expected result: A named owner and a target finish date at least two weeks before December 31.
2. Get access to the Microsoft 365 environment. In the Power Platform admin center, select the Microsoft 365 environment, select Membership, then select Add me. Expected result: You hold the System Administrator role on that environment. Microsoft says it can take about 30 minutes to apply.
3. Export the legacy inventory. Run Microsoft's Get-CopilotActions.ps1 script with your environment ID and pipe the output to Export-Csv. The script is in the Inventory for scheduled prompts article on Microsoft Learn, linked from the page above. Add the result to the same tracker you use for the five Power Platform retirement deadlines. Expected result: A CSV file listing each schedule's name, creator, created date and status.
4. Tell every owner in writing. Send each person on the list one short message with the December 31 date, the new home (the Task icon, then Scheduled), the limit of 10 active schedules and their own list. Ask early adopters to check Power Automate too, because prompts scheduled during the public preview run there and do not show on the Copilot page. Expected result: Every owner has the date, the path and their list at least two weeks before the deadline.
5. Triage each schedule. Ask each owner to mark every schedule as keep, rewrite or retire, using the table below. A schedule nobody reads is not automation. It is noise with a timer. Expected result: One decision recorded beside every row of the inventory.
6. Recreate the keepers as scheduled tasks. In Copilot Chat, hover over the prompt, select Schedule this, choose when and how often it runs, then select Save. People can also describe the schedule in plain language in Copilot Chat. Expected result: The task shows in the Active section of the Scheduled tab.
7. Verify and tidy. Select the Task icon, select the Scheduled tab, then select Run now on each new task. Use Pause or Delete on anything left over. Expected result: A response appears under Chats in bold with an icon, and nothing unwanted remains under Active.

Use this triage table in step 5.

Source: 2toLead keep, rewrite or retire triage.

What mistakes should you avoid, and how do you fix them?

The three costly mistakes are waiting for an automatic migration, assuming your old admin control still applies and rebuilding every schedule without triage. Each has a simple fix.

• Waiting for a migration. Microsoft Learn says people must create each schedule again. Fix: treat every schedule as manual until the owner sees it under the Scheduled tab.
• Trusting the old off switch. Legacy scheduled prompts followed the connected experiences policy. Microsoft says scheduled tasks are not a connected experience and have no separate policy setting. Fix: update your acceptable-use guidance to cover tasks that run while nobody is watching.
• Looking in Teams or Outlook. Microsoft's support article says both are outside the first release. Fix: point people to Copilot Chat on the web or desktop.
• Hitting the limit. Each person gets 10 active schedules and 50 in total. Fix: retire first, then recreate.
• Mixing up Cowork. Copilot Cowork has its own scheduled prompts, managed under Automations, and Cowork is metered in Copilot Credits. Fix: decide which schedules justify credits, using our Copilot Credits and FinOps for AI guide.

How do you check the move worked?

The move worked when every kept schedule shows as Active under the Scheduled tab, has produced one response and has an owner who confirmed it. Check five points in the week before December 31.

• Each owner's count of Active tasks matches the keep and rewrite rows in your inventory.
• Run now returned a response under Chats for each task.
• No task is stuck. Microsoft says a task that needs the person's approval pauses until they respond in its conversation.
• Your help desk article names the new path. For 30 days after the Scheduled tab arrives, schedules show in both the More options (...) menu and the Scheduled tab. After that, only the tab remains.
• You ran the PowerShell inventory one last time. From January 1, 2027, scheduled tasks will not appear in it.

In healthcare, education and government, ask your compliance lead to confirm how scheduled task activity shows in the Microsoft Purview audit log, and record that Copilot now runs these tasks without the person present.

How do you measure the result?

Measure the move with four numbers: migration rate, active tasks per licensed person, first-run success and hours returned.

• Migration rate: schedules recreated divided by schedules marked keep or rewrite.
• Active tasks per licensed person: a sign that Copilot works for people while they are away.
• First-run success: the share of new tasks that returned a useful response on Run now.
• Hours returned: minutes saved per run, multiplied by runs per month.

Here is a worked example with illustrative numbers. Replace them with your own.

• Your inventory shows 60 legacy schedules owned by 25 people. Triage keeps 40.
• Each kept schedule saves its owner 15 minutes a week. That is 10 hours a week, or about 43 hours a month. At a loaded cost of $65 an hour, the kept schedules return about $2,800 a month.
• The move takes about 4 hours of IT time plus 20 minutes per owner: roughly 12 hours, or about $800, once.
• Skip the move, and those 43 hours a month come back as manual work on January 1.

Give the number one owner, for the same reason every Copilot Credits meter needs a named owner.

What do IT leaders ask about Copilot scheduled prompts?

IT leaders ask four things first: what stops, whether anything moves on its own, how many tasks a person can have and whether admins can turn the feature off. Here are short, direct answers.

What happens to Copilot scheduled prompts on December 31, 2026?

Power Platform scheduled prompts retire on December 31, 2026 and no longer run after that date. Responses from earlier runs stay in each person's Copilot chat history, so nothing already delivered is lost. Any schedule a person wants to keep must exist as a scheduled task before then.

Do scheduled prompts move to scheduled tasks automatically?

Plan as if they do not. Microsoft Learn says people must create each schedule again as a new scheduled task before December 31, 2026. Check the Scheduled tab for each owner instead of assuming a schedule moved.

How many scheduled tasks can one person have in Copilot?

Up to 10 active schedules and 50 in total per person, according to Microsoft. Pause or delete tasks nobody reads to stay under the limit.

Can admins turn off scheduled tasks in Copilot?

Not with the old control. Microsoft says scheduled tasks are not a connected experience, are not governed by the Allow the use of connected experiences in Office policy and have no separate policy setting. They are available to everyone with a Microsoft 365 Copilot license.

How can 2toLead help?

2toLead helps organizations in healthcare, nonprofit, education, government and professional services turn Copilot features into habits people keep. In our fixed-scope, 90-day Copilot Adoption Accelerator, our Microsoft MVP team will:

• Run the legacy inventory and brief every schedule owner before December 31
• Triage schedules with your teams and rebuild the keepers as scheduled tasks
• Write ground rules for tasks that run unattended, with your compliance lead
• Publish a starter set of scheduled tasks by role and report adoption against a 65% active-use target

For more adoption reading, see the November 2026 Copilot Adoption Newsletter.

Find more practical guidance on the 2toLead Insights hub, or book a Copilot Adoption Accelerator call.

No hype. Just practical, governed AI that actually gets adopted.