This is the Trace Id: 7257cc4fa6344915c85fa5b9a9f9db9d
Skip to main content
Licensing

Updates to Microsoft 365, Dynamics 365, PowerApps and Flow Licensing

August 29, 2019

Today we are announcing licensing updates to Dynamics 365, PowerApps and Flow, including the PowerApps and Flow plans included in select Microsoft 365 and Dynamics 365 plans. These changes to our licensing model will:

  • Enable Dynamics 365 customers to buy just what they need
  • Make it easier for PowerApps, Flow and Dynamics 365 customers to start with a business scenario use-case and scale over time
  • Clarify inclusion of PowerApps and Flow within select Microsoft 365 and Dynamics 365 plans

Effective October 1, 2019, we are making the following changes:

Updates to Dynamics 365 licensing

  • Dynamics 365 is moving from the multi-application, one-size-fits-all Customer Engagement (CE), Unified Operations (UO), and Dynamics 365 Plans to individual applications that allow customers to buy just what they need, when they need it.
  • We are making refinements to restricted and unrestricted entities with the goal of enabling more users to access data directly through a PowerApps application or Flow workflow without requiring a Dynamics 365 license. The case entity will now be available to PowerApps and Flow users to create, read, update, and delete. Select Dynamics 365 for Sales entities will be added to the restricted entities list. Learn more about restricted entities here.

New PowerApps and Flow plans

New PowerApps and Flow plans will be introduced, including a per app plan and a per flow plan.

  • The PowerApps per app plan will allow individual users to run applications for a specific business scenario, while the Flow per flow plan will allow customers to implement critical workflows with reserved capacity.
  • With the PowerApps and Flow per user plans, individual users will be able to run an unlimited number of apps or workflows.

Across all PowerApps and Flow plans, customers will be able to take advantage of each service’s full features and capabilities. For example, model-driven applications and the full power of the Common Data Service will be available in both the PowerApps per app plan and the per user plans. Similarly, the ability to trigger at any frequency and without restriction on the number of runs will be available with all Flow plans, including Flow Free which will move to a limit of 5 active flows.

Changes to PowerApps and Flow for Microsoft 365 and Dynamics 365 subscriptions

  • We are refining the PowerApps and Flow plans included in select Microsoft 365 and Dynamics 365 subscriptions to focus on customizing and extending Office 365 and Dynamics 365.
  • Dynamics 365 subscribers may continue using PowerApps and Flow to extend and customize their Dynamics 365 applications. However, Dynamics 365 Enterprise licenses will no longer include general purpose PowerApps and Flow use rights. Dynamics 365 Enterprise application users can continue to run PowerApps applications within their Dynamics 365 environments, but running PowerApps applications in non-Dynamics 365 environments will require a PowerApps license. An additional Flow license will also be required to run flows that do not map to a Dynamics 365 application.
  • For Microsoft 365 subscriptions, we are reclassifying SQL, Azure and Dynamics 365 connectors from Standard to Premium. A standalone PowerApps or Flow plan license will be required to access all Premium connectors.  

Lastly, a single, integrated approach for daily capacity limits will be implemented to help maintain a consistent quality of service for customers with PowerApps and Flow plans. These capacity limits should not impact standard or reasonable usage of PowerApps or Flow. Organizations that require additional capacity for heavy usage scenarios will be able to purchase add-on capacity and assign it to specific users or processes. Existing storage add-ons for PowerApps and Flow remain unchanged.

We continue to evolve Microsoft 365, Dynamics 365, and the Power Platform to enable ecosystem engagement and respond to customer needs.

For more information, read the FAQ.