epifive

Posted on Nov 13 Edited on Nov 13 Originally published at epifive.com

Copilot Scheduled Prompts Move Off Power Platform: Migrate Before Dec 31

#ai #powerplatform #lowcode #microsoft

Microsoft is moving scheduled prompts in Microsoft 365 Copilot from Power Platform to native Copilot scheduling, called scheduled tasks. Message Center post MC1550533 (published November 12, 2026) and Microsoft Learn say the Power Platform version retires on December 31, 2026 and stops running after that date. To keep a schedule, recreate it as a new scheduled task in Copilot before then.

This guide is for Copilot users who rely on recurring prompts, and for the admins who support them. It covers what changes, how to find legacy schedules, how to recreate them and what the documentation does not say.

What the scheduled prompts change is

Scheduled prompts let a user run a Copilot request on a timetable, for example a daily brief. Until now the feature ran on Power Platform: Microsoft Learn describes a Power Platform production environment named Microsoft 365 that is created automatically the first time a licensed user uses a recurring Copilot feature.

The new design drops that dependency. Microsoft Learn states: "Scheduled tasks no longer use a Power Platform environment. Scheduled task data is processed and stored within the Microsoft 365 compliance boundary."

According to MC1550533, as summarized on the community mirror mc.merill.net:

Users describe a one-time or recurring task in natural language. Copilot runs it and returns the result to the associated conversation.
Users manage tasks under Tasks > Scheduled in the Microsoft 365 Copilot app.
Users can run, edit, pause, resume or delete a task.
A task that needs approval pauses until the user responds in the associated conversation.
Limits are 10 active and 50 total schedules per user.
For 30 days after the Scheduled tab appears, tasks can be reached from both the old "More options (...)" menu and Tasks > Scheduled. The old entry is then removed.

Microsoft's support article says scheduled prompts are "now called" scheduled tasks and are managed in Task Hub.

Key dates

Date	Event	Source
Nov 11, 2026	Rollout to Frontier/TAP	MC1550533
Nov 30 to Dec 31, 2026	Worldwide rollout	MC1550533
Dec 31, 2026	Power Platform scheduled prompts retire and stop running	MC1550533, Microsoft Learn
Jan 1, 2027	Scheduled tasks no longer appear in the legacy inventory	Microsoft Learn (inventory page)

The Message Center post says rollout timing may change based on reliability and migration readiness. It listed no "updated" date when we opened it. Learn and Message Center agree on December 31, 2026, so there is no date conflict to plan around.

Who it affects and availability

The post says it affects users with a Microsoft 365 Copilot premium license who use scheduled tasks, subject to organizational controls. It covers Microsoft 365 Copilot and Copilot Chat and Tasks in the Microsoft 365 Copilot app, on web and Windows desktop.

Microsoft's support article adds that scheduling works in Copilot Chat and in Microsoft Copilot on the web or desktop, and that Microsoft Teams, Outlook and mobile are not included in this initial release. That differs from the Learn admin page, which still describes legacy prompts as working across Teams, Office.com chat and Outlook. The pages do not reconcile the two, so test where your users actually schedule.

Two groups to watch:

Users who scheduled prompts during the public preview. Learn says these keep running in Power Automate until they expire before December 31, 2026. They do not appear on the Microsoft Copilot scheduled prompts page; manage them in Power Automate.
Consumer Copilot Tasks. A separate support article for personal Microsoft accounts (Microsoft 365 Personal, Family, Premium and Pro) says those Tasks will migrate to Copilot Cowork. That is a different feature and not part of MC1550533.

The documents we opened do not state whether sovereign clouds such as GCC are included. The Message Center post as we read it does not say. Check your tenant's own Message Center entry.

Requirements

A Microsoft Copilot license. Learn: "This feature is available to all users with a Microsoft Copilot license. There is no separate policy setting for this feature."
For the legacy inventory: the Power Platform Administrator role, PowerShell 7.0 or later, and the Az.Accounts and Microsoft.PowerApps.Administration.PowerShell modules.
To see the legacy prompts in the Microsoft 365 environment, the inventory page says you also need the System Administrator role on that environment. It takes about 30 minutes to show up everywhere.
Learn notes scheduled prompts appear only in the Work IQ tab of Microsoft Copilot.

Microsoft advises using roles with the fewest permissions rather than Global Administrator.

How to check whether you're affected

As a user

Open Copilot and look for scheduled prompts you created. If a prompt appears on the scheduled prompts page, it is a legacy Power Platform schedule until you recreate it. Treat any recurring prompt you rely on as at risk. MC1550533 says schedules that will not migrate automatically must be recreated before December 31, 2026; the documents we opened do not list which schedules migrate automatically, so recreate anything important.

As an admin: inventory legacy schedules

Microsoft Learn publishes an inventory process for legacy prompts. Its own warning applies: it covers only Power Platform scheduled prompts, and scheduled tasks "will not appear in this inventory" from January 1, 2027.

Sign in to the Power Platform admin center, select the Microsoft 365 environment (the default name; your tenant might use a different one), select Membership, then select Add me to get the System Administrator role.
Sign in with Connect-AzAccount.
Find the environment with the documented command:

