PowerApps Licensing Guide Training January 2020

Power Apps and Microsoft Flow Licensing Guide | January 2020

Original Source

Microsoft Power Apps, Microsoft Power Automate and
Microsoft Power Virtual Agents Licensing Guide

January 2020
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020
Table of Contents
How to buy ……………………………………………………………………………………………………………………………………………………………………… 2
Licensing Programs……………………………………………………………………………………………………………………………………………………………………… 2
How to license ………………………………………………………………………………………………………………………………………………………………… 2
Multiplexing ………………………………………………………………………………………………………………………………………………………………………………….. 2
Licensing Requirements for External Users ……………………………………………………………………………………………………………………………. 3
Power Apps subscriptions …………………………………………………………………………………………………………………………………………….. 3
Power Apps …………………………………………………………………………………………………………………………………………………………………………………… 3
Power Apps Portals ……………………………………………………………………………………………………………………………………………………………………… 7
Power Automate subscriptions ……………………………………………………………………………………………………………………………………. 9
Power Virtual Agents subscriptions …………………………………………………………………………………………………………………………. 12
Subscription Capacity …………………………………………………………………………………………………………………………………………………. 13
Capacity Add-ons ………………………………………………………………………………………………………………………………………………………… 14
Common Data Service Capacity Add-ons ……………………………………………………………………………………………………………………………..15
AI Builder capacity add-on ……………………………………………………………………………………………………………………………………………………….15
Power Apps and Power Automate capacity add-on……………………………………………………………………………………………………………16
Power Virtual Agents capacity add-on …………………………………………………………………………………………………………………………………..16
Trial and Implementation …………………………………………………………………………………………………………………………………………… 17
Power Platform Service Support……………………………………………………………………………………………………………………………….. 17
Pricing ……………………………………………………………………………………………………………………………………………………………………………. 18
Additional Resources ………………………………………………………………………………………………………………………………………………….. 18
Appendix A: Terminology and Custom Entities …………………………………………………………………………………………………….. 19
Appendix B: Standard Connectors moved to premium category ………………………………………………………………………. 21
Appendix C: Licensing Channel / Segment Availability ………………………………………………………………………………………… 22
Appendix D: Dynamics 365 and Office 365 licenses that include Power Apps and Power Automate capabilities ……………………………………………………………………………………………………………………………………………………………………. 23
Appendix E: Support Policies …………………………………………………………………………………………………………………………………….. 24
Appendix F: Change Log ……………………………………………………………………………………………………………………………………………. 25
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 1
Using This Guide
Use this guide to improve your understanding of how to license Microsoft Power Apps, Power Automate (previously known as Microsoft Flow) and Power Virtual Agents.
This guide is not intended to influence the choice of Microsoft products and services. The examples presented in this guide are illustrative. Microsoft reserves the right to review or update this document at any time without notice.
This document applies for users with Power Apps, Power Automate and Power Virtual Agents licenses.
To facilitate understanding of licensing requirements this guide is structured as follows:
1) What’s new
2) Channel Licensing (how to buy)
3) How to license (product licensing)
4) Add-ons
5) Notes: Changes
For help determining the right technology solution for any given organization, including the license requirements for a specific product or scenario, consult with your Microsoft account team or your Microsoft Certified Partner. This guide does not supersede or replace any of the legal documentation covering use rights.
What’s new in this licensing guide
This licensing guide was updated to reflect licensing updates as of January 2020. See the Change log Appendix F, for specific changes. What is changing in January? Description
See change log
Page 25
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 2
How to buy
Licensing Programs
Licensing programs are channels where you can buy Power Apps, Power Automate and Power Virtual Agents. You can license Power Apps, Power Automate and Microsoft Power Virtual Agents through Microsoft Volume Licensing (VL), Cloud Solution Provider program (CSP), and/or Web Direct (MOSP) programs. In Volume Licensing, Power Apps and Power Automate are available through:
• Enterprise Agreement (EA)
• Enterprise Agreement Subscription (EAS)
• Service and Cloud Enrollment (SCE)
• Enrollment for Education Solutions (under the Campus and School Agreement) (EES)
Additional channels:
• Microsoft Online Government
• Microsoft Products and Services Agreement (MPSA). More information on MPSA is available here.
• Microsoft Online Subscription Program (Web Direct/MOSP)
Participating in a Volume Licensing program typically involves signing an agreement and/or enrollment, meeting a minimum purchase requirement, and ordering licenses through a Microsoft Reseller. Visit the Microsoft Volume Licensing website to learn more about how to buy through Volume Licensing, find a reseller partner, and more helpful information.
How to license
Multiplexing
Multiplexing refers to the use of hardware or software that a customer uses to pool connections, reroute information, or reduce the number of users that directly access or use the Power Apps, Power Automate and Power Virtual Agents service. Multiplexing does NOT reduce the number of SLs of any type required to access the Power Apps, Power Automate and Power Virtual Agents apps. Any user or device that accesses the Power Apps, Power Automate and Power Virtual Agents app —whether directly or indirectly—must be properly licensed.
Power Apps, Power Automate and Power Virtual Agents service can only be accessed if you have a Power Apps, Power Automate or Power Virtual Agents license. Similarly, Power Apps, Power Automate and Power Virtual Agents licenses are required for users that input data into, query, or view data from the Power Apps, Power Automate and Power Virtual Agents apps through a pooling device. Pooled connections use a non-interactive user account in Power Apps, Power Automate and Power Virtual Agents that can access the system but only via the web service layer. Internal users accessing Power Apps, Power Automate and Power Virtual Agents service indirectly through a portal or via an API to a separate service such Microsoft Outlook must also be properly licensed, regardless of if they are set up as a Power Apps, Power Automate and Power Virtual Agents user in the app, for example:
• Internal users that access the Power Apps, Power Automate and Power Virtual Agents service must still be properly licensed for Power Apps, Power Automate and Power Virtual Agents.
• Any user that accesses Power Apps, Power Automate and Power Virtual Agents service that is made available through an automated process requires a Power Apps, Power Automate and Power Virtual Agents license
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 3
• The number of tiers of hardware or software between the Power Apps, Power Automate and Power Virtual Agents apps and the user or devices that ultimately use Power Apps, Power Automate and Power Virtual Agents service indirectly does not affect the number of SLs required.
For additional information about multiplexing refer to the Microsoft Volume Licensing Brief Multiplexing—Client Access License (CAL) Requirements.
Licensing Requirements for External Users
External users must be appropriately licensed to access Power Platform services and data. Applicable licensing includes:
• An appropriate Power Platform USL
• Seeded licensing capabilities from Office or Dynamics 365 USLs
• Power Portal login or page view capacity
• Accessing via an appropriately licensed Power Automate Per Flow workflow
Users must be appropriately licensed whether they are accessing directly or indirectly per multiplexing guidelines.
For additional information about multiplexing refer to the Microsoft Volume Licensing Brief Multiplexing—Client Access License (CAL) Requirements. Note, this document is intended to provide general multiplexing guidance that can be used for online as well as on-premises situations.
For additional information on external guest user access please see here.
Power Apps subscriptions
Power Apps
Service Overview
Power Apps is a low code/no code application platform that allows enterprises to digitize business operations by easily building line of business applications and customizing existing Office 365 and Dynamics 365 applications. For more details, please visit https://powerapps.microsoft.com
Licensing overview
General purpose, full Power Apps capabilities are licensed on a standalone basis. Additionally, limited Power Apps capabilities are included within various Office 365 and Dynamics 365 licenses. High level overview of the licensing structure is provided below. Per user, per app Per user Seeded Power Apps Licensing scheme
Per user, per app
Per user
Through Office 365 and Dynamics 365 user licenses Description
Allow individual users to run applications1 for a specific business scenario based on the full capabilities of Power Apps
Equip users to run unlimited applications based on the full capabilities of Power Apps
Customize and extend Office 365 & Dynamics 365 applications
1 Each license allows end user to run 2 custom apps and access 1 custom portal
Standalone Power Apps licensing
Customers that need general purpose and full capabilities of the platform should license Power Apps on a standalone basis. Licensing is supported on both a “per user” basis as well as a “per user, per app” basis. Both standalone licenses are fully featured. Details follow.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 4
Power Apps per app plan
Power Apps per app plan allows organizations to get started with the platform at a lower entry point. Customers on the per app plan typically start with 1-2 leading use case scenarios before adopting the platform more broadly. Power Apps per app plan is also an attractive licensing option to license end users that run only a few apps.
Power Apps per app plan allows individual users to run 2 custom applications (be it canvas or model or both) and access 1 custom portal based on the full capabilities of Power Apps. Per user, per app offer summary SKU Name
PowerApps per app plan License type
Tenant wide capacity license License assignment
In product Are licenses stackable?
Yes
Entitlement Summary for Power Apps per app license Plans and capabilities Power Apps per app plan Run custom apps / portals
Run custom apps (both canvas and model driven)
2 apps
Access custom portals
1 custom portal Connect to your data
Standard connectors

