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. 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 %}
</a> 

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 Microsoft Entra authentication. Microsoft Entra authentication is enabled by default when the website is provisioned. Change the site visibility state to public before disabling Microsoft Entra 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 might 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 might 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.

Microsoft Power Platform CLI for Power Pages

The following known issue applies only to PAC CLI version 1.29.6.

• You might receive the following error message while running Power Pages download or upload command.

Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: <guid>,Exception Type: System.AggregareException  The diagnostics logs can be found at: <Pac installation location>\logs\pac-log.txt

You can open pac-log.txt file and check for MSALCachePersistenceException to see if you are facing this issue

Error: Persistence check failed. Data was written but it could not be read. Possible cause: on Linux, LibSecret is installed but D-Bus isn't running because it cannot be started over SSH. HelpLink Url: Not Provided Stack Trace: at Microsoft.ldentity.Client.Extensions.Msal.Storage.VerifyPersistence0 at bolt.authentication.store.MsalExtensionCache

• You might not see login window when you use pac auth command to connect to your environment

Mitigation: This known issue applies only to PAC CLI version 1.29.6. To resolve the issue, revert to the previous Power Apps CLI version 1.28.3. To uninstall the latest version 1.29.6, see Uninstall Power Platform CLI for Windows and install the previous version 1.28.3 from here.

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.

  

• 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.

  

  Note

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

  Replace this line of code:

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

  with this line:

  <a aria-label="{{ link.name | escape }}" {% if link.Open_In_New_Window %} target="_blank" {% endif %} href="{{ link.url | escape }}" title="{{ link.name | escape }}">{{ link.name | 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 Pages design studio issues

Code components in design studio

Power Pages design studio’s canvas may not render some 3rd party code components. Execution of untrusted scripts in third party code components, page copy, web templates and content snippets are blocked because they can potentially access sensitive user data when rendered in Power Pages design studio.

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:

Microsoft Edge

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

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

Google Chrome

1. In a Chrome window, do one of the following:

   • In the browser address box, enter chrome://settings/content.

     OR

   • On the Chrome menu, select Settings > Show advanced settings, and then under Privacy, select Content settings.

2. In the Content settings dialog box, under Cookies, make sure Allow local data to be set (recommended) is selected.

3. Select Done and refresh the browser.

Note

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

Rich text editor (RTE) control on Power Pages

Only .PNG, .JPG., or .GIF file formats are supported for drag and drop.