Configuring a Power Page site (formerly called a "Power Portal," or "portal" for short) can be difficult, even for those who are experienced in Power Platform configuration. While a Power Page site is considered an individual, separate app (similar to the way model-driven apps and canvas apps are separate apps from one another), a builder will commonly use two different interfaces for configuration: the Power Page design studio and the Portal Management model-driven app.
It is important to note that, as of the time of this writing, Microsoft is in the middle of its transition from Power Portals to Power Pages, and some outdated terminology may still be present in the Power Platform and Microsoft documentation.
Power Page configuration data
Power Page site configuration data is stored in the Dataverse as records. When a new site is created, the system creates the numerous solutions, tables, and associated records automatically. These records can be edited by a builder via the Power Page design studio or the Portal Management model-driven app.
Because Power Page site configurations are stored as data, solution-based deployment is not available. Microsoft provides documentation that discusses the options for deploying site configurations across environments.
Power Page design studio
The Power Page design studio can be accessed at (for GCC tenants). Similar to Power Apps and Power Automate, you'll be able to choose the environment in the upper right-hand corner of the screen after logging in. Once you are in the correct environment, you'll be able to either create a new Power Page site or edit an existing one.
The design studio provides a builder with a basic WYSIWYG editor for a Power Page site. It can assist you in selecting a site's style (theme, colors, etc.), setting up table permissions, and even modifying related Dataverse data (tables, forms, and views) without having to switch to Power Apps. ()
