Fantastic video Reza! This information represents 90% of the questions and support cases I get related to ownership and licensing of flows 😅 On the benefits of solution cloud flows defined in Dataverse, you missed a chance to promote your recent video on another Dataverse-specific capability for flows: Drafts and Versioning 🙂
Well done Reza! Rock solid information. One interesting aspect of this to me which isn't well documented is the amount of time it may take before a flow begins executing after the trigger condition. E.g. When a SharePoint list item is modified. If the flow is owned by a user with a Premium License, then the flow will begin to execute within a shorter period of time. I don't believe there is a precise documentation on the time window, but there is a clear difference if you do a comparison between non-premium license and premium license.
Very clear explanation of a complicated subject! The Change Ownership / non Solution Flow foxed me for some time. Many thanks for sharing your knowledge
Super informative Reza! Always thankful for providing us with all these resources much appreciated. Any plan to Demonstrate/show us how to build the ¨ Change the PIMARY owner of a flow¨? If we are considering moving all flows to solutions and changing ownership to SPN with so many flows created with different accounts it would be cool to see how to change the ownership in bulk using flows. Thanks!
Thanks - very helpful video. I hope at some point Admins can see if the Flow is Standard or Premium e.g. from CoE, so it will help assign Premium licenses effectively
Great breakdown of licensing in Power Automate flows, Reza! Understanding the nuances of licensing can be daunting, but your video makes it clear and concise. Thanks for sharing this valuable information with the community! Regarding your mention at the end of the video about flows running under the Power Apps license, could you please elaborate on what that entails?
Glad it was helpful! Power Apps license grants use rights for power automate (in context flows). If you associate a power app to a flow, then the app license will cover the flow. There are some requirements for it. Video description has link to the detailed documentation.
Very good video, however I wish you talked more about the license because there is a LOT of things that could change the limit. For example the Transition Period. I would love to know more about that, like how it changes the limit, if you are in that period do you run flows as per your plan or not, etc.
Hello Reza, Thanks for the fantastic video! I have a query. Does polling trigger also counted for API limits. Ex- I have a trigger - When an item is created in SharePoint list with frequency - 1 minute. Does every minute polling will be counted against API limits? Thanks in advance!!
Hello Raza.. As usual excellent video and information.. 😊 I have a query regarding ownership transfer. I would like to transform ownership of my flow to other account, but in thay flows i have some email automation too that still sending emails from my account, how change that From email id to while transferring owner.. Please guide...... Thank in advance..
Thank you so much for this, very useful, one more thing, does Microsoft alert once an account hits maximum request limits on allowed flows within the 24hrs?
@@RezaDorrani This does not make me want to use premium connectors. I use ALM, and therefore the owner of all my flows in PROD is an SPN account. A per-flow license is $100, with the minimum package being 5 licenses.
@@anthonyleduc There is a process license that allows you to tie it with a business process. Includes multiple flows. Check licensing page for Power Automate
I make videos when I receive multiple requests on a topic. Every 6 months I ask subscribers for topic suggestions on Community Tab of my channel. Most voted idea gets added to my backlog. Make sure to post this idea whenever I post the next topic suggestion post.
Excellent video @Reza. Can't thank you enough. Can you share custom connectors with Service Principal? I assume custom connectors require premium license much like http connector?
Hi Reza, my question is more on power apps. If we are all have an o365 E3 in our tenancy, can we still access to a power app from an external tenancy if we are granted access? or do we need another license particular to that external tenancy?
Case 1: Power Apps triggered Instant Flow "Associated" with an App Case 2: Power Apps triggered Instant Flow "Not Associated" with an App. In both the cases the flow will be triggered under the triggering user context, association is just to pair(App and Flow) from the relation point of view , it does not bend/skew/provide advantage from licensing perspective, this is my understanding, any correction to this? #SPN is going to be my next best friend in some scenarios (only some). Thank you!
Not sure to understand SPN licensing. I have some critical flows for the organization, no premium connectors. I do not want to have users to be owners of the flows as they might leave the company. I would like to use deployment pipelines and solutions. I do not share these flows with many people. Do I need process license for each flow (i have around 20) and each workspace Dev/Uat/Prod? Or maybe if the owners of the SP have premium per user licences is enough? Thank you for your reply
Separate tool. Free only for windows 10 or 11 users and that too only manually triggered and attended automations. You would need the premium license to utilize its full capabilities.
It is interesting video. I would need more information what type of licenses is required for Queue based process running of 2 machines and how to assign licenses in this scenario.
A very informative video, Reza - thank you. The API limits are another good reason to use batch updates in flows rather than loop through every single record in turn.
Hey Reza, Thank you very much for this very useful video, as usual ;-) It is a coincidence that on my side I've just tried to run a flow few days ago with a Service Principal account I've created in Azure as it is a good solution (maybe the only one?) not to be user dependant. Very quickly I've succeded to run a flow with this Service Principal account to a Dataverse connector, but I could do it with a SharePoint connector (not able to connect the Service Principal acccount maybe due to access limitations?). Do you know if there are some limitations with the Service Principal account as owner of the flow ?
@@RezaDorrani, if the user leaves the company, the SPN, as owner of the flow, can continue using the users connections in the flow without erroring out?
Fantastic video Reza! This information represents 90% of the questions and support cases I get related to ownership and licensing of flows 😅
On the benefits of solution cloud flows defined in Dataverse, you missed a chance to promote your recent video on another Dataverse-specific capability for flows: Drafts and Versioning 🙂
Thanks so much Chris!
I definitely missed that :(
Drafts and flows is my favorite
Wow! Reza came just on time when I was really confused with the plan of Power Automate and the API Call limit.
Could not thanks more.
Thanks
Glad it helped!
This video is incredibly insightful and well-made! The explanations are clear, and the visuals are engaging. Great job!
Thank you very much!
Well done Reza! Rock solid information. One interesting aspect of this to me which isn't well documented is the amount of time it may take before a flow begins executing after the trigger condition. E.g. When a SharePoint list item is modified. If the flow is owned by a user with a Premium License, then the flow will begin to execute within a shorter period of time. I don't believe there is a precise documentation on the time window, but there is a clear difference if you do a comparison between non-premium license and premium license.
I am not aware of any documentation on this or if there is a time limit in play to trigger based on license
Very useful and informative especially the account under with the flow run and changing ownership with the solution context. Thanks for sharing
Great to hear!
Very clear explanation of a complicated subject! The Change Ownership / non Solution Flow foxed me for some time. Many thanks for sharing your knowledge
You’re most welcome
Very insightful, as ususal!
Thank you very much, Reza!
Most welcome
Many Thanks Reza. Article is good on Power Platform resources with respect to licensing. Awesome
Most welcome
Super informative Reza! Always thankful for providing us with all these resources much appreciated.
Any plan to Demonstrate/show us how to build the ¨ Change the PIMARY owner of a flow¨? If we are considering moving all flows to solutions and changing ownership to SPN with so many flows created with different accounts it would be cool to see how to change the ownership in bulk using flows.
Thanks!
Most welcome!
No plans to demonstrate that (was done for a customer)
I remember using Power Platform APIs to manage it.
You are one YT greatest content creators- thank you!
Wow! Thanks so much
Thanks - very helpful video. I hope at some point Admins can see if the Flow is Standard or Premium e.g. from CoE, so it will help assign Premium licenses effectively
CoE does have a premium flag from what I remember. Check documentation on coe.
Great breakdown of licensing in Power Automate flows, Reza! Understanding the nuances of licensing can be daunting, but your video makes it clear and concise. Thanks for sharing this valuable information with the community! Regarding your mention at the end of the video about flows running under the Power Apps license, could you please elaborate on what that entails?
Glad it was helpful!
Power Apps license grants use rights for power automate (in context flows). If you associate a power app to a flow, then the app license will cover the flow. There are some requirements for it. Video description has link to the detailed documentation.
Great video and thanks for sharing this info, Reza.
My pleasure!
Very good video, however I wish you talked more about the license because there is a LOT of things that could change the limit. For example the Transition Period. I would love to know more about that, like how it changes the limit, if you are in that period do you run flows as per your plan or not, etc.
Transition period is a transition. I want this video to stand the test of time :)
I have shared links to detailed documentation in video description
Hi, Thank you for this video
Welcome
Very clear video Reza, thank you.
You are very welcome
Hello Reza, Thanks for the fantastic video!
I have a query.
Does polling trigger also counted for API limits.
Ex- I have a trigger - When an item is created in SharePoint list with frequency - 1 minute.
Does every minute polling will be counted against API limits?
Thanks in advance!!
Most welcome!
I am not sure about that. My guess is Yes but please check the documentation.
Where can i see the request counter? Great video!
Analytics option in flow. Video description has links to documentation that has the details.
Hello Raza.. As usual excellent video and information.. 😊
I have a query regarding ownership transfer. I would like to transform ownership of my flow to other account, but in thay flows i have some email automation too that still sending emails from my account, how change that From email id to while transferring owner.. Please guide...... Thank in advance..
You would need to change the connection references in the solution to point to connection of new account under which you want email to be sent.
@@RezaDorrani Great... Thanks a lot.. ☺
Thank you so much for this, very useful, one more thing, does Microsoft alert once an account hits maximum request limits on allowed flows within the 24hrs?
I believe if you are exceeding limits the flow owners are now getting an email warning
Thanks Reza, great video. Quick question, are the API limits per user per flow in 24 hrs or just per user for all flows owned by the user in 24 hrs?
All flows (automated and scheduled) owned by the user and run by the user (manually triggered) in 24 hours
Can you please explain Powerapps licensing, especially the licensing relationship between powerapps and power automate?
Dataverse requires premium license when used in apps or flows
As i understand if the owner of the flow is a SP, you must purchase per-flow licence
Yes if using premium features or require higher API limits
@@RezaDorrani This does not make me want to use premium connectors. I use ALM, and therefore the owner of all my flows in PROD is an SPN account. A per-flow license is $100, with the minimum package being 5 licenses.
@@anthonyleduc There is a process license that allows you to tie it with a business process. Includes multiple flows. Check licensing page for Power Automate
Need a video on new Coauthoring in power apps
I make videos when I receive multiple requests on a topic. Every 6 months I ask subscribers for topic suggestions on Community Tab of my channel. Most voted idea gets added to my backlog. Make sure to post this idea whenever I post the next topic suggestion post.
Thanks! Where we can find info about daily consumption API call related to an account? :)
Video description has all the links
Excellent video @Reza. Can't thank you enough. Can you share custom connectors with Service Principal? I assume custom connectors require premium license much like http connector?
Custom connectors are premium.
I believe the connection can be shared with SPN.
Thank you for this video
My pleasure
Hi Reza, my question is more on power apps. If we are all have an o365 E3 in our tenancy, can we still access to a power app from an external tenancy if we are granted access? or do we need another license particular to that external tenancy?
As far as I know, if that power app uses standard connectors then yes.
@@RezaDorranithanks Reza! so we dont need another license in the external tenancy.
@@shredernie should not. Best to test with 1 user and confirm.
if we make the Service Application as Primary owner how the Licensing affect ? not sure if we can assign any license to it.
You can assign process license to the flow if flow is using premium connectors
Case 1: Power Apps triggered Instant Flow "Associated" with an App
Case 2: Power Apps triggered Instant Flow "Not Associated" with an App.
In both the cases the flow will be triggered under the triggering user context, association is just to pair(App and Flow) from the relation point of view , it does not bend/skew/provide advantage from licensing perspective, this is my understanding, any correction to this?
#SPN is going to be my next best friend in some scenarios (only some). Thank you!
Power apps triggered flows always run in user context.
Is it possible in power automate, to create prod,UAT and Dev environment if its license is Power automate for 365 only?
Possible but to create environments you need capacity at tenant level. Min 1GB needed.
@@RezaDorrani thank you.
@@RezaDorrani can you please guide ,where we can check the capacity
@@musicmania9837 check documentation on how to check capacity for tenant for power platform. It is in admin center.
@@RezaDorrani sure,Thank you so much .
Will it be able to export flow as a unmaged flow with power automate 365 license ?
Possible
@@RezaDorrani also managed too?
@@musicmania9837 Yes
Always best to try it out and check
@@RezaDorrani Thank you.
Not sure to understand SPN licensing. I have some critical flows for the organization, no premium connectors. I do not want to have users to be owners of the flows as they might leave the company. I would like to use deployment pipelines and solutions. I do not share these flows with many people. Do I need process license for each flow (i have around 20) and each workspace Dev/Uat/Prod? Or maybe if the owners of the SP have premium per user licences is enough? Thank you for your reply
A process license is recommended for SPN owned flows. You cannot assign a user license to an SPN.
@@RezaDorrani is the process license mandatory if the flows are NOT using premium ?
@@alexandrubadiu2355 No but the API limits for all flows combined that have SPN ownership is only 25k
Can SPNs only associated with one flow?
@@rowenaravelopeacock1619 You can associate as many
Is power automate desktop a separate tool and is it free ?
Separate tool.
Free only for windows 10 or 11 users and that too only manually triggered and attended automations.
You would need the premium license to utilize its full capabilities.
Incredible video, very well explained and understandable. Congratulations! It would be great another one like it but of Power Apps 🙏🙏
Thanks so much!
Would love to do one on Power Apps as well.
Let’s see how well this video is received.
Well explained. I always refer your channel for understanding licensing model
Most welcome
Is every action considered an API call? e.g. Compose action where the API call in it?
Yes.
Thank you so much Reza for the explanation. One question do the SPNs need to have license assigned when adding as a primary owner to premium flows?
Most welcome!
SPN cannot get a license as its a non-interactive user but since flow is premium you would need to license it with process license.
It is interesting video. I would need more information what type of licenses is required for Queue based process running of 2 machines and how to assign licenses in this scenario.
PAD is not an area I am well versed with
A very informative video, Reza - thank you.
The API limits are another good reason to use batch updates in flows rather than loop through every single record in turn.
Most welcome!
Batch for the win.
This was well explained! Thank you!
Most welcome
Is there a way to convert .xls to .xlsx file through Power Automate?
I have not tried that hence not sure
Isn't Power Automate entirely a RPA tool? Why are you only calling desktop flows as RPA. Doesn't the cloud flows fall under RPA as well
No. DPA is cloud flows. RPA is desktop flows.
I would like to prepare some sort of forms to be accessed also by organization's guest. Is it possible?
Forms in flow?
Hey Reza, Thank you very much for this very useful video, as usual ;-) It is a coincidence that on my side I've just tried to run a flow few days ago with a Service Principal account I've created in Azure as it is a good solution (maybe the only one?) not to be user dependant. Very quickly I've succeded to run a flow with this Service Principal account to a Dataverse connector, but I could do it with a SharePoint connector (not able to connect the Service Principal acccount maybe due to access limitations?). Do you know if there are some limitations with the Service Principal account as owner of the flow ?
SharePoint connector does not support SPN. What you are doing is setting connections via SPN. What I show in video is the flow owner being the SPN.
@@RezaDorrani, if the user leaves the company, the SPN, as owner of the flow, can continue using the users connections in the flow without erroring out?
@@alexandrubadiu2355 No it cannot as the connection is not working.
For connections, you can use a service account.