Provision a site using the older add-on
Note
- Effective October 2022, Power Apps portals is Power Pages.
- This topic applies to legacy capabilities. For latest information, go to Microsoft Power Pages documentation.
If you have purchased an older site (portal) add-on, and want to provision a portal using the add-on, you must go to the Dynamics 365 Administration Center page and provision the portal.
Note
- To provision a portal, you must be assigned either System Administrator or System Customizer role of the Microsoft Dataverse environment selected for the portal. You must also have the required permissions to create and register an application in Microsoft Entra ID. If you don't have the required permissions, contact the Global Administrator to update your permissions or ask the Global Administrator to provision the portal.
- There can be only one portal of each type and for a language created in an environment. For more information, go to creating additional portals.
- To learn about the roles required to create add-on portals, read Admin roles required for portal administrative tasks.
Provision add-on portal
To provision an add-on portal:
- Create a Power Pages website.
- In the Power Platform admin center, select Convert to Production. The Convert trial to production window will appear.
- Choose the Add-on option and select the Confirm button.
The table below summarizes the features associated with each portal option:
Feature | Customer Self-Service Portal | Partner Portal | Employee Self-Service Portal | Community Portal | Custom Portal |
---|---|---|---|---|---|
World Ready | * | * | * | * | * |
Multi-Language Support | * | * | * | * | * |
Portal Administration | * | * | * | * | * |
Customization and Extensibility | * | * | * | * | * |
Theming | * | * | * | * | * |
Content Management | * | * | * | ||
Knowledge Management | * | * | * | * | |
Support/Case Management | * | * | * | ||
Forums | * | * | * | ||
Faceted Search | * | * | |||
Profile Management | * | * | |||
Subscribe to Forum Thread | * | * | |||
Comments | * | * | * | ||
Azure AD Authentication | * | ||||
Ideas | * | ||||
Blogs | * | ||||
Project Service Automation Integration | * | ||||
Field Service Integration | * | ||||
Partner Onboarding | * | ||||
Portal Base | * | * | * | * | * |
Portal Workflows | * | * | * | * | * |
Web Notifications | * | * | * | * | * |
Microsoft Identity | * | * | * | * | * |
Identity Workflows | * | * | * | * | * |
Multistep Forms | * | * | * | * | * |
Feedback | * | * | * | * | * |
Troubleshoot provisioning
Sometimes the package installation process or URL creation process can error out. In these cases, the processes can be restarted.
If Name-Configuring changes to Name-Provisioning Failed, you need to restart the provisioning process.
Go to the Applications page, and select the portal.
Select the blue pencil button labeled Manage.
Choose one of the following options:
Restart Provisioning: Restarts the installation process with the configuration that was previously defined.
Change Values and Restart Provisioning: Lets you change some of the values before restarting the provisioning process.
If the package installation has failed, the portal administrator page will open without any issues, but navigating to the actual portal URL will show a message Getting set up. To confirm this:
Go to the Solution Management page of the Dynamics 365 Administration Center page and check that the package status is Install Failed.
If the package status is Install Failed, try retrying the installation from the solution page. Also, be sure to check that a system administrator is installing the solution with the default language in Dataverse set to the language the portal should be installed in.
Note
Some solutions have prerequisites for their installation, so an installation will fail if the prerequisites are not met. For example, to install the Partner Field Service for a partner portal, the Partner Portal and Field Service solutions must have already been installed. If you attempt to install the Partner Field Service first, the installation will fail and give you an error message.
Change portal type and audience
After you've provisioned a portal, the option to change the portal audience is disabled.
However, you can change the audience and type of portal after it's provisioned by following the steps in Change the Dynamics 365 instance, audience, or type of portal.
Note
- It's recommended to reset and provision your portal again to change the audience, type of portal, organization, and so on. More information: Reset a portal
- The changing of Dynamics 365 instance is applicable only to the portals provisioned using the older portal add-ons.
Next steps
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for