Power Apps portals FAQs

We've compiled a list of frequently asked questions and provided brief answers to help you get to your information quickly.


How do I track changes to Power Apps portals configuration?

You can use auditing in Microsoft Dataverse to keep track of changes to Power Apps portals configuration entities. Auditing helps determine the change history if configuration data needs to be reverted.

Does Power Apps portals support TLS 1.2?

Power Apps portals version 8.3 and later supports TLS 1.2.

Which TLS 1.2 cipher suites are supported by Power Apps portals?

Power Apps portals supports the following TLS 1.2 cipher suites as per Microsoft Security Policy to account for multiple clients support. Strongest cipher suites are at the top of the list. This ensures the clients always use the strongest cipher suite that they support from this list while connecting to portals.



You can control the cipher suites when configuring Azure Front Door with portals for edge caching and Web Application Firewall (WAF) capabilities. In that case, ensure you only use the cipher suites supported by Azure Front Door. Also, while custom domain HTTPS settings using Azure portal allows you to choose a default minimum TLS version between 1.0 and 1.2, use TLS version 1.2 for strong ciphers.

How do I redirect a user to a default page after signing in?

You can configure a portal to redirect a user to a default page after signing in. For detailed steps, go to Redirect a user to a default page on sign-in.

For more information on working with Liquid templates, see Work with Liquid templates.

Licensing and provisioning

How do I get a portal subscription?

Power Apps portals are now available as standalone in Power Apps. You no longer need to acquire license to provision a portal. User access to the portal requires license depending on persona type. Read more details at Power Apps portals licensing FAQ.

How do I change the base URL of a portal after it's provisioned?

You can change the base URL of a portal after it's provisioned by following the steps in Change the base URL of a portal.

I'm getting an error that I don't have appropriate license to access this website.

Internal users with Azure Active Directory credentials trying to sign-in without a valid license assigned will see this message on the sign-in page: You don't have a valid license to access this website. Please contact your system administrator.

Users could also see this error if Pay-as-you-go has not been enabled for this environment.

Portal login error

Depending on the purchased SKU type - such as different Dynamics 365 SKUs, Power Apps per app plan or Power Apps per user plan, an administrator will need to either provide an appropriate license to the users, or have appropriate number of app passes available to the environment. For more information about app passes, go to Allocate or change capacity in an environment. Once app passes are allocated to the environment, the portal will have to be restarted for changes to take effect.

For details about licensing of internal users, go to Portal Licensing FAQ.

For details about licensing of internal users using Pay-as-you-go, go to Power Apps per app meter.

For details about use rights to portals for internal users, go to FAQ use rights to portals for internal users and Licensing Guide section Power Apps Portals – Use rights for Internal users.

Are the guest users treated as internal users for licensing?

No. Guest users added for B2B collaboration in the Azure Active Directory won't be considered as internal users, and will require logins. For more information about portal login licensing model, go to the Licensing Guide section Per login model.

Dataverse environment lifecycle

We recently moved our Dataverse environment from one geolocation or tenant to another. How do we handle portals connected to our organization?

When you move your Dataverse environment from one geolocation or tenant to another, associated portals to that organization won't move automatically. Also, since your organization has moved, any portal associated with that organization won't work and will throw an error on startup.

To associate your portal again to relevant organizations:

  1. Reset your existing portal host from the existing geolocation or tenant by following the steps in Reset a portal. This will delete your associated portal resources and the portal URL won't be accessible after the operation completes.

  2. Once your existing portal is reset, go to the new tenant (or to the new geolocation of the existing tenant) and provision a portal available there.

After restoring a Dataverse environment from an old backup, the portal connected to the organization isn't working. How do we fix it?

When a Dataverse environment is restored from a backup, various changes are done in your organization that can break your portal's connection with the organization. To fix this issue:

  • If the organization ID is the same after the restore operation, and portal solutions are also available:

    1. Open Power Apps portals admin center.
    2. Go to the Portal Details tab.
    3. In the Portal State drop-down list, choose Off.
    4. Select Update.
    5. Once the update operation is complete, set the Portal State drop-down list to On and then select Update.

    Your portal will be restarted and a connection will be created with the organization again.

  • If the organization ID is different after the restore operation, or portal solutions are deleted from your organization:

    • In this case, it's better to reset the portal by following the steps in Reset a portal and then reprovision it.

We recently changed the URL of our Dataverse environment and our portal stopped working. How do we fix it?

When you change the URL of your Dataverse environment, your portal will stop working because it can't identify the Dataverse environment URL anymore. To fix this issue:

  1. Open Power Apps portals admin center.
  2. Go to Portal Actions > Update Dynamics 365 URL.
  3. Follow the instructions in the wizard.

Your portal will be restarted and start working again.

Debugging and fixing problems

Performance of basic forms: Actions such as create/update/delete on basic forms take a lot of time to complete or timeout.

This can happen because of multiple reasons - such as depending on your data and customizations done on that table in Dataverse. When troubleshooting such performance related issue on record actions from portals, ensure that there are no synchronous plugins registered on those events that may possibly cause these delays. Wherever possible, try to implement them asynchronously so that they don't hold or delay the transaction.

When accessing my portal, I see a generic error page. How can I see the actual error?

Whenever a server error occurs while trying to render a portal, a generic error page is displayed to end users along with the timestamp and activity ID of the error. Portal administrators can configure their portal to get the actual error details, which are helpful in debugging and fixing issues. To see the actual error:

  • Disable the custom error page on the portal: This will turn off the custom error page and will allow you to see the complete stack trace of any error when browsing to that page. You can disable the custom error by following the steps in Disable custom error.

It's advisable to use this only when you're developing a portal. Once your portal is live for your users, you should enable custom errors again. More information: View portal error logs

  • Enable diagnostic logging: This will allow you to get all the portal errors in an Azure Blob storage account. You can enable diagnostic logging by following the steps in Access portal error logs.

When you enable diagnostic logging, you can search for particular errors that users report by using the Activity ID shown on the generic error page. The Activity ID is logged along with the error details and is useful to find the actual issue.

Portal administration and management

Do portals use any static content from CDNs (Content Delivery Network) that I need to allow-list?

Yes. Power Apps portals uses out of the box portal's static assets from Azure CDN that includes default JavaScript and CSS files for presentation that earlier rendered as part of the portal app. You must allow-list the following CDN URL to render portals successfully:


How do I use a custom login provider on my portal?

Portals supports any custom login provider that provides support for standard authentication protocols. We support OpenIdConnect, SAML2, and WS-Federation protocols for any custom IDP. OAuth 2 is supported only for a fixed set of known IDPs. For more information on how to set up an IDP configuration, see Configure portal authentication.

How do I get new portal releases in my sandbox portal first before it gets applied to production?

Any portal release is done in two phases: early upgrade and general availability (GA). During the early upgrade phase, we only upgrade portals that are marked for early upgrade. To get a new portal release in your sandbox (development or test) environment, you can enable your portal for early upgrade. For information on how to enable a portal for early upgrade, see Upgrade a portal.

How do I use a custom domain name for my portal?

You can enable your portal to use a custom domain name in place of the standard microsoftcrmportals.com domain name. More information: Link your portal to a custom domain

See also