Power Platform licensing requirements

Power Apps paid plans

The licensing model on this platform depends on the type of connector needed for your data sources. Standard connectors, such as the one used for SharePoint, don’t require an additional license besides Microsoft 365, but premium or custom connectors do require a Power Apps license:

• Per app plan

Allows running one app (canvas or model-driven) or portal per user.

• Per user plan

Allows building and using unlimited apps and portals (within service limits).

• Pay-as-you-go plan

Allows a per user plan that charges for the number of apps or portals runs by a user each month (note that this plan requires an Azure subscription).

To get more insight into the licensing model, please visit https://www.microsoft.com/en-us/power-platform/products/power-apps/pricing/.

Power Automate paid plans

In Power Automate, three licensing plans allow access to data using premium connectors, custom connectors, and on-premises data. The difference lies in the capacity of these plans and who will be the end-user of them:

• There are two user plans: the Power Automate Premium and the Power Automate Hosted Process. Both let you create unlimited flows, including AI builder service credits, but the latter adds unattended robotic process automation in a hosted virtual machine.
• On the other hand, the Power Automate Process licenses a bot that runs unattended robotic process automation.

Using either of these options depends entirely on the analysis of the business process that requires automation. For detailed information about the pricing of these plans, please refer to https://www.microsoft.com/en-us/power-platform/products/power-automate/pricing.

Download the example code files

The code bundle for the book is hosted on GitHub at https://github.com/PacktPublishing/Microsoft-Power-Apps-Cookbook-Third-Edition. We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

Download the color images

We also provide a PDF file with color images of the screenshots/diagrams used in this book. You can download it here: https://packt.link/gbp/9781835465158.

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, and user input. Here is an example: “Repeat step 9 for the Ticket Priority column, using the following choices: Low, Medium, and High.”

A block of code is set as follows:

Filter(
    vw_TicketData,
    customer_id = CustomersCbx.Selected.id
)

Any command-line input or output is written as follows:

Set-ExecutionPolicy -ExecutionPolicy Bypass

Bold: Indicates a new term, an important word, or words you see onscreen. For example, words in menus or dialog boxes appear in the text like this. An example is: “Choose a name, a region close to you, and describe the purpose. For the Type, you can select Production, Sandbox, or Trial”

Warnings or important notes appear like this.

Tips and tricks appear like this.