A cloud-based workflow diagram shows users and credentials feeding automated software that connects to email, teams, and databases.
Microsoft has put a Power Automate change on its roadmap that could loosen how shared desktop flows authenticate connectors when a cloud flow triggers them. The roadmap entry is ID 579907. It is listed as "In development" for Power Automate on Desktop, in the General Availability ring, for the Worldwide (Standard Multi-Tenant) cloud. The estimated general availability is March 2027.

Microsoft's own roadmap disclaimer says dates and descriptions are estimates and subject to change. Treat March 2027 as a target, not a promise. Nothing here is available to use today.

A cloud-based workflow diagram shows users and credentials feeding automated software that connects to email, teams, and databases. What Microsoft says is coming​

Microsoft's description says the feature lets you bring your own connections in shared desktop flows that include connector operations and need to run in attended or unattended mode. It says this removes the need for embedded connection references in cloud runs.

That is all the roadmap says. It does not publish any of the following:

  • the user interface or setup steps
  • which connectors will be supported
  • licensing changes
  • whether ownership or sharing rules change

I won't guess at those. The rest of this piece is about the context that makes the change matter.

How it works today​

Desktop flows can use cloud connector actions such as SharePoint, Outlook, Teams and Dataverse. Those actions need connections, and sharing a flow does not share the connections. Microsoft's documentation says a connection is the authenticated link between Power Automate and an external service.

Microsoft's current guidance splits shared access into two roles.

Run-only users

  • Makers with user access on a shared desktop flow must always bring their own connections when they run it.
  • They can only perform attended console initiated runs.
  • Those runs come from the Power Automate for desktop console, not from a cloud flow.

Co-owners

  • A co-owner can embed connection references into the flow. You can only embed or remove references if you own the underlying connection.
  • Embedded references are available to other co-owners only within the scope of the shared flow.
  • That is why embedding is a real access-control decision. It gives co-owners use of your connection's data through that flow.

The current rules for cloud-triggered runs​

To invoke a desktop flow with connector actions from a cloud flow, the flow must use the Power Automate v2 schema. If you are a co-owner, all of its connection references must be marked as embedded.

The embedding steps in the current documentation are:

  1. Select the desktop flow in Power Automate, then select Details.
  2. In the Connection references section, select Manage.
  3. Set Embedded in desktop flow to Yes for each reference.
  4. Confirm your selection.

There is also a known limitation. When you import a desktop flow with embedded references through a solution, the required references are not included automatically. You must add them to the solution alongside the flow.

For console runs, there is already a bring-your-own-connection model. Co-owners bring their own connection for references that are not embedded. Run-only users bring their own even when the references are embedded. The documentation also describes a suppressed prompt. When there is only one valid connection per connector, or several that map to the same email account, the prompt does not appear.

The roadmap item appears to extend this bring-your-own-connection idea from console runs to cloud-triggered attended and unattended runs. That is my reading of the roadmap text and the documentation, not something Microsoft has spelled out.

Why embedding is a pain point​

Embedding solves a real problem, but it also creates three trade-offs.

  • Access: Embedding hands co-owners the use of a connection through the flow. Microsoft's January 2025 message center post (MC958691) warned that, without preparation, sharing flows with embedded references may expose data, since co-owners could reach sensitive information or connections they should not have.
  • Ownership: Only the connection's owner can remove an embedded reference. If that person leaves or changes roles, the flow can become awkward to maintain. This follows from the ownership rule, though Microsoft does not describe it as a problem.
  • Deployment: The solution-import limitation above means embedded references can break promotion between environments unless you plan for it.

If the roadmap feature works as described, it could reduce reliance on embedding for cloud runs. Whether it fully replaces embedding, or only gives you another option, is not stated. Do not assume embedding goes away.

Don't confuse the two kinds of connection​

Two different connections are involved in a cloud-triggered desktop run, and the roadmap concerns only one of them.

  1. Connector connections are used by actions inside the desktop flow, such as SharePoint or Outlook. These are what "bring your own connection" refers to.
  2. The desktop flow connection links the cloud flow to a machine or machine group. It is set up separately.

The machine-side requirements are documented separately. Microsoft's trigger documentation lists these prerequisites:

  • a registered machine or machine group
  • a work or school account
  • a configured desktop flow connection
  • a license, which for attended runs is the appropriate license and for unattended runs is an unattended add-on

For unattended runs, Microsoft's documentation adds several constraints:

  • Power Automate signs in to the machine with the selected desktop flow connection, runs the flow, then signs out.
  • Unattended runs need a machine with all users signed out. Locked sessions block them, and logging in mid-run is unsupported.
  • The documentation also says unattended runs can't run with elevated privileges.
  • The "Connect with sign-in" connection method works only for attended runs. Using it for unattended runs fails.

The roadmap does not say any of these change. Bring-your-own-connection for connectors would not, on the evidence available, alter machine credentials or the unattended session rules.

What admins should do now​

  • Inventory your shared desktop flows that contain connector actions and run from cloud flows. Those are the ones relying on embedded references.
  • Review who owns the underlying connections. Service-style ownership is easier to govern than personal accounts, though that is general practice and not a Microsoft requirement here.
  • Plan for the unknowns. Wait for Microsoft's documentation before redesigning anything. In particular, wait for answers on how users will supply connections at cloud run time and whether run-only users can trigger cloud runs.
  • Keep to the current rules until then. Use the v2 schema, embed references for co-owned shared flows, and include connection references in solutions when you move flows between environments.
  • Watch for a message center post or an updated roadmap entry. Microsoft typically publishes one as a change approaches.

Bottom line​

This is a modest but useful roadmap item for teams that run shared desktop automation from the cloud. It targets a real friction point: today's cloud-run path depends on embedded connection references that tie access to whoever owns the connection. The details that decide its value are still unannounced, including the experience, permissions model and supported scenarios. Until Microsoft publishes them, the March 2027 date is a target and the feature is a plan.

 

References

  1. Power Automate: Bring Your Own Connection in attended/unattended cloud triggered runs Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Cloud Connectors in Power Automate for desktop - Power Automate | Microsoft Learn learn.microsoft.com
  3. Share desktop flows that contain connector actions - Power Automate | Microsoft Learn learn.microsoft.com