PowerApps is licensed on a per-user basis. Each user who accesses the service to create and run apps needs a license. Office 365 and Dynamics 365 customers can immediately benefit from the PowerApps and Microsoft Flow capabilities that these offerings include. Customers who want to build apps and flows that access data sources outside Office 365 and Dynamics 365, or need additional functionality, can purchase standalone subscriptions to PowerApps and Microsoft Flow. There are important differences in functionality between these groups of licenses.
Please see the PowerApps pricing page for the latest pricing information for each PowerApps license. Please see Microsoft Flow pricing page for the latest pricing information for each Microsoft Flow license.
PowerApps capabilities for Office 365 and Dynamics 365 enable users to create and run apps within the context of these services. These apps can also be extended to leverage data in common cloud services including Box.com, Facebook, and many more. Users with access to PowerApps through Office 365 and Dynamics 365 can't create or run apps against Microsoft Common Data Service databases. See the PowerApps pricing page for the list of Office 365 and Dynamics 365 plans that include PowerApps capabilities.
NOTE PowerApps will be added to existing and new Office 365 subscriptions starting later in November 2016.
- If you sign in to PowerApps with an Office 365 subscription prior to this change going out, you will be prompted to sign up for a free PowerApps Plan 2 trial.
- Feel free to sign up for the trial if you want to try out PowerApps until the update is made to your Office 365 subscription.
- However, please be aware that the trial license may include features of PowerApps that are not available to you through your Office 365 subscription when the trial expires after 90 days. See PowerApps pricing to see what capabilities are included in your Office 365 subscription.
Full-featured standalone PowerApps plans provide users the ability to create and run apps across data sources that extend beyond Office 365 and Dynamics 365, such as Salesforce and on-premises data sources, as well as Microsoft’s Common Data Service. These subscriptions also include features not available in Office 365 and Dynamics 365 plans.
PowerApps licenses always include Microsoft Flow capabilities. In addition to being included in PowerApps licenses, Microsoft Flow is also available as a standalone service. See PowerApps pricing page for more information on the specific Microsoft Flow capabilities that each PowerApps license includes.
The per-user licenses above come with included capacity for resources used when an app or flow is executed. These resources include data storage, file storage, and flow runs. The capacities included in the per-user licenses are pooled at the tenant level and, when the tenant’s capacity is exhausted, customers may purchase additional capacity through add-on licenses. See the PowerApps pricing page for the capacity quantities that each PowerApps license includes.
Let’s take a look at an example. ABC Inc. has 1,000 employees, of which 700 employees are licensed with Office 365 Enterprise 3. Early on, a power user creates a line-of-business application that simplifies how customer orders are tracked. Later, the HR department works with IT to roll out an app for reporting time off and absences, and the app is built on the Common Data Service.
ABC Inc. starts by developing an app for its Office 365 licensed users. The app brings together customer and product configuration data stored in Office 365 SharePoint lists with customer-order documents, which they store in Box.com. Because this app only accesses data stored in Office 365 and a common cloud service covered with a standard connector, the Office 365 licenses they already have cover both creation and usage of this app.
Licenses required: The 700 Office 365 Enterprise 3 licenses they already have are sufficient.
Based on how quickly and easily the order-tracking app was launched, ABC’s Human Resources group enlists the help of IT to create a time and absence reporting app that will be rolled out across the entire company. All employees will be required to use this app to report their hours, vacations, and sick days.
For this app, IT selects the Common Data Service as the system in which to store time and absence data. The Common Data Service provides the security and data-policy capabilities that IT requires for information related to employees. They assign two IT employees to the project to create the database and model the time and absence app data in the Common Data Service. These employees are also responsible for tracking app usage and establishing the policy applied to this data.