Premium connectors

On premises data gateway

Custom connectors
⚫ Store and manage data
Utilize Common Data Service

Create and access custom entities (includes complex entities)

Dynamics 365 restricted entities access1
Read only Execute workflows
Power Automate use rights
Within app context
Classic Common Data Service non real-time and real-time workflows
⚫ Per license capacity2
Common Data Service Database Capacity3
50 MB
Common Data Service File Capacity3
400 MB
Daily API request limit2
1,000 Infuse AI
AI Builder capacity add-on
$
1 An entity within Common Data Service becomes restricted only if the Dynamics 365 application is installed on a given environment
2 Service limits are published at https://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits
3 Common Data Service database and file capacity entitlements are pooled at the tenant level
Note:
• Embedded canvas apps within a model-driven app will not count towards the two-app limit.
• A single user might be covered by multiple ‘per app’ licenses to allow the user to use multiple solutions targeted at various business scenarios, without requiring a per-user license
• Once a pool of Power Apps per app licenses are purchased, individual licenses need to be assigned to specific environments and to individual users (i.e. if the same app exists in two environments, a user would require two per app SLs to access both).
• The Power Apps Per App plan is available to education customers under faculty and student pricing. Since these licenses are sold as tenant level capacity and not assigned to users in active directory, customers and partners will be responsible for ensuring that student pricing is only being applied to students. This means that when licenses are purchased with student pricing, the number of app licenses assigned to non-students (i.e. faculty) in the product may not exceed the number of faculty licenses purchased as this would indicate that student licenses have been assigned to faculty.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 5
Power Apps per user plan
Power Apps per user plan allows licensed users to run unlimited custom applications based on the full capabilities of Power Apps. Per user offer summary SKU Name
PowerApps per user plan License type
User license
Entitlement Summary for Power Apps per user license Plans and capabilities Power Apps per user plan Run custom apps / portals
Run custom apps (both canvas and model driven)
Unlimited
Access custom portals
Unlimited Connect to your data
Standard connectors

Premium connectors

On premise data gateway

Custom connectors
⚫ Store and manage data
Utilize Common Data Service

Create and access custom entities (includes complex entities)

Dynamics 365 restricted entities access1
Read only Execute workflows
Power Automate use rights
Within app context
Classic Common Data Service non real-time and real-time workflows
⚫ Per license capacity2
Common Data Service Database Capacity3
250 MB
Common Data Service File Capacity3
2 GB
Daily API request limit2
5,000 Infuse AI
AI Builder capacity add-on
$
1 An entity within Common Data Service becomes restricted only if the Dynamics 365 application is installed on a given environment
2 Service limits are published at https://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits
3 Common Data Service database and file capacity entitlements are pooled at the tenant level
Power Apps use rights included with Dynamics 365 licenses
Limited Power Apps use rights are included within the same environment(s) as the licensed Dynamics 365 application(s) to allow users to customize & extend Dynamics 365 applications. Use of Power Apps capabilities included with Dynamics 365 licenses must be only within the context of the licensed Dynamics 365 application. Further, the specific use rights vary by Dynamics 365 license type.
Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 6
Power Apps use rights with Dynamics 365 applications Capabilities Dynamics 365 Applications1 Dynamics 365 Enterprise Applications2 Run custom apps3
Run standalone apps (canvas/model driven)

Within same environment(s) as licensed Dynamics 365 application(s) Connect to your data
Use pre-built connectors (standard, premium) connectors


Use custom and on-premises connectors

⚫ Store and manage data
Utilize Common Data Service


Create and access custom entities
15 per application

Dynamics 365 restricted entities use rights
Create, read, update and delete
Create, read, update and delete Execute workflows
Power Automate use rights
Within app context
Within app context
Classic Common Data Service non real-time and real-time workflows

⚫ Infuse AI
AI Builder capacity add-on
$
$ Power Apps Portal use rights
Standalone Power Apps Portals use rights

