Power Platform Governance and Administration

In the command bar designer, you can define what happens when a command is activated - execute formula or JavaScript.

For visibility, you can only choose between 'Display' or 'Display with condition from formula'. This means that for simple buttons with more complicated display conditions, the entire button must be created using the XRM Toolbox, as the requirements in the visibility rule can only be implemented to a limited extent with Power FX.

This problem would be solved if the visibility could also be defined with Javascript.

Currently, the Power FX function 'User()' is not supported in model-driven apps.

This should also be enabled in model-driven apps so that

• the visibility of buttons can be adjusted based on the logged-in user
• the current user can be automatically written to a field via a button
• ...

Currently invited guest users with a privileged role like Power Platform Administrator, are not able to switch tenants between organisations.

As a workaround we had to create a dedicated Entra ID user and grant Power Platform Administrator to be able to access PPAC space of our org.

This is a feature we would like to add.

Thanks,

Athanasios

It would be useful if we can have JavaScript function to make the form read-only. Currently there is no way to make a form read-only as a work around, we have to disable each fields in the form.

a Power Platform Reader role, similar to Power Platform Administrator role but allows only read/view on all power platform environments

The ability to change the creator is currently not implemented.

Adding this functionality will allow users to better manage their environments over time.

The idea is specifically related to article:

https://learn.microsoft.com/en-us/power-platform/alm/form-alm

(1) It would be great to prevent the unhealthy scenario mentioned in the article. i.e., "it is not a healthy ALM practice to create multiple managed solutions from the development environment where the base solution (Solution A) is in an unmanaged state". A preventive mechanism should be in place to prevent a form to be added to an unmanaged solution if it is already included in another unmanaged solution within the same environment.

(2) The steps described in "Creating a new form and maintaining it using multiple managed solutions" is not a pragmatic solution, as it requires a separate environment to be setup/available just to make sure a change involves removing a field from a form will work in target environment.

A more robust solution without involving another environment would have been more practical.

Per MS' documentation, Power Pages will not accept encrypted SAML assertions from any identity provider -

We are implementing Power Pages in the Azure GCC High environment, and are subject to federal government audits. Right now, this will be a strike against us per NIST 800-53 standards for SAML authentication. I understand this is not on the roadmap for Power Pages, but this will get to be a bigger customer requirement going forward.

Currently, Power Pages Design Studio auto-saves changes to the live website, publishing changes live that are not yet ready! It should not function this way - but should have a clear Save / Publish distinction. Save would store the changes temporarily but not publish, while Publish would make them live.

Design Studio also does not allow you to view version history, track changes and revert to previous versions. This would be a fantastic improvement on a system edited by multiple makers.

It is surprising that we don't have the ability to edit any SEO fields whatsoever from Design Studio. Title and description should be the bare minimum. Other SEO fields like og:image should also be supported and easily editable on the page settings popup.

It should not be required to switch to Portal Management app to do things such as:

• Change the Page Template
• Set page's Publish status, or Access Control
• Edit SEO fields (title, description, image, etc)
• Edit the page's custom CSS / JS

These should be accessible from the Page's Settings field (which currently only shows name and partial URL).