Microsoft has removed a feature from its Microsoft 365 Roadmap that would have let users schedule recurring prompts for declarative Copilot agents. The change, recorded on July 6, 2026, cancels roadmap item 531759 and dashes hopes for a more autonomous AI assistant in the Microsoft 365 suite.
This cancellation affects users of the new declarative agent type in Microsoft 365 Copilot, which includes the Analyst agent and other role-based agents designed to handle specific business tasks. With scheduled prompting, users could have automated routine queries like “Summarize yesterday’s sales” or “Generate a weekly report,” allowing the Copilot to run these tasks without manual initiation.
What Microsoft Actually Removed
The Microsoft 365 Roadmap is a publicly accessible feed where the company lists features it is actively developing, rolling out, or has cancelled. Item 531759 was titled “Copilot: Recurring prompts for declarative agents” and described the ability to set prompts to run on a schedule. The exact cadence options—daily, hourly, or custom—were never detailed, nor was the underlying mechanism: whether prompts would run in the background or require an active session.
On July 6, the roadmap entry was updated to “Cancelled,” meaning Microsoft will not deliver this feature. No accompanying blog post or message center notification explained the rationale. For a feature that would have significantly expanded Copilot’s utility, the quiet removal has left many administrators and power users puzzled.
Declarative agents, which this feature targeted, represent a shift in how Copilot interacts with business data. Unlike the general chat-based Copilot, declarative agents are tailored to specific domains—financial analysis, project management, retail operations—and respond to natural-language prompts by connecting to relevant data sources. Scheduling these prompts could have turned Copilot into a proactive assistant, delivering insights on a fixed timetable.
What This Means for You
The impact depends on your role:
For Business Users and Power Users
If you rely on Copilot for daily reports or have experimented with the Analyst agent to query business metrics, the cancellation means you will continue to trigger prompts manually. The dream of a “set it and forget it” report—where Copilot drops a summary into your inbox every morning—is dead for now. You’ll need to open the Copilot panel, type or recite your prompt, and wait for the response each time.
For IT Administrators and Governance Teams
The removal complicates plans to roll out automated Copilot-based reporting across teams. Many admins anticipated using recurring prompts to standardize daily status updates or compliance checks. Without this feature, they must either accept manual workflows or turn to third-party automation platforms like Power Automate, which can call Microsoft Graph APIs but cannot directly trigger Copilot’s natural-language reasoning on a schedule.
For Developers and ISVs
Declarative agents are part of the broader Copilot extensibility platform, and the ability to schedule agent prompts could have opened new scenarios for integrated line-of-business applications. Its cancellation suggests Microsoft may not be prioritizing agentic automation in this manner. Developers building on the Copilot stack should watch for alternative scheduling capabilities within the Power Platform or Azure AI.
How We Got Here
Copilot’s evolution has been rapid. Microsoft introduced declarative agents at its Build conference in 2025, positioning them as a low-code way to create domain-specific AI assistants. The Analyst agent, for instance, allows users to ask natural-language questions about their Excel data, Power BI dashboards, or even SQL databases—and get interpreted results. Recurring prompts were a logical next step: why ask the same question every Monday morning when the assistant can just do it?
The roadmap item appeared in early 2026, generating excitement among early adopters. But the feature remained in “development” status for several months, with no preview releases or detailed documentation. Its abrupt cancellation aligns with a pattern of Microsoft pruning its roadmap: the company often reassesses priorities, especially in fast-moving areas like AI. Still, the lack of an official explanation fuels speculation that the feature may have been technically more complex than anticipated, or that it duplicated existing capabilities in other tools.
One plausible reason: Microsoft may want to funnel scheduled automation through Power Automate rather than embedding it directly into Copilot. Power Automate already offers robust scheduling and trigger mechanisms and can connect to many of the same data sources. However, Power Automate lacks the natural-language reasoning that makes declarative agents so appealing—you set up rigid flows, not colloquial queries.
What to Do Now
If you were counting on Copilot recurring prompts, you have several paths forward:
Evaluate Power Automate Workflows
Microsoft’s Power Automate can replicate parts of the scheduled prompt idea, though it requires more configuration. You can design a flow that runs on a schedule, queries data (e.g., from Excel, SharePoint, or an API), and emails a summary. The output won’t be as conversational as a Copilot-generated response, but it can fill the gap for basic report delivery.
Continue Manual Prompting—for Now
For ad hoc needs, manual prompting in Copilot still works. Train yourself and your team to use consistent, well-crafted prompts to speed up repetitive tasks. Keyboard shortcuts and pinned prompts can slightly reduce the friction.
Provide Feedback to Microsoft
Use the Microsoft Feedback Portal or your organization’s Microsoft 365 admin center to record your disappointment and explain your use case. Microsoft sometimes restores cancelled features based on customer demand. Mention roadmap item 531759 specifically so product teams know what you’re referencing.
Monitor Third-Party Solutions
Third-party vendors may step in to offer Copilot scheduling add-ins or services that bridge the gap. Keep an eye on apps in the Microsoft Teams store or independent automation tools that integrate with Copilot’s APIs, if and when those become available.
For IT Admins: Revisit Your Automation Strategy
If you had built a deployment timeline around Copilot recurring prompts, it’s time to pivot. Consider a hybrid approach: keep manual Copilot sessions for high-value analysis while using Power Automate for routine data pulls. Engage with Microsoft’s FastTrack or your account team to communicate your needs.
Outlook: Will Scheduled Prompts Ever Return?
Don’t write this feature off entirely. Microsoft frequently cycles through ideas: a feature that gets cancelled today may reappear as part of a larger reboot months later. The company recently announced deeper integration between Copilot and Power Automate, hinting that automation is front of mind. It’s conceivable that scheduled prompts will emerge not as a standalone Copilot feature but as a template within Power Automate that leverages declarative agents under the hood.
Near-term, watch for announcements at Microsoft’s autumn Ignite conference, where the AI roadmap often solidifies. In the meantime, the cancellation is a reminder that even the most promising roadmap items can vanish with a single status update. Staying adaptable and exploring multiple automation avenues remains the best strategy for any organization betting on Microsoft’s AI ecosystem.