Within same environment(s) as licensed Dynamics 365 application(s)
1Dynamics 365 Sales Professional, Dynamics 365 Customer Service Professional, Dynamics 365 Talent: Onboard, Dynamics 365 Team Members, Dynamics 365 Operations – Activity, Dynamics 365 Business Central Team Members
2 Dynamics 365 Sales Enterprise, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field Service, Dynamics 365 Project Service Automation, Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Retail, Dynamics 365 Talent, Dynamics 365 Business Central
3 Power Apps and Power Automate usage will count against the API request limits provided by the Dynamics 365 license Service limits are published at https://aka.ms/platformlimits – Power Apps and Power Automate capacity add-on can be purchased to increase daily service limits
Power Apps use rights included with Office 365 licenses
Limited Power Apps use rights are included with select Office 365 licenses to allow users to customize & extend Office 365 for productivity scenarios. For a complete list of Office 365 licenses that include Power Apps use rights, please refer to Appendix D.
Power Apps use rights with Office 365 licenses Capabilities Office 365 Run custom apps/portals
Run custom apps (canvas apps)
Unlimited
Run custom apps (model driven apps)

Access custom portals

  • Connect to your data
    Standard connectors (see Appendix B)

    Premium connectors
  • On premise data gateway

  • Custom connectors

  • Store and manage data
    Utilize Common Data Service
  • Create and access custom entities (includes complex entities)

  • Execute workflows
    Power Automate use rights (See Power Automate with Office 365 section)
    ⚫ Per license capacity2 (shared capacity across all Power Apps and Power Automate usage)
    Common Data Service Database Capacity1
  • Common Data Service File Capacity1

  • Daily API request limit2
    2,000
    1Common Data Service database and file capacity entitlements are pooled at the tenant level
    2 Reference https://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 7
    Power Apps Portals
    Service Overview
    Power Apps Portals deliver the capability to build standalone, external-facing portals over the Common Data Service. For more information on Power Apps Portals, please visit https://powerapps.microsoft.com/en-us/powerapps-portals/
    Licensing overview
    Provisioning a Power Apps Portals instance
    Power Apps Portals instances can be provisioned by customers on-demand. Provisioning a portals instance draws 1GB from available (unused) Common data service database capacity. Thus, provisioning additional portals instances is only capped by available Common data service database capacity.
    Usage of a Power Apps Portals instance
    Each end user that accesses a Power Apps Portals instance needs to be licensed appropriately. The table below outlines the end user types. End user type Description Use case examples External user (authenticated)
    Obtains secure access to personalized data by utilizing authentication mechanisms such as Azure AD B2C, LinkedIn, Okta, etc.
    • B2B – Partner management (Dealer, Supplier, Franchise etc.)
    • B2C – Account management etc. Anonymous user
    Access publicly viewable web pages powered by the portal
    Knowledge management sites Internal user
    A user licensed with Power Apps or Dynamics 365
    Employee self-serve
    The licensing scheme varies based on end user type. End user type Licensing model Description External user (authenticated)
    Per login
    A login provides the authenticated user with access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login
    Think of a login as a day pass to a single Power Apps Portal Anonymous user
    Per page view
    Internal user
    • License fee pays for access to Power Apps Portals
    • No additional monetization
    Custom portal use rights are aligned with custom app use rights
    Per login model
    For Power Apps Portals instances that implement authenticated external user scenarios, appropriate login capacity, based on anticipated usage volumes, should be purchased. Customers should purchase necessary capacity of logins across all Portals instances that cater to authenticated external user scenarios. SKU Names Unit Capacity Min Purchase Monthly Volume Launch Channel PowerApps Portals login capacity add-on
    100 logins
    /month
    1
    100 logins
    Oct-19
    All PowerApps Portals login capacity add-on tier-2
    10
    1,000 logins
    Dec-19
    All PowerApps Portals login capacity add-on tier-3
    50
    5,000 logins
    Dec-19
    CSP only
    Each unit provides 100 logins/month. Volume tiers and corresponding SKUs differ based on minimum purchase requirements. For each of the tiers, once the minimum purchase requirement is met, additional units can be purchased in units of 1.
    For example, a customer requiring 5,500 logins/month can purchase 55 units of “Power Apps Portals login capacity add-on tier-3”
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 8
    Capacity enforcement
    For Power Apps Portals login capacity add-on SKUs, purchased capacity is enforced monthly. Unused logins do NOT carry over from one month to another. Customers should purchase appropriate capacity aligned with peak monthly anticipated usage.
    Overage handling
    While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
    Assignment of purchased capacity
    The minimum assignment capacity per Power Apps Portal instance is 100 logins/month. Once the minimum capacity of 100 logins/month is assigned, additional logins can be added in terms of 1 login.
    Per page view model
    For Power Apps Portals instances that implement anonymous access scenarios, appropriate capacity of page views, based on anticipated usage, should be purchased. Customers should purchase necessary page views capacity across all Portals instances that cater to anonymous access scenarios. SKU Name Unit Capacity Channels PowerApps Portals page view capacity add-on
    100,000
    page views/month
    All
    Each unit provides 100,000-page views per month. For example, a customer requiring 570,000-page views per month, should purchase 6 units of “Power Apps Portals page view capacity add-on”
    Capacity enforcement
    For Power Apps Portals pageview capacity add-on SKUs, purchased capacity is enforced monthly. Unused page views do NOT carry over from one month to another. Customers should purchase appropriate capacity aligned with peak monthly anticipated usage.
    Overage handling
    While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
    Assignment of purchased capacity
    The minimum assignment capacity per Power Apps Portal instance is 50,000-page views/month. Once the minimum capacity is assigned, additional page views can be added in terms of 1-page view
    Power Apps Portals – Use rights for Internal users
    For internal users i.e. users licensed with Power Apps or Dynamics 365 licenses, the use rights for Power Apps Portals which are essentially custom portals aligns with use rights to custom Power Apps. License Custom Power Apps Portals use rights Dynamics 365 Team Members
    None Dynamics 365 Operations – Activity
    None Dynamics 365 Professional license1
    None Dynamics 365 Enterprise license2
    • Power Apps Portals that map to licensed Dynamics 365 application context
    • Power Apps Portals that map to the same environment as the licensed Dynamics 365 application Power Apps per app
    1 Power Apps portal Power Apps per user
    Unlimited Power Apps portals Office 365
    None
    1Dynamics 365 Sales Professional, Dynamics 365 Customer Service Professional, Dynamics 365 Talent: Onboard
    2Dynamics 365 Sales Enterprise, Dynamics 365 Customer Service Enterprise, Dynamics 365 Field Service, Dynamics 365 Project Service Automation, Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Retail, Dynamics 365 Talent, Dynamics 365 Business Central
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 9
    API limits for Power Apps portals
    Each login provides a daily limit entitlement of 200 API calls per 24-hour period per user. Anonymous page views, which rarely interact with backend system functionality, are afforded up to 3 API calls per page view.
    These API calls are pooled at portal level depending on number of logins/page views assigned to portal.
    Power Automate subscriptions
    Service Overview
    Power Automate allows enterprises to implement automated workflows and business processes and achieve operational efficiencies. For more details, please visit https://flow.microsoft.com.
    Licensing overview
    General purpose Power Automate capabilities are licensed on a standalone basis. Limited Power Automate capabilities are also included within Power Apps, Office 365 and Dynamics 365 licenses. High level overview of the licensing structure is provided below. Power Automate Per user Per flow Seeded Flow
    Licensing scheme
    Per user
    Per flow
    Minimum purchase of 5 flows
    Through Office 365, Dynamics 365, and Power Apps
    Description
    Allow individual users to create unlimited flows based on their unique needs.
    Implement flows with reserved capacity that serve unlimited users across an organization.
    Automate business processes and workflows for Office 365, Dynamics 365, and Power Apps
    Standalone Power Automate licensing
    Customers that need full-fledged, general purpose workflow/business process automation capabilities, should consider purchasing standalone Power Automate licenses. Licensing is supported on both a “per user” basis as well as a “per flow” basis. Both standalone licenses include the full capabilities on Power Automate. Details follow.
    Power Automate per user plan
    Power Automate per user plan equips individual users to create and run unlimited workflows and business processes based on their unique needs. The per user plan is intended to support the broad adoption of an automation culture in an organization. Should the entire organization be licensed with the Power Automate per user plan, admins will have minimal overhead with tracking how many flows are being activated/used within the organization. Per user offer details SKU Name
    Flow per user plan Enabled flows
    Unlimited Usage limit
    5,000 daily API requests
    “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
    Power Automate per business process plan
    Power Automate per business process plan is licensed by flow and allows customers to implement critical business processes with capacity that serves teams, departments, or the entire organization without individually licensing each end user that triggers the licensed flow.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 10
    Power Automate per business process plan is great for departmental scenarios where typically, one power user sets up a flow and shares the same with the broader group. This plan alleviates the need to license each end user that knowingly/unknowingly triggers execution of the licensed flow. Per flow offer details SKU Name
    Flow per business process plan Minimum purchase
    5 units Usage limit
    15,000 daily API requests per licensed flow
    Note:
    • All types of enabled top level flows need to be licensed (Scheduled flows, automated flows, instant flows and business process flows). Flows that are only used as “child” flows (triggered by another flow) do not need to be additionally licensed
    • Should customers wish to license more top-level flows, they should purchase more units of the “Power Automate per business process plan”
    Should customers only wish to license more usage capacity for currently licensed flows, they may purchase “Power Apps and Power Automate capacity add-on”. Plan and Capabilities Power Automate per user plan Power Automate per flow plan Basics
    Minimum purchase
    NA
    5 units
    User license required?
    Yes

  • Execute flows
    Workflows


    Business process flows

    ⚫ Connect to your data
    Standard connectors


    Premium connectors


    On premises data gateway


    Custom connectors

    ⚫ Store and manage data
    Common data service use rights

    ⚫ Per license capacity
    Common Data Service Database Capacity1
    50MB
    50MB
    Common Data Service File Capacity1
    200MB
    200MB
    Daily API request limit2
    5,000
    15,000
    1 Reference https://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits.
    2 Additional Common Data Service Database/File/Log capacity can be purchased in increments of 1GB. Common Data Service Database and File capacity are pooled tenant wide.
    Note, scheduled flows may be configured to trigger every minute, irrespective of license type. There are no limits on the frequency of flow runs beyond what the connector supports.
    Power Automate use rights included with Power Apps licenses
    Power Apps licenses (both “Power Apps per app plan” and “Power Apps per user plan”) include Power Automate use rights for the purpose of automating workflows associated with the Power Apps application(s).
    Power Automate use within Power Apps is limited to the context of the Power Apps application. What this means is that for both triggers and actions, flows included within a Power Apps application can connect to:
    • Any data source within the use rights of the Power Apps application
    • Directly with the Power Apps application (via built in trigger/action)
    If the flow is isolated and has nothing to do with the Power Apps application, then standalone Power Automate licenses will need to be purchased.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 11
    Example of Power Automate use within Power Apps application context:
    User with a standalone Power Apps license runs an app that uses SQL DB as the data source and includes flows that:
    • Read from OR write to SQL DB
    • Use a built-in Power Apps trigger and/or action – e.g., Send a push notification to the app
    Example of Power Automate use outside of Power Apps application context:
    The same user (in the example above) now also wants to use a flow that updates an Oracle database, and:
    • Is completely unrelated to the Power Apps app
    • Does not interact in any way with the Power Apps app (or its data sources)
    This user will then require a standalone Power Automate license. Plans and capabilities Power Automate use rights within Power Apps licenses Execute flows1,2
    Workflows

    Business process flows
    ⚫ Connect to your data
    Standard connectors

    Premium connectors

    On-premises data gateway

    Custom connectors
    ⚫ Store and manage data
    Common data service use rights

    1 Power Automate use needs to map to the context of the embedding Power Apps applications
    2 Power Automate usage counts against the service limits associated with the embedding Office 365 license. Please review https://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits
    Power Automate use rights included with Dynamics 365 licenses
    Dynamics 365 licenses include Power Automate use rights for the purpose of customizing and extending Dynamics 365 application(s).
    Power Automate use within Dynamics 365 is limited to the context of the embedding Dynamics 365 application. For both triggers and actions, flows included within the Dynamics 365 application can connect to:
    • Any data source within the use rights of the Dynamics 365 application
    • Directly with the Dynamics 365 application (via built in trigger/action)
    If the embedded flow is not within the context of the Dynamics 365 application, then standalone Power Automate licenses will need to be purchased.
    Summary of Power Automate use rights with Dynamics 365 licenses Plans and capabilities Power Automate use rights within Dynamics 365 licenses Execute flows1,2
    Workflows

    Business process flows
    ⚫ Connect to your data
    Standard connectors

    Premium connectors

    On-premises data gateway

    Custom connectors
    ⚫ Store and manage data
    Common data service use rights

    1 Power Automate use needs to map to the context of the embedding Dynamics 365 applications
    2 Power Automate usage counts against the service limits associated with the embedding Dynamics 365 license. Reference https://aka.ms/platformlimits for more details on usage limits; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 12
    Power Automate use rights included with Office 365 licenses
    Office 365 licenses include Power Automate use rights for the purpose of customizing and extending Office 365 applications.
    Power Automate use within Office 365 is limited to the context of the embedding Office 365 application. For both triggers and actions, flows included within the Office 365 application can connect to:
    • Any data source within the use rights of the Office 365 application
    • Directly with the Office 365 application (via built in trigger/action)
    If the embedded flow is not within the context of the Office 365 application or if the embedded flow needs to connect to a premium on-premises or custom data source standalone Power Automate licenses will need to be purchased.
    Summary of Power Automate use rights with Office 365 licenses Plans and capabilities Power Automate use rights within Office 365 licenses Execute flows1
    Workflows
    Unlimited1
    Business process flows
  • Connect to your data
    Standard connectors

    Premium connectors
  • On-premises data gateway

  • Custom connectors

  • Store and manage data
    Common data service use rights
  • Per license capacity
    Daily API Requests1
    2,000
    1 Usage capacity is across both Power Apps and Power Automate; “Power Apps and Power Automate capacity add-on” can be purchased to increase daily service limits. More details at https://aka.ms/platformlimits
    Power Virtual Agents subscriptions
    Service Overview
    Power Virtual Agents empowers teams to easily create powerful bots using a guided, no-code graphical interface without the need for data scientists or developers. It easily integrates bots with hundreds of apps and services using prebuilt connectors and allows the ability to create custom workflows with Power Automate, enabling bots to take action on behalf of customers. It allows users to monitor and continuously improve bot performance using AI- and data-driven insights available in an easy-to-read dashboard. For more information, please visit: https://powervirtualagents.microsoft.com
    Licensing overview
    The Power Virtual Agents application is licensed per tenant. The administrator will need to assign user licenses through the admin portal to Power Virtual Agent users who need access to the Power Virtual Agents application. Power Virtual Agents will be charged according to the unit of ‘sessions’1 (see below for definition of session). Tenant offer summary SKU Name
    Power Virtual Agent License type
    Tenant license
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 13
    Summary of Power Virtual Agents entitlements Plans and capabilities Power Virtual Agents entitlements Create flows
    Workflows
    Unlimited (only applicable for flows triggered from Power Virtual Agents) Chat Sessions
    Sessions / tenant / month
    2k Store and manage data
    Common data service use rights
    ⚫ Per license capacity
    Common data service – Database Capacity
    10GB
    Common data service – File Capacity
    20GB
    Common data service – Log Capacity
    2GB
    1Session definition:
    A session is an interaction between the customer and the bot, and represents one unit of consumption. The session begins when an authored topic is triggered. These sessions are referred to as ‘billed sessions’ in the product. Sessions are deducted for both testing and production usage.
    A topic ends in one of the following scenarios:
    i. When all of the customer’s questions are answered
    ii. When a customer intentionally ends or closes a chat session, or
    iii. When a bot is unable to answer adequately and the interaction is escalated to a live agent
    Reference link for details.
    Capacity enforcement
    All Power Virtual Agents purchased capacity is enforced monthly and unused sessions do not carry over month to month.
    Overage handling
    While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
    Comprehensive monitoring, reporting and alerting mechanisms will be instituted to assist customers with managing Power Virtual Agents capacity. More stringent technical enforcement (including service denial) will result for usage that is significantly over the purchased capacity.
    Subscription Capacity
    Power Apps, Power Automate and Power Virtual Agents default subscription capacities leverage the same tenant and infrastructure and will accrue across one tenant. Every tenant with a Power Apps, Power Automate or Power Virtual Agents license receives default capacity. In addition, for each Power Apps per user, Power Apps per user, per app, Power Automate per user, and Power Automate per flow plan license there is additional capacity added to the tenant. Power Apps Default Capacity per tenant Default per user Default per app Accrued per user Accrued per app Common Data Service Database capacity
    10GB
    1GB
    250MB
    50MB Common Data Service File capacity
    20GB
    2GB
    2GB
    400MB Common Data Service Log capacity
    2GB
    200MB
  • Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 14
    Power Automate Default Capacity per tenant Default per user Default per flow Accrued per user Accrued per flow Common Data Service Database capacity
    1GB
    1GB
    50MB
    50MB Common Data Service File capacity
    2GB
    2GB
    200MB
    200MB Common Data Service Log capacity
    200MB
    200MB

  • Note, customers may have as many flows as needed per-flow plan. Each flow will increase capacity limits. Power Virtual Agents Default Capacity per tenant Default per tenant Common Data Service Database capacity
    10GB Common Data Service File capacity
    20GB Common Data Service Log capacity
    2GB
    Power Apps, Power Automate, Power Virtual Agents and Dynamics 365 Customer Engagement applications leverage the same tenant and infrastructure. Common Data Service capacity (database, file and log formats) is pooled across the tenant and shared amongst relevant application workloads.
    Common Data Service allows integration with Outlook and SharePoint.
    Common Data Service capacity – Capacity types and Purpose Type Purpose Database Stores and manages entity definitions and data
    File
    Store attachments to notes or emails in Customer Engagement applications and Power Apps. These include documents, image files, videos, PDF files and other crucial files needed in an organization. Log Records entity and attribute data changes over time for use in analysis and reporting purposes. Log capacity is designed to help organizations meet their auditing, compliance, and governance policies
    The first subscription of Power Apps OR Power Automate OR Power Virtual Agents OR Dynamics 365 Customer Engagement provides the one-time default capacity entitlement for the tenant. For example, if a new customer purchases “Power Apps per user plan”, the tenant will receive 10GB of default Common Data Service Database capacity. Additional subscriptions do not add to the tenant’s default capacity.
    When additional subscriptions are added to the tenant, additional Common Data Service capacity may accrue to the tenant.
    Example:
    Let’s assumed that a new customer starts by purchasing 10 Power Apps per user licenses and 20 Power Apps per app licenses. In this case, the total tenant wide pooled capacity will be as follows: Default and Accrued Capacity Allocation Default/ tenant Accrued/10 Enterprise USL Total Tenant wide capacity Common Data Service Database Capacity 10GB 10250MB + 2050MB = 3.5GB 10GB + 3.5GB = 13.5GB Common Data Service File Capacity 20GB 102GB + 20400MB = 28GB 20GB+28GB = 48 GB Common Data Service Log Capacity 2GB NA 2GB
    Capacity Add-ons
    If you require additional subscription capacity (such as additional database or file capacity), you can include these optional add-on licenses with your subscription. Subscription add-ons apply across tenant and are not tied to a specific user. Subscription add-ons can be purchased at any time and remain a part of the subscription for the remainder of the subscription term.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 15
    Common Data Service Capacity Add-ons
    Power Apps apps or flows utilizing the Common Data Service will consume varying quantities of Database Capacity, File Capacity, and Log Capacity and may require different kinds of Power Apps and Power Automates environments. Apps may utilize flows, or flows may be run separately from apps.
    Each type of per user license (Office 365, Dynamics 365 applications, the standalone Power Apps and Power Automate Plan licenses) include capacities of one of more of these basic resources. These entitlements are pooled, and shared across users, at the customer tenant level. Subscription Capacity/tenant Additional Increment Common Data Service Database capacity
    1GB Common Data Service File capacity
    1GB Common Data Service Log capacity
    1GB
    AI Builder capacity add-on
    Service overview
    AI Builder helps empower everyone – regardless of their technical experience to work with Artificial Intelligence (AI). This solution helps easily add AI capabilities to both apps and business processes. AI Builder supports various scenarios such as predictions, business card, and many more. For more information on AI Builder, please visit https://PowerApps.microsoft.com/ai-builder/
    Licensing overview
    AI Builder is licensed as an add-on to standalone Power Apps and Power Automate licensing as well as Dynamics 365 licenses.
    AI Builder is licensed on a capacity basis. AI Builder capacity is expressed in the form of “service credits”. Service credits serve as the single (common) currency across all the scenarios supported by AI Builder. Available service credits are deducted when AI Builder services are used. Different scenarios (for example, forms processing, prediction, etc.) burn down service credits at different rates.
    Customers should purchase the appropriate number of AI Builder capacity add-on units based on anticipated usage across all scenarios. Offer Details SKU name
    AI Builder capacity add-on License type
    Tenant wide capacity license Entitlement
    1 million monthly service credits Qualifying base licenses
    Power Apps, Power Automate and Dynamics 365 licenses
    Each unit of “AI Builder capacity add-on” includes 1 million service credits per month. For example, a customer requiring 4.7 million service credits per month (based on anticipated usage), should purchase 5 units of “AI Builder capacity add-on”.
    Note:
    • Purchased service credits can be used from AI Builder models included within Power Automate, Power Apps and Dynamics 365 applications
    • Service credits are deducted / consumed for both training and production usage
    • Service credits are pooled across the tenant
    Capacity enforcement
    For AI Builder capacity add-on SKUs, purchased capacity is enforced monthly and unused service credit do not carry over month to month.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 16
    Overage handling
    While occasional and reasonable overages will be tolerated, customers exceeding purchased capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
    Comprehensive monitoring, reporting and alerting mechanisms will be instituted to assist customers with managing AI Builder capacity. More stringent technical enforcement (including service denial) will result for usage that is significantly over the purchased capacity.
    Assignment of purchased capacity
    Assignment of purchased capacity to appropriate Power Automate, Power Apps applications and Dynamics 365 workloads is managed in product. Assignment helps ensure capacity for critical AI models. The minimum capacity to be assigned is 1 service credit.
    Power Apps and Power Automate capacity add-on
    Power Apps and Power Automate capacity add-on increases the daily API request limit for Power Apps, Power Automate and Dynamics 365 users/workloads that need more usage capacity than their allocation. For more details on service limits and to learn about daily service limits applicable to various to licenses, please visit https://aka.ms/platformlimits Offer details SKU name
    PowerApps and Flow capacity add-on Base licenses
    Power Apps, Power Automate, Office 365 and Dynamics 365 licenses Capacity entitlement
    Additional 10,000 daily API requests per unit Capacity assignment
    In product
    Capacity enforcement
    For Power Apps and Power Automate capacity add-on SKUs, purchased capacity is enforced daily and unused/unassigned API calls do not carry over from day to day. Also, the assigned capacity is specific to a user/flow
    Overage handling
    While occasional and reasonable overages will be tolerated, customers exceeding licensed capacity should adjust their purchase quantity per standard Microsoft terms to remain in compliance.
    Assignment of purchased capacity
    Upon purchase of the add-on subscription, the tenant admin will need to assign the purchased capacity to specific users and/or flows. Minimum capacity that needs to be assigned is 1,000 daily API requests.
    Power Virtual Agents capacity add-on
    Power Virtual Agents capacity add-on increases the number of chat bot sessions limit per tenant per month. Offer details SKU name
    Chat session for Virtual Agent Purchase requirement
    Power Virtual Agents Capacity entitlement
    1000 Chat sessions / tenant / month
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 17
    Trial and Implementation
    Free Trials
    You can sign-up for a free trial of Power Apps, Power Automate or Power Virtual Agents for details:
    • Power Apps here
    • Power Automate here
    • Power Virtual Agents here
    Development and Testing with Power Apps and Power Automate
    The free Community Plan is intended for individual use allowing developers to learn and build skills on Power Apps, Power Automate and Common Data Service. To learn more, click here.
    You can find Power Apps, Power Automate and Power Virtual Agents price lists here:
    Power Platform Service Support
    Support Plans
    The benefits included in the Subscription Support Plan are applicable for customers who license Power platform solutions via MOSP, EA, MPSA, EAS, and EES. Premium Support offerings are available for purchase:
    • Professional Direct Support is a Power platform solutions specific support plan providing a cohesive support experience with exceptional tools and resources to accommodate any needs during all stages of the Power platform solutions lifecycle. Fast response times for customers’ most critical issues, proactive advisory services and much more.
    • Enterprise Solutions – Unified Support is a comprehensive support solution for your large business that helps reduce costs, enhance productivity, and use technology to realize new opportunities for any stage of the IT lifecycle.
    Microsoft guarantees support in International English and provides local language support in select markets around the world wherever possible.
    (i) Technical support is included in the online subscriptions when a customer chooses to deploy online (Volume Licensing and Web Direct). When purchasing through the CSP program, support is required to be provided by your partner.
    (ii) If a customer chooses to deploy with dual-use rights, Microsoft Technical support will assist with support issues resulting with the deployment of dual use rights, however, support is not included for the on-premises deployment.
    (iii) Support offerings for on-premises are sold separately when a customer chooses to deploy on-premises. The customer has the following options:
    a. Seek support from their partner
    b. Purchase professional support incidents from support.microsoft.com to get support directly from Microsoft
    Response times for technical support incidents vary by case severity. Definitions are included in Appendix E. More information about Power platform solutions Support options can be viewed here.
    Support offerings may not be mixed on a tenant. Each Power platform solutions user must be licensed with the same support offering, i.e., if the customer purchases Professional Direct support, all their users must be licensed with Professional Direct.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 18
    Pricing
    You can find Power Apps, Power Automate and Power Virtual Agents price lists here:
    • Power Apps: https://powerapps.microsoft.com/pricing
    • Power Automate: https://flow.microsoft.com/pricing
    • Power Virtual Agents: https://go.microsoft.com/fwlink/?linkid=2099502
    Additional Resources
    Resource Link
    Power Apps Service
    https://powerapps.microsoft.com/
    Power Automate Service
    https://flow.microsoft.com/
    Power Virtual Agent Service
    https://powervirtualagents.microsoft.com/
    Dynamics 365 Licensing Guide
    https://go.microsoft.com/fwlink/?LinkId=866544&clcid=0x409
    Dynamics 365 Business Central Licensing Guide
    https://go.microsoft.com/fwlink/?LinkId=871590&clcid=0x409
    Dynamics 365 Mixed Reality Licensing Guide
    https://go.microsoft.com/fwlink/?LinkId=2090495&clcid=0x409
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 19
    Appendix A: Terminology and Custom Entities
    Administration: Administration is critical in order to establish boundaries and policies around the use of Power Apps in organizations
    • Manage environments – space to store, and manage, and share data, apps, and flows
    • Data policies – create and enforce policies that define how data can be shared
    App (definition of Power Apps per app): An “app” is a combination of Power Platform assets that solves a specific business scenario
    • Each “per app” license provides use rights to 1 Portal and 2 custom apps (model driven and/or canvas)
    • No limits on other components (e.g., forms, dashboards, etc.)
    Application Program Interface (API): Any form of application programming interface that provides access to a Microsoft service and any associated tools, including sample code that enables interactions with Microsoft’s services, and documentation that Microsoft makes available under these TOU, and includes all elements, components, and executables of such API.
    Application Types:
    • Canvas Apps: Design and build a business application from a canvas in Microsoft Power Apps without writing code in a traditional programming language. Design the application by dragging and dropping elements onto a canvas, the designer has complete control over app layout.
    • Model-driven Apps: Design is a component-focused approach to app development based on data model and business processes. Unlike canvas app development where the designer has complete control over application layout, with model-driven apps much of the layout is determined for you and largely designated by the components you add to the application.
    Common Data Service: Common Data Service lets you store and manage data that’s used by business applications.
    Connector: It provides a way for users to connect their business data and leverage a set of pre-built actions and triggers to build their applications and workflows. Examples of connections: Common Data Service, SharePoint, SQL, OneDrive, Excel, Dynamics 365.
    • Standard Connector: Data sources within the Microsoft 365 ecosystem. Examples: Excel, Outlook, SharePoint, LinkedIn. A list of standard connectors here.
    • Premium Connector: Business systems beyond Microsoft 365. Examples: DocuSign, Zendesk, Jira Software.
    • Custom Connector: To support more tailored scenarios, you can build custom connectors with their own triggers and actions. These connectors are function-based – data is returned based on calling specific functions in the underlying service. Example: Services that are not available as prebuilt connectors.
    • On-premises Connector: Access on-premises data using a gateway. Example: Microsoft SQL Server.
    CRUD: Create, read, update, and delete operations.
    Entities: A set of records used to store data, similar to how a table stores data within a database. Entities let you model your business data for use within your organization business applications. Examples of entities: Account, Contact, Lead, Opportunity.
    • Standard entities: Common Data Service provides set of business entities, out of the box, that represent most commonly used entities across business applications. Examples: Account, Appointment, Contact, Email, etc.
    • Custom entities: Entities that are created by the customer/partner for a specific business need. For example, type of machine is not a standard entity, so you can create it as a custom entity.
    • Restricted entities: Entities that requires a Dynamics 365 license for full access. Examples: Case, SAL, Knowledge Articles. For list of restricted entities click here.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 20
    • Complex entities: These are entities that use complex server-side business logic. Any entity (whether standard or custom) becomes complex once the customer/partner associates the entity with the custom business logic. Example: any entity that uses a real-time workflow or code plug-in.
    Flow (definition of flow within app context): For both triggers and actions, flows included within an embedding application can connect
    • To any data source within the use rights of the embedding application
    • Directly with the embedding application (via built in trigger/action)
    Workflows:
    • Background workflows: Task automation across systems and services. Runs in the background.
    • Real-time workflows: Task automation across systems and services. Runs in a real time manner.
    • Business process flows: Structured stateful human interactive workflows which are composed of multiple steps, allows branching/stage gating, and includes process KPIs and reporting.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 21
    Appendix B: Standard Connectors moved to premium category
    Power Apps and Power Automate rely on a common set of pre-built connectors to provide access to business data. These pre-built connectors are divided into two categories (Standard and Premium) which align to the use rights across the various service editions. For a complete list of the available data connectors click here.
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 22
    Appendix C: Licensing Channel / Segment Availability License Channel Segment EA EAS EES CSP MPSA MOSP CORP FAC STU EDU GOV GCC NFP Power Apps per app plan ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Power Apps per user plan












    ⚫ Power Automate per user plan ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Power Automate per business process plan












    ⚫ Power Apps Portals login capacity add-on ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Power Apps Portals login capacity add-on tier-2












    ⚫ Power Apps Portals login capacity add-on tier-3 ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Power Apps Portals page view capacity add-on












    ⚫ AI Builder capacity add-on ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Power Apps and Power Automate capacity add-on












    ⚫ Common Data Service Database Capacity ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Common Data Service File Capacity












    ⚫ Common Data Service Log Capacity ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ ⚫
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 23
    Appendix D: Dynamics 365 and Office 365 licenses that include Power Apps and Power Automate capabilities
    Dynamics 365 Qualifying Licenses
    Dynamics 365 Sales Enterprise
    Dynamics 365 Supply Chain Management
    Dynamics 365 Sales Professional
    Dynamics 365 Retail
    Dynamics 365 Customer Service Enterprise
    Dynamics 365 for Talent
    Dynamics 365 Customer Service Professional
    Dynamics 365 for Talent: Onboard
    Dynamics 365 Field Service
    Dynamics 365 Unified Operations – Activity
    Dynamics 365 Project Service Automation
    Dynamics 365 Business Central
    Dynamics 365 Team Members
    Dynamics 365 Business Central Team Members
    Dynamics 365 Finance
    Office 365 Qualifying Licenses
    Office 365 Business Essentials
    Office 365 A5 for Students
    Office 365 Business Premium
    Office 365 Education E3 for Faculty
    Office 365 A1 for Faculty
    Office 365 Education E3 for Students
    Office 365 A1 for Students
    Office 365 Education for Homeschool for Faculty
    Office 365 A1 Plus for Faculty
    Office 365 Education for Homeschool for Students
    Office 365 A1 Plus for Students
    Office 365 Enterprise E1
    Office 365 A3 for Faculty
    Office 365 Enterprise E2
    Office 365 A3 for Students
    Office 365 Enterprise E3
    Office 365 A3 for Student Use Benefit
    Office 365 Enterprise E3 Developer
    Office 365 A5 for Student Use Benefit
    Office 365 Enterprise E3 without ProPlus
    Office 365 A5
    Office 365 Enterprise E5
    Office 365 A5 for Faculty
    Office 365 Enterprise F1
    Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 24
    Appendix E: Support Policies
    SEVERITY CUSTOMER’S SITUATION EXPECTED MICROSOFT RESPONSE EXPECTED CUSTOMER RESPONSE A Critical business impact: • Customer’s business has significant loss or degradation of services. • Needs immediate attention Initial response: • 1 hour or less for Professional Direct and Unified Support • Next business day for Subscription • Allocation of appropriate resources to sustain continuous efforts all day, every day₁ • Accurate contact information on case owner B Moderate business impact: • Customer’s business has moderate loss or degradation of services, but work can reasonably continue in an impaired manner Initial response: • 2 hours or less for Professional Direct and Unified Support • Next business day for Subscription • Allocation of appropriate resources to sustain continuous effort unless customer requests to opt-out of 24×7₂ • Accurate contact information on case owner C Minimum business impact: • Customer’s business is substantially functioning with minor or no impediments of services Initial response: • 4 hours or less for Professional Direct and Unified Support • Next business day for Subscription • Accurate contact information on case owner C Minimum business impact: • Customer’s business is substantially functioning with minor or no impediments of services Initial response: • 4 hours or less for Professional Direct and Unified Support • Next business day for Subscription • Accurate contact information on case owner

    1. 24×7 support is only available for Professional Direct and Unified Support. Unified customers login to Microsoft Online to submit. 24×7 support for Severity B incidents is only available for Unified.
      2.Microsoft may downgrade the severity level if the customer is not able to provide adequate resources or responses to enable Microsoft to continue with problem resolution efforts.
      Power Apps, Power Automate and Power Virtual Agents Licensing Guide | January 2020 P a g e | 25
      Appendix F: Change Log
      Page
      Topic
      Change
      Action
      Date
      3
      Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for Licensing Requirements for External Users External Users External Users External Users External Users External Users External Users External Users External Users External Users External Users External Users External Users
      AddedAddedAddedAddedAdded
      Added Added Added Added Added Added section sectionsectionsectionsectionsection.
      January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020
      4
      Power Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app license Power Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app license Power Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app licensePower Apps per app license
      ClarifiedClarifiedClarifiedClarifiedClarifiedClarified Clarified
      If the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user f the same app exists in two environments, a user would require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access both would require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access both would require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access bothwould require two per app SLs to access both.
      January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020
      7
      Azure ADAzure ADAzure ADAzure ADAzure ADAzure ADAzure ADAzure AD
      ClarifiedClarifiedClarifiedClarifiedClarifiedClarified
      Azure AD Azure AD Azure AD Azure AD Azure AD Azure AD Azure AD Azure AD Azure AD B2C
      January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020
      12
      Power Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual Agents
      RemovedRemovedRemovedRemovedRemovedRemovedRemoved
      Removed Removed Removed Removed Removed Removed Removed Removed sentence sentencesentencesentencesentencesentencesentence: “Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a Since Power Virtual Agents is a tenanttenanttenanttenanttenanttenant-based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and based license, customers may install, use, and configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with configure one Power Virtual Agents application with only one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instance only one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instance only one Dynamics 365 instanceonly one Dynamics 365 instanceonly one Dynamics 365 instance.”
      January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020
      17, 2417, 2417, 2417, 2417, 2417, 24
      Service Support Plans and PoliciesService Support Plans and Policies Service Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and Policies Service Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and Policies Service Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and PoliciesService Support Plans and Policies
      AddedAddedAddedAdded
      Added Added Added Added Added section andsection andsection andsection and section andsection andsection andsection andsection andsection and policy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendixpolicy appendix.
      January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020January 2020
      AllAllAll
      Power AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower AutomatePower Automate
      Update UpdateUpdateUpdateUpdate
      Microsoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power Automate Microsoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power AutomateMicrosoft Flow renamed Power Automate
      December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019
      AllAllAll
      Power AppsPower AppsPower AppsPower AppsPower AppsPower AppsPower AppsPower AppsPower AppsPower Apps
      Update UpdateUpdateUpdateUpdate
      PowerApps PowerApps PowerApps PowerApps PowerApps PowerApps PowerApps PowerApps PowerApps changed changed changed changed changed changed changed changed to Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Appsto Power Apps
      December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019
      4
      Power Power Power Power Power Power Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan Apps per Plan – Student Student Student Student Student Student Student Student licenseslicenseslicenseslicenseslicenseslicenses
      AddedAddedAddedAddedAdded
      The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education The Power Apps Per App plan is available to education customers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricing customers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricing customers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricing customers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricingcustomers under faculty and student pricing
      December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019
      1, 2, 1, 2, 1, 2, 1, 2, 1, 2, 1, 2, 12, 1612, 1612, 1612, 1612, 1612, 16
      Power Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual AgentsPower Virtual Agents
      AddedAddedAddedAddedAdded
      Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available Power Virtual Agents is becoming generally available and and and and licenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchase licenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchase licenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchaselicenses are available for purchase
      December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019December 2019
      4
      Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use Dynamics 365 Power Apps use rightsrightsrightsrightsrightsrights
      ClarifiedClarifiedClarifiedClarifiedClarifiedClarified Clarified
      User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment User rights are included within the same environment as Dynamics 365 applicationsas Dynamics 365 applications as Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applications as Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applicationsas Dynamics 365 applications
      November 2019November 2019November 2019November 2019 November 2019November 2019 November 2019November 2019November 2019November 2019November 2019
      11
      Common Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integrationCommon Data Service integration
      AddedAddedAddedAddedAdded
      Allows Allows Allows Allows Allows Allows integration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePoint integration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePointintegration with Outlook and SharePoint
      November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019
      12
      AI BuilderAI Builder AI BuilderAI BuilderAI BuilderAI BuilderAI BuilderAI BuilderAI Builder
      ClarifiedClarifiedClarifiedClarifiedClarifiedClarified
      AddAddAdd-on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics on to Power Apps and Flow as well Dynamics 365 licenses365 licenses365 licenses365 licenses365 licenses365 licenses365 licenses365 licenses365 licenses365 licenses
      November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019November 2019
      4-7
      Power Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plans Power Apps plansPower Apps plansPower Apps plansPower Apps plansPower Apps plans
      NewNewNew
      CapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapability
      October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019
      7-9
      Power Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps Portal Power Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps PortalPower Apps Portal
      NewNewNew
      CapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapability
      October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019
      9-13
      Flow plansFlow plansFlow plansFlow plansFlow plansFlow plansFlow plansFlow plansFlow plansFlow plans
      NewNew
      CapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapabilityCapability
      October 2019October 2019October 2019 October 2019October 2019 October 2019October 2019October 2019October 2019October 2019
      14
      AI Builder CapacityAI Builder Capacity AI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder CapacityAI Builder Capacity
      NewNewNew
      Capacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity add-on
      October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019
      15
      Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity Power Apps and Flow Capacity
      NewNewNew
      Capacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity addCapacity add-on
      October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019October 2019
      © 2020 Microsoft Corporation. All rights reserved.
      This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. This information is provided to help guide your authorized use of products you license; it is not your agreement. Your use of products licensed under your license agreement is governed by the terms and conditions of that agreement. In the case of any conflict between this information and your agreement, the terms and conditions of your agreement control. Prices for licenses acquired through Microsoft resellers are determined by the reseller.