Govern SharePoint Custom Forms with a Dedicated Power Platform Environment
Diesen Beitrag auf Deutsch lesen
Custom SharePoint forms are canvas apps in disguise. A dedicated production environment and the SharePoint Custom Form Maker role improve discovery and control.
TL;DR
Power Apps custom SharePoint forms are stored in the default environment unless admins assign a dedicated environment with Set-AdminPowerAppSharePointFormEnvironment. The environment must be production, have Dataverse storage enabled, and enable Dynamics 365 apps so admins can install the SharePoint Custom Form Maker role.
Original by Michael Roth, on MichaelRoth42 Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Treat a customized SharePoint form as a governed canvas app because it can contain Power Fx, lookups, validation and flows.
- Admins/CoE: Assign a dedicated production environment and set it as the default for future custom forms so they are easier to find and manage.
- Security/Compliance: Grant the SharePoint Custom Form Maker role and review permissions because SharePoint and Power Apps permissions can differ.
Frequently asked questions
Where are Power Apps custom SharePoint forms stored by default?
Custom SharePoint forms are stored in the default environment unless an administrator assigns another environment for future forms.
What does the SharePoint Custom Form Maker security role allow?
The role lets users create, edit and use custom SharePoint forms without granting rights to create other apps or flows.
How can administrators move existing custom SharePoint forms out of the Default environment?
Administrators can use the open source FlowPowerAppsMigrator tool to move existing custom forms and flows between environments.