This guide provides step-by-step instructions to deploy a Power Platform Portal from a local environment using the Power Platform CLI (pac).
Before deploying a Power Platform Portal solution, ensure you have the following installed:
| Tool | Version | Installation Link |
|---|---|---|
| Power Platform CLI | Latest | Install Guide |
- Make sure you have Disabled Enhanced Data Model for your environment in the Power Platform admin center.
- Create an empty website from https://make.powerpages.microsoft.com/. This is required to provide infrastructure for portal data to be imported.
- A Dataverse environment with necessary permissions.
- A Power Platform Service Principal or a Dataverse user account with Solution Import/Export permissions.
- A valid authentication method for
pac auth create(e.g., username/password, client ID & secret, certificate-based auth).
Run the following command to authenticate:
pac auth createpac powerpages upload --path PORTAL_FOLDER_PATH --modelVersion 1After deploying the solution, verify that it is successfully deployed:
pac powerpages listYour solution should be displayed in the list.
- Navigate to ./Portal/ConfigData folder under your Portal solution.
- Create zip archive including:
- data_schema.xml
- [Content_Types].xml
- data.xml (you will find it in the folder indicated by specific language code).
pac tool CMTUsing Configuration Migration Tool which is opened by PAC CLI, import configuration to your environment.
-
Authentication Issues?
- Run
pac auth listto verify authentication. - Use
pac auth delete --index <number>to remove incorrect auth profiles.
- Run
-
Deploy Issues?
- Ensure you have the correct permissions in Power Platform.
- Verify the portal folder path.
- Make sure Enhanced Data Model is Disabled for your environment.
- Disable Enhanced Data Model
- Use Microsoft Power Platform CLI with Power Pages
- Import Configuration Data
If you have any questions, feel free to create an issue in the repository. 🚀