Known issues

Power Pages trial

  • If your administrator disabled the self-service sign-up, you won't be able to sign up for a trial of Power Pages.

  • If your administrator disables site creation for non-administrator–type users in your company, you won't be able to create a website. You'll be redirected to the Power Pages home page in the default environment. You'll have to reach out to your administrator to provide you with an environment that has enough privileges for you to edit an existing site in the environment.

  • If your administrator disables the creation of a trial environment for non-administrator–type users in your company, you won't be able to create an environment. However, you can still create a site inside an existing environment in the tenant, where you have necessary minimum privileges.

  • When you create a site for the first time in a new environment, you won't be able to rename the environment; however, the ability to rename the environment when it's created will be available in a future update.

Pages workspace

  • Buttons added in websites built with the starter template can't be resized.

Modifying the header in Portal Management App

When customizing the header, if someone has modified the Liquid code, these changes must be synchronized. Changes won't reflect in studio until the attribute values in the underlying content snippets are updated to reflect these changes. To resolve this issue, open the Mobile Header content snippet in the Portal Management app and update the source code with the correct attribute values for each snippet as in the example below.

<a href="~/">
    {% if snippets['Logo URL'] %}
        <img src="{{ snippets['Logo URL'] }}" alt="{{ snippets['Logo alt text'] }}" style="width: auto; height: 32px; margin: 0 10px;">
    {% endif %} 
    {% if snippets['Site name'] %}
        <h1 class="siteTitle">{{ snippets['Site name'] }}</h1>
    {% endif %}

Styling workspace

  • The section padding/margin settings feature in the Style workspace won't work for sites built using the starter templates.

Adjusting the background color for your Power Pages site

This known issue applies only to sites created using Power Pages prior to September 23, 2022.

Power Pages themes have been updated to meet the highest visual accessibility standards. To ensure that your existing Power Pages sites created prior to September 23, 2022 adhere to these standards, you'll need to update your theme settings to adjust the background using one of the following options.

Option 1: add a new color to the theme's palette

Add a new color to the theme's palette using the Color Palette in the Style workspace.

Option 2: edit a background on a section of the page

Select the desired color while editing the background on a section in the Pages workspace.

Option 3: modify your theme

Modify the theme in the Style workspace using the following steps:

  1. Select a different theme.

  2. Choose your original theme.

  3. Select Save.

Site visibility

A Power Pages website in private mode won't work when you disable Azure Active Directory authentication. Azure Active Directory authentication is enabled by default when the website is provisioned. Change the site visibility state to public before disabling Azure Active Directory authentication.

Dynamics 365 templates

For limitations related to editing Dynamics 365 templates using Power Pages design studio, see Limitations.

Visual Studio Code extension for Power Pages

  • You man get an error when updating the Power Platform Tools for Visual Studio Code with the error message Cannot install Power Pages generator: spawnSync npm.cmd ENOENT. To resolve the issue, install node.js and restart Visual Studio Code.

  • Two sets of the Power Pages create commands may appear in the menu and won't work if you have both the stable version of Power Platform Tools and the Power Platform Tools [PREVIEW] installed on Visual Studio Code.

    Uninstall the Power Platform Tools [PREVIEW] version to resolve the issue.

General issues

  • You receive the following error message when configuring or using table fields:

    Field Name: You've exceeded the maximum number of X characters in this field.

    This can happen if the referenced field for the table exceeds characters limit mentioned in the error. To increase this limit, go to the Data workspace, select the table, select the field, choose Edit column. In the Advanced options, increase the Maximum character count field value to a higher value. Allowed values: 1 through 1,048,576.

    Fields where limit may need to be increased:

    Table Field Display Name
    Basic Form Settings (adx_settings)
    List View (adx_views)
    Basic Form Metadata Subgrid Setting (adx_subgrid_settings)
    Web Page Copy (adx_copy)
  • The Modified Date for the app might be incorrect because these apps are pre-provisioned apps and could have been provisioned earlier.

  • When you create an environment along with the starter portal, the owner of the site isn't displayed correctly. It's displayed as System.

  • If you're reusing the URL of a recently deleted site to create a new site, it has some delay for runtime to set up. This experience happens because the purge of previous resources would still be in progress and may take from 30 minutes to 1 hour for the new site to set up on Azure. The site will also not be available for editing during this time and may show errors when launched in studio for editing.

  • When switching an environment in Power Apps, the sites within an environment may not show up immediately in Apps or Recent Apps list. This experience happens particularly on environments that are created in a different region than their tenant. The workaround is to use browser refresh or wait for some time for the site to show up in the apps list. You'll be able to view all sites in an environment from the Power Pages home page.

  • If you keep the portal settings pane open in Power Apps home page while resetting the site from the Power Pages hub in the Power Platform admin center, a user sees the "Something went wrong" error message in the portal settings pane, as the site is no longer available.

  • In certain cases, when you create a new site, the styles aren't applied properly to the site, and the website is displayed without the styles when opened through Browse website. This behavior rarely happens and styles can be recovered by restarting the site from the Power Pages hub in the Power Platform admin center.

  • When configuring a basic form using the Portals Management app, the incorrect model-driven form is displayed when rendered as a basic form on a page. This may happen when a model-driven form name is duplicated across different form types (Main, Card, and QuickViewform). Only one form name appears when configuring or creating a basic form for the portal. To resolve the issue, rename or create a copy (with a unique name) of the model-driven form to use when configuring the basic form. When creating a form in Data workspace, you'll only be presented with the Main form.

  • By default, Power Pages sites use the Azure Active Directory Graph API for the portal's Azure app registration which is currently deprecated. Power Pages will use the Microsoft Graph API in a future update, so no administrator intervention is required. If the existing Azure Active Directory Graph API permission is replaced manually using the Microsoft Graph API, it will revert back to the Azure Active Directory Graph API when you Enable or Disable SharePoint integration from the Power Pages hub in the Power Platform admin center.

    Azure AD Graph API configuration.

  • When configuring the Open in New Window setting on the Profile web link, the profile page won't open in a new window. To resolve this issue, update the Header web template by updating the Liquid code in the {% if profile_nav %} section.

    Showing line of code to update in the header web template.


    Make a backup of the Header web template before performing these steps.

    Replace this line of code:

    <a aria-label="{{ | escape }}" href="{{ link.url | escape }}" title="{{ | escape }}">{{ | escape }}</a>

    with this line:

    <a aria-label="{{ | escape }}" {% if link.Open_In_New_Window %} target="_blank" {% endif %} href="{{ link.url | escape }}" title="{{ | escape }}">{{ | escape }}</a>
  • Adding a cloud flow immediately after creating a site results in a failure. To prevent this, wait approximately 30 minutes to 1 hour after you create your site before adding a cloud flow.

