Introduction Dynamics 365 Sales, the reigning champ of sales applications, equips any enterprise to increase sales by deeply understanding their client base and their purchasing
This blog post delves into the strategic role of Dynamics 365 project managers, highlighting their responsibilities and daily tasks, including project planning, team coordination, stakeholder
Your comprehensive guide to understanding the functional integrations of Microsoft 365 Copilot into existing Microsoft applications and how this revolutionary AI enabled productivity tool is
This blog serves to give you an in-depth understanding of the role of a Microsoft D365 Supply Chain Management Consultant, from daily duties to the
The modern PowerApps Portal allows an organization to put up a stand-alone website that can target a wide range of user-types. The beauty of a Power Apps Portal is the ability to securely target an authenticated user, and the flexibility of being able to target anonymous users, all in the same product. Along with this versatility, Power Apps portals offer a low code Portal Editor whose interface is incredibly user friendly. This allows for your organization’s portal to be customized and maintained by business proffesionals with little to no developer experience. The other major advantage of creating a portal, is around topic of data. Since the data is all stored in Common Data Service (CDS), it’s centralized and available at your convenience without messy connectors.
Power Apps Portals are built on top of Common Data Service (CDS), meaning, if you don’t currently have an environment with a CDS database, you won’t be able to provision a Power Apps Starter Portal. It’s also important to note that as of late, there can only be one portal of each type and for a language created in an environment. So, let’s take a step back for a moment and take a broader look at the Microsoft Power Platform as an ecosystem.
We know that on the Microsoft Power Platform there are three solutions (Power BI, Power Apps, and Power Automate) that all work together sharing data that is stored in Common Data Service. We can then use data connectors to connect to our Dynamics 365 apps, or to a database (CDS). So as we dig into Power Apps Portals, I want you to keep the image above in mind as it relates specifically to Common Data Service.
Now let’s talk about Power Apps Portals and the architecture and its ability to “connect”. We can only provision one portal typer per Power Apps Environment, but that doesn’t mean that we cannot connect that environment to another database. However, as mentioned above, anytime you need to provision a new starter portal, you’ll need to first create a new environment.
Note: Remember that when portals existed as add-ins in Dynamics 365, the structure was referred to as ADX. So if you come across this prefix on certain items, it’s referring to the legacy structure.
The graphic above only centers in on a portal inside of a Power Apps Environment. But Power Apps can also connect to other databases or data sources. For example, we could connect in Power BI, or Power Automate.
When Microsoft launched Power Apps Portals in October of 2019, they also made the decision to begin referring to Dynamics 365 Portals (legacy version portals) as Power Apps portals as well. One of the major changes that accompanied the naming convention decision was the revamping of the licensing model. In the past, Dynamics 365 Portals were licensed as add-ons to the Dynamics 365 applications. Certain Dynamics 365 application licenses included a default add-on Portal. however, with the October 2019 announcement of Power Apps Portals, Microsoft changed licensing to be based on usage.
If you are just now deploying a Power Apps portal, this won’t make a difference for you. However, if you have existing Dynamics 365 Portal, you can expect to go through a transition period that will be based on your current contract. Once this expires, you will be converted to the new licensing model. Microsoft has recently granted an extension to December 31st, 2020- due to the COVID-19 outbreak. Before diving into the new usage model, I want to give you a visual overview of the general licensing changes.
To summarize, the provisioning method is completely different for portals with capacity-based licenses than for add-on based licenses. The steps you take will be different. Today’s blog post is focused on creating a CDS starter portal.
Now that we have an overview of the changes, let’s dive into the new usage model. The new usage licensing model is based on persona-types that access the portal. A different licensing usage model exists for each persona that Microsoft has pre-determined. They are essentially split into External Users, Authenticated Users and Anonymous Users. What do I mean by an authenticated user versus an anonymous user? I mean that an organization could use one PowerApps Portal to target existing customers, or maybe vendors that current exist in your system, and/or target completely anonymous users (that don’t currently engage with your organization). The authenticated users can register through connectors like LinkedIn, Facebook, Twitter, etc., and then populate through to your system. You could also manually set up an authenticated user through AAD (Azure Active Directory). Here is a basic graphics showing the User Types and their appropriated Licensing Usage Model.
When looking at the ‘per login’ usage model, it’s important to understand the definition of a ‘login’. A log-in can be defined as a sort of “day pass” to the portal. If the external user has already logged into the portal once, log-ins for the rest of that day (24-hour period) will not be billed. It is also important to note that log-ins are specific to portals. So your subsequent log-ins to other portals, even if residing in the same tenant, would be counted an individual logins per portal.
Before configuring a portal, it’s important to understand the different stages it goes through after birth. When you deploy your portal, it will originate as a trial portal. From the date of creation, your free trial will last a full 30 days. After those 30 days are up, you have the option to convert it to a production portal before it enters the “self-destruction” stages.
If you don’t convert your portal to a production portal, you’ll begin to see notifications about your portal expiring. These notifications can be found in the Power Apps Portals Admin Center. If you don’t convert your portal before the 30 day trial expiration, your portal will first go into a suspended state. This means that though you cannot access the portal, you can still convert it to a production portal within the first seven days of its suspension status.
If you still choose to not convert your portal within that seven-day suspension period, your portal will be deleted. The portal data, however, will stay in the Dataverse instance of the environment the portal resides in.
I’ll be walking you through the steps of provisioning a starter portal in an existing environment. If you have not yet created an environment, or would like to work out of a new environment, please create it now. Keep in mind that depending on the environment you select in Power Apps, you can create a CDS starter portal, or a portal in an environment that contains model-driven applications that are a part of Dynamics 365.
1). The first thing we’re going to do is sign into PowerApps by going to to make.powerapps.com
2). Under Make Your Own App, click on Portal from blank
3). At this point you will be prompted to select an environment or create a new one. Enter in a name for your portal and give it a URL and a language preference. When you’re finished filling the information out, select Create to provision the new starter portal. you may have a little bit of time on your hands at this point in the provisioning process. The status of the portal will be display in notifications or in the application grid. Once successful, the status will be updated.
Note: It’s important to keep in mind that a portal is created as a trial by default. There is currently no way to create a portal that does not initiate as a trial. This is Microsoft’s way of offering you 30 days to try out Power Apps Portal capabilities while inflicting zero cost to your organization. After 30 days, the trial will expire and will be suspended and eventually, shut down.
If you decide to keep your portal, you can easily convert it to a productional portal. To do this, you’ll need the administrator role in Power Platform. In order to convert your Power Apps Portal to a production portal, the environment in which you are converting the portal must be a Production Environment as well. In other words, you cannot convert a Power Apps Portal trial to a production portal inside of a Sandbox environment.
Introduction Dynamics 365 Sales, the reigning champ of sales applications, equips any enterprise to increase sales by deeply understanding their client base
This blog post delves into the strategic role of Dynamics 365 project managers, highlighting their responsibilities and daily tasks, including project planning,
Your comprehensive guide to understanding the functional integrations of Microsoft 365 Copilot into existing Microsoft applications and how this revolutionary AI enabled
Discover how Avantiico helps you improve business processes, provide customers with a seamless experience and transform the way you do business.