Power Platform Community Forum Thread Details

Hello Community,

I would appreciate your guidance on a Power Automate licensing and architecture scenario related to unattended automation.

We recently acquired a Power Automate Process license with the intention of moving to a more robust unattended execution model.

At the moment, we have an existing solution composed of Power Automate Desktop flows and cloud flows, but these were originally created under a user account associated with a Power Automate Premium license. Because of that, the current model is still tied to a specific user identity and does not feel like the cleanest or most supportable foundation for long-term unattended execution.

I am trying to confirm the best-practice approach before moving forward.

Current scenario

Existing desktop and cloud flows were built under a Premium user account

The customer has now purchased a Power Automate Process license

The target model is to support unattended automation

There is some uncertainty around the correct relationship between:
- the new Process license
- the environment capabilities required for unattended automation
- the account used to own/manage the flows
- the machine or machine group setup
- and the migration path from the current Premium-based configuration

Main question

Would it be considered a best practice to build a new unattended setup from scratch, instead of trying to retrofit the current one?

More specifically, I am considering an approach like this:

Create or designate a new environment intended specifically for the unattended automation model

Make sure the environment has the correct unattended capabilities/capacity required for this setup

Create a new dedicated account/service account for managing the automation in a cleaner way

Associate the new model properly with the newly acquired Power Automate Process license

Rebuild or rebind the desktop flows and cloud flows under this new unattended structure

Validate that the environment, account, machine configuration, and unattended licensing model are all aligned with each other, so there is no mismatch between a Premium-user-based setup and the new unattended Process-license-based setup

What I would like to confirm from the community

I would really appreciate feedback on the following points:

Is it necessary or strongly recommended to use a new environment for this kind of unattended migration?

Does the environment itself need to be explicitly enabled or prepared for unattended capabilities, or is the key dependency mainly at the license/capacity level?

Is it a better practice to use a new dedicated account rather than continuing with the original Premium user account that created the flows?

For flows originally created under a Premium account, is it generally cleaner to:
- reassign ownership and connections, or
- rebuild them under the new unattended model?

When implementing a Power Automate Process license, what is the recommended sequence across:
- environment
- unattended capability/capacity
- machine or machine group
- account ownership
- desktop flow setup
- cloud flow setup

Have others seen issues caused by mixing:
- old Premium-based flow ownership
- new unattended Process licensing
- and environment-level configuration that may not be fully aligned?

My current thinking

My current assumption is that the cleanest approach may be to create a new unattended-aligned model end to end, where:

the license model is unattended,

the environment setup is aligned to unattended execution,

the account strategy is also aligned to unattended execution,

and the flows are migrated or rebuilt so that all pieces match consistently.

In other words, instead of carrying over potential mismatches from the Premium-user-based model, I am wondering whether it is better to create a cleaner “unattended-to-unattended” structure from the start.

Additional note

My main expertise is more on the D365 functional side, so I have been organizing this analysis based on Microsoft documentation, supporting references, and structured research in order to understand the Power Automate unattended model correctly before implementing it.

If anyone has already gone through a similar migration from a Premium user-based setup to a Process license unattended setup, I would greatly appreciate your recommendations, lessons learned, and any best-practice guidance.

Thank you in advance.

Power Automate Pr...

Categories:

Building flows

Power Automate Desktop

General topics

Using flows

For an unattended model using the Process license, I believe the cleaner approach is to set up a new environment and a new service account. Maybe trying to retrofit the old Premium‑user setup will cause mismatches later.
I think the best practice is:

Create a dedicated environment for unattended automation
Use a dedicated service account.
Attach the Process license to that account
Configure machines/machine groups under this new setup
Rebuild or reassign flows so everything is owned by the unattended account

I believe this keeps the license, environment, machines, and flow ownership aligned, and maybe avoids the problems people see when mixing old Premium‑based flows with new unattended licensing.