Power Apps portals Studio issues


You can edit and design Power Apps portals sites using the new Power Pages design studio. More information: Power Pages design studio and Power Apps portals Studio.

  • If a site has page hierarchy of more than three levels, the pages from fourth level onwards aren't displayed in Power Apps portals Studio.

  • The selected text font size will only be displayed if there's a font size defined specifically for that text. If it's part of the standard HTML tags such as p, H1, H2, H3, and so on, Power Apps portals Studio won't display the font size.

  • Webpage using the Page with side navigation template displays only the link of the pages that existed during the webpage creation. You can update the links on the left side of the page by changing the page template to another template and then back to Page with side navigation.

  • When you delete a webpage, canvas doesn't reflect the updated menu until the next refresh of canvas.

  • Color picker and its related strings are supported only in English.

  • A few template pages on the Employee Self Service portal aren't able to render correct breadcrumb.

  • A few Power Apps portals templates, especially bound to customer engagement apps (such as Dynamics 365 Sales and Dynamics 365 Customer Service), don't have default menu items as per their hierarchy of pages. The reason is that there isn't page order available in all or few of the webpages. Any portal without the display order of webpages will have this issue.

  • An error message is displayed when the page content (page copy) exceeds its limit of 65,536 characters and page summary exceed its default limit of 2000 characters.

  • Navigation menu is only visible on the canvas with a resolution of minimum width of 1600 px.

  • An image uploaded on a page becomes the child of the page. If you delete the page, and use the image on another page, the image won't render on Power Apps portals Studio and website.

  • Form rendering isn't currently supported in Power Apps portals Studio. When you add a form, you must select Browse website to open the website and verify the form.

  • On a text or a section background, if you change the color to No color, Power Apps portals Studio doesn't remove the related attributes such as background color or font color, instead make the values null.

  • In the following scenarios Power Apps portals Studio stops to load and shows the "Sorry, there's a disconnect" error:

    • If the Home page is deleted or disabled for a portal.
    • If a page template related to the Home page or any page is disabled or deleted.
  • Power Apps portals Studio will be unable to load source code of those content snippets that don't have a language assigned in Dataverse.

  • In some instances, the changes for header and footer, either through WYSIWYG experience of Power Apps portals Studio or through the code editor, won't be reflected immediately.

  • If a webpage is assigned the Search template in Power Apps portals Studio, it will show a page with the loader. For this scenario to work, you'll have to create an appropriate site marker for that page.

  • The Default studio template also shows up as an option in page template while creating a new page once it's used in Power Apps portals Studio. Also, this template is only inserted in English language and it doesn't support localization based on default Dataverse or portal language.

  • A list rendered as a calendar control or map isn't configurable through Power Apps portals Studio.

  • The Partial URL field in page properties doesn't accept special characters and it breaks the rendering in the canvas for some time.

  • Upload CSS might fail in scenarios where CSS file name contains special characters or space in the file name.

  • Unpublished webpages don't render in canvas of Power Apps portals Studio.

  • While using Power Apps portals Studio, if your portal base language is different than the browser's language, the new webpages created using the Default studio template will have dummy content inserted in browser's language instead of portal language.

  • Only CSS applied at the root page is displayed in the Theme pane. Although if you try uploading a CSS file with a same name as any other CSS file available in the portal, Power Apps portals Studio asks you to replace that file.

  • Power Apps portals Studio is currently not supported on Safari in Mac operating system and has the following issues:

    • The selection of component isn't correct and hovering on a component provides incorrect target indication.
    • Two or three column sections don't render properly in Power Apps portals Studio but works fine on the website.

More information: Power App portal maintenance and troubleshooting

Power Pages design studio issues

Images not displaying in Power Pages design studio

If third party cookies are disabled in your browser, images won't display in Power Pages design studio. To correct this known issue, you need to enable cookies in your browser.

Here's how to enable cookies if your browser is blocking them:

  1. In the Microsoft Edge window, select More (...) > Settings > View advanced settings.

  2. Scroll down to Cookies, and select Don't block cookies


If you don't want to enable all third party cookies, you can also adjust your browser settings to allow cookies for only [*.] instead.