Rollout Power Automate Desktop to entire company

(1) Share

Report

Posted on by SM-06101152-0

Hi All,

We are preparing to provide Power Automate Desktop to our entire company of more than 55,000 users.
Earlier this year we disabled the ability to create new UiPath's and have a team migrating any existing UiPath RPAs to PAD.

I am wondering if anyone has done this where they also need to look at Charge Back to Business Segments for the License, how many PAD Environments you ended up setting up, how you segmented them, etc.

We plan to have an Intake request app, along with setting up Approvals to Business Segment Leaders and then Admin after they approve.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Michael E. Gernaey 53,362 Super User 2025 Season 2 on at

Like (1)

Report

HI @SM-06101152-0

Are they doing only standard RPA or also Robotic RPA? Since licensing is extra for Robotic RPA versus free RPA (attended).

So logically there isn't a license until you start looking at scenarios with connectors and cloud flow integrations and I am not sure which of those or all you are allowing people to do and also depending on what M365 plan you have, and if people are developers with developer licenses.

Are you looking at using Premium PA licenses? (with or without Robotic RPA?).

Your organization seems very large which is cool :-) but if you do that you need to segment somehow. Even at Microsoft, we had different environments for different segments (sales / F&O etc) so you might want to look into that as then you can track license charge backs by environment which is pretty straight forward.

However once you start allowing things like AI Builder or Copilot etc it becomes confusing a bit again because some things are then included for free in CP licenses.

But either way I would segment by some agreed BUs / Organizations / environments.

Would have to know more to give the best answer possible.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
SM-06101152-0 5 on at

Like (0)

Report

Thank you @Michael E. Gernaey for your reply.

We will have both Attended and Unattended RPAs. Currently all the UiPath's being migrated are Unattended and so they are using our own Hosted Machines.

Those of us on the Planning committee are discussing possibly moving to the Microsoft Hosted Machine license model to reduce workload and internal Hosted machines.
Although each unattended bot is more expensive, we think reducing the workload and hosting our own Hosted Machine might be worth it.

We will be assigning the Power Automate Premium License to users once the Intake form has been approved.
We are going to use Security groups to assign users to the Correct Environment based on the Business Segment.

We also have another wrinkle we have to prepare for and that is SOX compliance RPAs.
Still trying to decide if we will have one SOX Compliance Environment, or one for each of the three Business segments.

One of the main questions that keep coming up is..
Is it better to have One Environment per Business Segment, or should there be further breakups of where RPAs are created?

Was this reply helpful? Yes No
David_MA 12,980 Super User 2025 Season 2 on at

Like (0)

Report

We create separate Power Platform environments for each region and assign regional users accordingly. This helps us forecast Power Platform costs for the coming year. Regional IT budgets cover all IT services and are allocated based on headcount. For example, if a region’s IT budget is $10,000 for 100 employees, the cost per employee is $100 annually. Departments are charged based on their headcount. Corporate-level projects that apply globally are funded through a global IT budget, which is divided by total company headcount and added to each region’s allocation. We're not 55,000 employees, but we're a good size company and this method works.

Currently we us UiPath and don't allow employees to use Power Automate Desktop.

Was this reply helpful? Yes No