Power Automate flows: Licensing, Ownership, and API Limits
ฝัง
- เผยแพร่เมื่อ 19 มิ.ย. 2024
- In this Power Automate tutorial, we will explore key aspects of Power Automate cloud flows that every user (Beginner or Advanced) must be aware of. We'll explore the three types of cloud flows and how connector classification (standard vs. premium) is tied to licensing. Understand the different Power Automate licensing options: Power Automate Premium per User and Power Automate Process licenses. I'll guide you on how to determine if your flow is premium and how to identify the license you have along with its capabilities.
Learn about the critical role of flow ownership in driving license needs for your flow and explore Power Platform API request limits. Additionally, I'll show you how to change the primary owner of a cloud flow and the benefits of having Service Principal ownership for a cloud flow.
Join me to uncover these important details and much more.
Change the owner of a cloud flow
learn.microsoft.com/power-aut...
Power Automate licenses & Understanding Power Platform Requests
learn.microsoft.com/power-pla...
learn.microsoft.com/power-aut...
Power Platform Connectors
learn.microsoft.com/connector...
Requests limits and allocations
learn.microsoft.com/power-pla...
#powerautomate #microsoft #powerplatform #licensing
0:00 Must know about Power Automate cloud flows
0:29 What is Power Automate & cloud flow types
1:53 Power Automate Connectors
2:44 How to check if my flow needs a premium license?
3:06 How do I check my own license?
3:33 Power Automate license options
4:08 Importance of Power Automate flow primary owner
4:45 When to change Power Automate flow primary owner?
6:04 Power Platform Request Limits
8:02 How to change Primary Owner of Power Automate flow?
10:24 How does licensing and API limits work for Instant flows?
11:23 Advantages of Service Principal Owned cloud flows
12:33 Use Power Apps premium license for flows by associating apps and flows - วิทยาศาสตร์และเทคโนโลยี
![CAMPปลิ้น | EP.76[2/2] เดินมาสิบกว่าป่า วันนี้รู้แล้วว่าโจโฉกลัวอะไร!](http://i.ytimg.com/vi/R7Yor-t2Au0/mqdefault.jpg)
![เก่งแต่ลับหลัง (FINSTA) - ส้ม มารี (Zom Marie) Ft. Punch 4EVE [Official MV]](http://i.ytimg.com/vi/OOolBU2aC70/mqdefault.jpg)
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
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
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!
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.
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!
This video is incredibly insightful and well-made! The explanations are clear, and the visuals are engaging. Great job!
Thank you very much!
Thank you for this video
My pleasure
This was well explained! Thank you!
Most welcome
Very insightful, as ususal!
Thank you very much, Reza!
Most welcome
Very clear video Reza, thank you.
You are very welcome
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.
Many Thanks Reza. Article is good on Power Platform resources with respect to licensing. Awesome
Most welcome
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.
Hi, Thank you for this video
Welcome
You are one YT greatest content creators- thank you!
Wow! Thanks so much
Great video and thanks for sharing this info, Reza.
My pleasure!
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.
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.
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
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
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.
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.
Where can i see the request counter? Great video!
Analytics option in flow. Video description has links to documentation that has the details.
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
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.
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
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
I would like to prepare some sort of forms to be accessed also by organization's guest. Is it possible?
Forms in flow?
Is there a way to convert .xls to .xlsx file through Power Automate?
I have not tried that hence not sure
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.
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
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.
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.