Avoid These Common Power Platform Licensing Errors

The blog post by Alex Shlega [MVP] elucidates common Microsoft Power Platform licensing mistakes and offers insightful advice on how to avoid them. Although the licensing has been clarified over time, it can remain complex and making assumptions can be costly.

For instance, all features within the Power Platform can technically be used but can become expensive, as required licenses are not always inexpensive. The cost of Power pages, Power virtual agents, and usage of restricted tables in Power Apps solutions are described.

The misunderstanding between internal and external users can lead to multiplexing, points out Shlega. Both categories of users need licenses to access Dataverse, and moreover, should be licensed for required applications. Even a company employee interacting with a web site in the "client" capacity could technically fall under multiplexing. It's important to consult Microsoft in ambiguous scenarios.

The author also highlights different authentication methods in Power Pages. Users have to pay per authenticated/unauthenticated user unless Power Pages can recognize such users via Azure AD authentication. Any other authentication methods, like Google or Facebook, will be counted towards Power Pages per-login licensing.

The assumption that the D365 environment requires users to be on D365 licensing is incorrect. Power App users can use these environments and even read from the restricted tables. The D365 licensing guide explains this on page 4.

More General Insights on Power Platform Licensing

In general, understanding licensing can be a complex endeavor. The licensing of Microsoft's Power Platform is no exception and it is crucial to understand its nuances. One of the key aspects is that the cost depends on the chosen features and their application. Also, it's important to differentiate between authenticated and unauthenticated users and methods of authentication, as this impacts licensing cost.

Further, even external access to a service like Dataverse requires a license, a common mistake made by users. The possible complexity around 'multiplexing' and licensing implications highlight the need for external consultation, preferably directly with Microsoft. Accurate understanding and applying these rules can prevent unnecessary expenditure.

In summary, diligence in understanding terms and conditions of any licensing is crucial, more so with complex systems like Power Platform. The author provides valuable insights and a call to read the licensing guide documents while navigating the licensing landscape offering more comprehensive information. You can find more about this in the Pro License explanations.

Read the full article Simple Power Platform licensing mistakes to avoid

Learn about Simple Power Platform licensing mistakes to avoid

Understanding Power Platform licensing can be complex, but avoiding the classic pitfalls is the secret to mastering its nuances. With the objective to not provoke the beast that is licensing, here are a few common miscalculations to circumvent and expand your knowledge on this subject. As we proceed, you will be apprised of any additional occurrences.

One such misconstruction is the notion that any available feature can be utilized. Theoretically, it's true, but practically it could cause a dent in your pocket, as some of the essential licenses come with a hefty price tag. For example, Power pages and Power virtual agents come at costs that escalate according to usage, whereas the use of restricted tables in your solution would require stipulated Power Apps licenses. Links to Power Apps are given for a better understanding.

We then move onto delineating the difference between internal and external users; a concept referred to as multiplexing. Infrastructural users necessitate licenses to access Dataverse, irrespective of how they plan to operate with it. Additional licensing needs to be considered for the necessary first-party applications when using restricted tables. The case of a website that enables users globally to submit customer service cases in your D365 environment serves to elaborate this point.

Different authentication methods in Power Pages is another concept that needs clarity. Payments are designated per authenticated/unauthenticated users, but Power App/D365 licenses could cover this usage. However, that coverage is only extended once Power Pages are capable of recognizing these users, a criterion that can only be fulfilled if the users use Azure AD authentication for login. Use of Google, Facebook or any other authentication method would be extra and counted against power pages per-login licensing.

There is often an assumption that accessing a D365 environment requires the user to be on D365 licensing, but that's not true, at least, as of now. Power App users can utilize those environments and can even extract data from the restricted tables. For better clarity, a quote from the Dynamics 365 licensing guide has been shared.

We also need to remember that speculating license rules based on guesswork can lead to errors. Ideally, you should refer to the guides by googling the terms "D365 licensing guide" and "Power Apps licensing guide". These documents will provide detailed licensing guidelines. It might seem like a daunting piece of literature, but they are rich sources of knowledge that can guide you in the right direction.

Make sure to check out the links to the D365 and Power Platform licensing guide, along with upcoming Power Platform Chat sessions and newly available e-books. This post aims to safeguard you from making costly mistakes, but if you stumble upon a new one, don't forget to share it so everyone can learn.

More links on about Simple Power Platform licensing mistakes to avoid

Simple Power Platform licensing mistakes to avoid

Mar 18, 2023 — If you have Power Pages, you pay per authenticated/unauthenticated users, but Power App / D365 licenses may cover that kind of usage. It will ...

7 Mistakes To Avoid When Creating A Power Platform ...

Feb 26, 2023 — 1. Picking The Incorrect Region · 2. Choosing The Wrong Environment Type · 3. Forgetting To Enter An Environment URL · 4. Failing To Apply A ...

Keywords

Power Platform licensing, avoid licensing mistakes, Simple Power Platform, Power Platform errors, Power Platform tips, licensing errors, Power Platform guidance, prevent licensing mistakes, Power Platform license missteps, best Power Platform practices