Get-AdminPowerAppEnvironment 'Microsoft 365'

Save the scripts from the Learn inventory page (Get-CopilotActions.ps1 and the removal scripts) in the same folder. We do not reproduce them here; copy them from Microsoft's page.
List all legacy prompts for the tenant, using your own environment ID:

.\Get-CopilotActions.ps1 -EnvironmentId abc123-a100-xyz000-12345

For one user, add -UserId. To export, pipe the output to Export-Csv, as the page shows:

.\Get-CopilotActions.ps1 -EnvironmentId abc123-a100-xyz000-12345 | Export-Csv -Path C:\temp\resultFile.csv

The values above are Microsoft's documented placeholders. The output lists fields such as Name, CreatedOn, Status and CreatedByFullName.

How to migrate your scheduled prompts, step by step

Microsoft's support page describes the creation path for scheduled tasks. Menu names may vary because the page says Home, the new Copilot starting point, is still rolling out.

Recreate a schedule as a user

Go to Copilot Chat and sign in with your Microsoft 365 account.
Use one of the documented methods: hover over a prompt and select Schedule this, choose when and how often it runs, then select Save; create a scheduled task directly in Copilot Chat; or create one from Task Hub.
After a run, the response appears in the Chats section on the left. Scheduled tasks are bolded and have an icon.

Manage tasks

Select the Task icon in the left sidebar header of the Copilot app.
Select the Scheduled tab. Tasks appear under Active or Inactive.
Use Run now (Active tasks only), Edit Schedule, Pause (Active only; the task moves to Inactive) or Delete (deleted tasks do not appear in Inactive).

MC1550533 words the path as Tasks > Scheduled. The two pages describe the same tab differently, so match whichever label you see.

What admins should do

Microsoft's recommended actions in MC1550533 are to:

Notify users who rely on scheduled prompts.
Tell them to recreate schedules that will not migrate.
Tell them Copilot Chat schedule management is moving to Tasks > Scheduled.
Update internal documentation and helpdesk guidance.
Review applicable Microsoft 365 Copilot controls and organizational policies.

If you use the inventory, export the list before the retirement date, contact each owner and give them the retirement date. Deleting legacy prompts with the documented scripts is optional and not required by Microsoft.

Limitations, testing and rollback

Limits: 10 active and 50 total schedules per user (Learn and MC1550533). The support page lists no limits, so use the Learn figure.
Approvals: tasks needing approval pause until the user responds in the conversation.
Unknowns: the documents do not say which legacy schedules migrate automatically, what error a user sees after December 31, or whether every schedule frequency carries over.
Testing: recreate one schedule per user group, run it with Run now, and confirm the response lands in Chats.
Rollback: Microsoft does not document a way to keep Power Platform scheduled prompts past December 31, 2026. During the 30-day overlap, the old menu still reaches tasks.
Rollout timing: worldwide rollout runs November 30 to December 31, which leaves little time. Users in the worldwide group may not see the Scheduled tab until late in that window.

Privacy and admin notes

Scheduled task data is processed and stored within the Microsoft 365 compliance boundary.
MC1550533 states the change alters how existing customer data is processed and that Copilot can run tasks without the user present.
Microsoft says the change does not cause data loss; earlier responses stay in chat history.
Scheduled tasks are not a connected experience and are not controlled by the Allow the use of connected experiences in Office setting. Legacy prompts still are until retirement: setting it to Disabled hides legacy scheduled prompts, though existing ones keep running until their schedule finishes.
There is no separate policy setting for scheduled tasks. If you must block them, review your Copilot license assignment; the documents we opened describe no other control.
For audit and retention of Copilot interactions, see /blog/copilot-interactions-audit-retention-ediscovery. For license planning, see /blog/microsoft-365-copilot-license-assignment-checklist.

What we checked

Opened MC1550533 on mc.merill.net on 2026-11-13: published November 12, 2026, no updated date shown, act-by December 31, 2026, limits of 10 and 50.
Opened the Learn page "Manage Scheduled Prompts for Microsoft Copilot" (updated 2026-11-11): confirmed the December 31, 2026 retirement, the 10 active and 50 total limits and the lack of a separate policy setting.
Cross-checked the retirement date and limits between MC1550533 and the Learn page: both match.
Opened the Learn inventory page (updated 2026-11-11): copied the documented commands and prerequisites and confirmed legacy inventory ends for scheduled tasks on January 1, 2027.
Opened the Learn Power Platform page on the Microsoft 365 environment: confirmed the environment name, the role and the Copilot license requirement.
Opened Microsoft's support pages on scheduling prompts and on consumer Copilot Tasks: quoted the UI labels.
Could not confirm in the Microsoft 365 roadmap and found no Tech Community post for this retirement; labels differ between Message Center and the support page.
Not tested on a live tenant or account; the rollout had not reached every account on 2026-11-13. We did not run the PowerShell.

Last tested: 2026-11-13

Sources

This guide was researched and drafted with AI assistance and checked against the vendor documentation listed in its References. Read the maintained version and related guides on EpiFive.

DEV Community