Effective October 12, 2022, Power Apps portals is Power Pages. More information: Microsoft Power Pages is now generally available (blog)
We will soon migrate and merge the Power Apps portals documentation with Power Pages documentation.
A website is the core table of portals application. A portal application selects a single Website record, and this determines what portal tables such as web pages, web files, web roles, and content snippets are applicable to this application.
With a website providing an application scope, multiple distinct portal applications can be connected to a single organization.
Determination of which website record a given portal application is bound to is usually by the website's name, specified in the configuration of the portal deployment. However, it is also possible to control this by domain name or website bindings.
Websites are created when you create a new portal. However, advanced website management can be performed from the Portal Management app.
When you delete a website record, data related to the website record in portal metadata tables, such as webpages and web links, is also deleted. This is generally the desired behavior, as it means an entire website and all its related data can be removed from an organization in a single operation.
Open the Portal Management app.
Go to Portals > Websites.
To edit an existing website, select the website name.
Enter or edit appropriate values in the fields.
Select Save & Close.
|Name||The descriptive name of the website. This field is required.|
|Default Language||Default language for the selected portal. Before you change the default language, you must:
- Add the language in Microsoft Dataverse environment.
- Add the language in Supported Languages section for Websites record.
|Owner||The owner contact record for the selected Websites record.|
|Primary Domain Name||The primary domain name of the portal to which this website record will be added.|
|Parent Website*||The parent website of the website. This field can generally be ignored, except in certain advanced portal configurations in which a single portal application is bound to one master website at the application root path, with one or more child websites available at specific sub-paths.
* Only for backward compatibility, not to be used for new or existing portals.
|Header and Footer Templates||The Web templates for headers and footers overriding global headers and footers.|
|Supported Languages||The supported languages for the selected Websites record.|
Submit and view feedback for