cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jayesh110283
New Member

SharePoint Designer Workflow to Power Automate rewrite License consideration suggestion

Hi Community,

 

I have to rewrite SharePoint Designer workflows to Power Automate mostly all actions seems use SharePoint related connections so which License I should suggest customer to save the cost we have to redesign 5000 SharePoint designer workflows to Power Automate, how can I save cost for the customer in licesing? please suggest 

1 ACCEPTED SOLUTION

Accepted Solutions
eric-cheng
Solution Sage
Solution Sage

Hi @jayesh110283 ,

 

No simple answer.

 

If your customer has E3 and E5 licensing, Power Automate will be included along with standard connectors.  This will get you through most scenarios involving SharePoint, Excel and business logic e.g. loops, conditions etc.  

 

If your customer's SPD workflows requires additional connectivity e.g. SQL, web service etc, then you will need premium connectors which will require either a per flow or per user license.  It is possible to minimise costs by using service accounts but again, it depends on the scenario.

 

I haven't looked at SPD workflow for a while but from what I recall, the functionality is limited so I think standard connectors should be fine.  If your customer had custom workflows built in Visual Studio/WF or used a third party tool e.g. Nintex/K2, then that would be tricker.  

 

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

Connect on LinkedIn

View solution in original post

1 REPLY 1
eric-cheng
Solution Sage
Solution Sage

Hi @jayesh110283 ,

 

No simple answer.

 

If your customer has E3 and E5 licensing, Power Automate will be included along with standard connectors.  This will get you through most scenarios involving SharePoint, Excel and business logic e.g. loops, conditions etc.  

 

If your customer's SPD workflows requires additional connectivity e.g. SQL, web service etc, then you will need premium connectors which will require either a per flow or per user license.  It is possible to minimise costs by using service accounts but again, it depends on the scenario.

 

I haven't looked at SPD workflow for a while but from what I recall, the functionality is limited so I think standard connectors should be fine.  If your customer had custom workflows built in Visual Studio/WF or used a third party tool e.g. Nintex/K2, then that would be tricker.  

 

--------------------------------------------------------------------------
If I have answered your question, please mark my post as a solution
If you have found my response helpful, please give it a thumbs up

Connect on LinkedIn

View solution in original post

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Welcome Super Users.jpg

Super User Season 2

Congratulations, the new Super User Season 2 for 2021 has started!

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Users online (1,487)