Those dates are planning milestones, not a launch announcement. Microsoft’s AI at Work Roadmap explicitly describes its release dates as estimates and says its information is subject to change. The live roadmap page retrieved for this report did not expose the individual entry, so the feature-specific details remain attributable to the roadmap metadata rather than independently confirmed launch documentation.
What direct triggers would change
The proposed change concerns how a desktop flow starts, rather than what its automation steps can do. The roadmap description says supported events will be able to initiate desktop flows without an intermediary cloud flow, with the intended benefit of simplifying automation design and connecting desktop work to business processes.
Microsoft Learn describes desktop flows as Power Automate’s robotic process automation capability. They can automate tasks involving Excel, files, websites, modern desktop applications and legacy software, interacting through application interface elements, images or screen coordinates. In other words, they handle work on the computer—not just exchanges between connected online services.
The potential value is straightforward: where a cloud flow serves only as the bridge between an event and a desktop automation, a direct trigger could remove one component to configure and maintain. That is an architectural implication of the proposal, however—not evidence of faster execution, lower licensing costs or greater reliability.
The roadmap metadata scopes the feature to Power Automate on Desktop, in Worldwide (Standard Multi-Tenant) environments. It does not establish availability in other cloud instances or identify a required Power Automate for desktop version.
Direct event triggers are not scheduled triggers
There is an important distinction behind the similar terminology. Microsoft already documents a separate Scheduled triggers preview that starts desktop flows on a recurring timetable without creating a cloud flow. Its documentation describes managing those schedules in Automation center and selecting a desktop flow and execution connection.
A schedule answers, “When should this run?” The new roadmap item instead describes starting a flow when a supported event occurs. The scheduled-trigger documentation does not establish which events roadmap item 579975 will support, or how its configuration will work.
That existing preview also provides a useful caution against reading “direct” as “dependency-free.” Microsoft’s scheduled triggers still require a published desktop flow, a registered machine or machine group, a connection reference, and the licensing and capacity appropriate to the selected run mode. Those are requirements for the scheduled preview, not confirmed prerequisites for the planned event triggers.
The practical lesson is that removing an intermediary cloud flow does not, by itself, establish that execution infrastructure or licensing requirements disappear.
What makers and administrators still need to know
The roadmap description leaves several implementation questions unanswered:
- Supported events: It does not name event sources or filtering options.
- Execution targeting: It does not explain how a trigger selects a machine or machine group.
- Run modes: It does not establish support for attended or unattended execution.
- Permissions and licensing: It provides no feature-specific requirements.
- Failure handling: It does not describe retries, duplicate-event handling or behavior when an execution target is unavailable.
These are evaluation questions, not announced limitations. They matter because a simpler starting mechanism is useful only if it fits the operational requirements of the automation.
For planning purposes, the sensible approach is to identify flows whose intermediary cloud component does little more than initiate desktop work, then evaluate those candidates once Microsoft publishes the supported events and implementation guidance. There is no basis yet for rebuilding production automations around this roadmap entry.
The takeaway: Power Automate’s planned direct triggers could make some event-driven desktop automations less cumbersome. But “no intermediary cloud flow” is a specific design improvement—not a promise that cloud flows become unnecessary across desktop automation. January and March 2027 are the dates to watch, while the supported event list will determine how much practical work this feature can take off administrators’ plates.