Power Platform Governance: Customize the governance error message

Recently, the Power Platform Product Group added in this great PowerShell capability for managing end user error messages and I feel personally responsible to spread the word on this awesome feature.

If you've ever opened a Power App that wasn't compliant with a data loss prevention policy, you were probably greeted with a generic error message (like below). For the average end user, a generic error message about data loss prevention policies isn't enough information for them to understand what next steps need to be taken in order to fix the issue.

With this new PowerShell capability (documentation), we can start to customize what this error experience is like for our end users.

There are currently two aspects of this error message we can customize: error message details and contact details.

Error message details provides a custom URL for the user to reference when reaching the error screen. You might want to use this to either provide your company's Power Platform FAQ site or even a link to a custom solution that allows users to submit DLP policy change requests. The URL can be enabled or disabled.

Contact details provides the end user with an email address to reach out to with any questions. This could be your Power Platform Admin, help desk, etc. This can also be separately enabled/disabled.

Above: User experience when opening a Power App that has a DLP policy conflict

Below: Maker experience when trying to save/publish a Power App with a DLP policy conflict

This governance message content currently appears in the following experiences:

• User launches a Power App that has a DLP policy conflict
• Make saves a Power App that has a DLP policy conflict
• Maker shares a Power Apps canvas app but doesn't have share privileges
• Maker shares a Power Apps canvas app with "Everyone" but doesn't have privilege to share with "Everyone"

According to the Power Platform PowerShell documentation, this experience will eventually also be included whenever a maker saves a flow that has a DLP policy conflict.

Overall, this capability helps clear the ambiguity around the generic Power Platform governance error messages and I hope to see many admins leveraging this feature.