Power pages went GA at Ignite, and amongst the slew of new features, one of the most significant is the new licensing model. The new model not only makes the product cheaper in most cases. It opens the door for new use cases with Power Pages.
Two major updates change how Power Pages/Power Apps Portals have been used in the past.
One of the biggest change is that Power Pages is its product, and With it being its product, It brings less dependency on Power Apps Licensing.
Power Apps Portals have predominantly been used for use cases where users are external to your organization. Power Apps(Canvas & Model Driven ) were primarily used for Internal user use cases. Earlier, even if you built Power Pages for internal users, they would need a Power Apps license.
With the new change, internal and external users fall under the same licensing model. Power pages are viable for many internal use cases, such as Request management/ HR use cases. Many of the HR services are used by employees only a few times a year, and building them on Power pages provides better licensing and customization support.
Since Microsoft acquired the product in 2015, it has continued to evolve the product. Over the course of years, it changed to CRM Portals, to Power Apps portals and now Power Pages. Microsoft’s approach has always been to make it easier for Makers to build and deploy Portals. With Power Pages, the product has really evolved into a true Low Code Maker platform, Power pages are in GA now, and that means you can edit and manage all your existing PowerApps Portals as Power Pages.
Let’s dive into the Power Pages and see what has really changed and how it makes a compelling Platform to build websites:
Power Pages Licensing has been completely revamped, the new licensing model is focused on MAU(Monthly Active Users) vs tracking each login in 24 hours window. The licensing model for external and internal users are same as well as the new license model includes Dataverse and CDN . You can find more details on Power Pages License here, I will post another blog around some of the licensing strategies for Power pages.
In the previous blog we covered how to embed Power BI Report in Power Apps Portal using “Publish to Web” and “Embed for organization” mode, In this post we will cover “Embed for your customers” mode and then applying Row level security(RLS) on the report.
Method 2: Embed for your Customers- Power Bi Report for private customer reports.
Enable Power Apps Portals for Power Bi integration and create your Power Bi report you want to publish under the Power Bi workspace you have defined during Power Bi Setup earlier. Refer the part I blog for steps.
Enable RLS on Power Bi Report:
Enable Report for Row level security by adding role, its required for embedded customers mode to function. On Power Bi Report under Modeling Click on Mange roles
Power BI has become the choice of tool when we talk about Reports, Power Apps portal has built in reporting and charts but if are looking for modern dashboard and reports embedding Power Bi in Power apps portal is the way to go, In this blog we will look into the different ways that could be done,
Before any of this could be done we need to Setup and enable Portal for Power Bi Visualization, here is the detailed steps from Microsoft Documentation for enabling Power Apps portal for Power Bi Visualization and embedded service which allows powerbi liquid tag to work in Portal
Here is the list of Key steps involved, but refer to Microsoft doc for detailed steps