Navigating the world of software licensing can sometimes feel like deciphering a secret code, and Power Apps is no exception. If you've found yourself wondering about the 'Power Apps per user license' and what it really means for you or your team, you're definitely not alone. Let's break it down in a way that feels less like a legal document and more like a friendly chat.
At its heart, a Power Apps per user license is designed to give a single user the ability to run and use Power Apps. Think of it as a personal key that unlocks the door to building and using applications within the Power Platform. This license typically grants access to a broad range of capabilities, including the ability to build and run apps that might use premium connectors or features.
One common question that pops up is about using this license with Power Automate. The good news is, yes, you can! However, there's a small but important caveat: it's generally valid for flows that are triggered by a Power App. So, if your app kicks off an automation, your per user license covers that. It's not a free pass for every single Power Automate flow out there, but it’s a handy integration for app-centric workflows.
What about those times when a trial license expires? It can be a bit confusing when you can still access an app even after the trial period is officially over. This often happens for a couple of hours due to how the system recognizes access, and sometimes a quick refresh of the app is needed for the revocation to fully take effect. It’s a little bit of system caching at play.
Now, let's touch on 'premium' features. You might have an app that uses connectors like SQL Server, and you're wondering why you can still access it with what seems like a standard Office-seeded license. This is often a result of what's called 'grandfathering.' Back in 2019, Microsoft made some changes to how certain connectors were classified. For a transition period, apps that were already using these reclassified connectors were allowed to continue without requiring a premium license, extending until October 1, 2024. So, if your app falls into this category, it's essentially exempt for now.
Even if you've removed all premium connectors from an app, you might still see it flagged as 'premium.' This usually means you need to publish the app again after making those changes for the designation to update correctly. Similarly, if your app is part of that 2019 grandfathering, it's expected to continue showing a premium designation, but end-users can still access it with their existing Office-seeded licenses.
For those using Dynamics licenses, you might encounter prompts for trial licenses when opening apps in a browser. This is because different Dynamics licenses have varying Power Apps usage rights. It's always a good idea to consult the Power Platform licensing guide to understand your specific Dynamics license. Generally, Dynamics licenses with Power Apps rights allow users to run apps without premium capabilities, whether embedded or standalone. However, if your license has 'limited use rights' for Power Apps, you might only be able to use premium canvas apps when they're embedded within model-driven apps in a supported way.
So, what makes an app require a premium license in the first place? Common culprits include premium connectors, Dataverse entities, on-premises data gateways, and custom APIs. Makers can check the 'App Details' page in the maker portal to see their app's license designation. If your app does require premium licensing, end-users will need an appropriate entitlement to access it.
Interestingly, you don't actually need a license to build canvas apps. However, building model-driven apps does require a license.
When it comes to Power Automate flows associated with Power Apps or Dynamics 365, the licensing can get a bit nuanced. If a flow is automated and tied to an app, the owner needs a Power Apps Premium or Dynamics 365 license. For instant flows, every user running it needs that premium license. And if a parent flow calls a child flow, the child flow often inherits the parent's license context, especially if it uses premium connectors and doesn't have its own Process license.
If you're working on a proof of concept and need more time, Microsoft recommends using a developer environment. These environments don't expire, offering a stable space for experimentation. While trial licenses do have expiration dates and can only be renewed a few times, developer environments are the way to go for longer-term testing.
Ultimately, understanding Power Apps licensing, especially the per user license, is about ensuring everyone has the right access to build, run, and automate effectively. It’s a system designed to be flexible, but a little clarity goes a long way in making sure your apps and workflows run smoothly.
