Block Connectors Using New DLP Management Experience

Microsoft has recently released new governance features, in general availability, that allow organizations to better manage their connectors. As part of this new experience, they have provided the ability to block connectors which was not previously available.

Administrators can access this feature by navigating to https://admin.powerplatform.microsoft.com/dlp/. From there, you can edit or create policies. Data Loss Prevention (DLP) policies allow an administrator to place connectors into different data groups. The three options include:

• Business
• Non-business
• Blocked

The idea behind data groups is that you can place connectors within the same data group so they can be used together. This means that a maker can build a flow that includes any number of connectors that belong to the Business data group (or Non-business data group). However, if you try to mix connectors from data groups, that will be a violation and the flow will not be able to be saved or run.

The Blocked data group works differently than the other two data groups. When you place a connector in the Blocked data group, it is not available for use in any flows or apps. If you try to add this connector to a flow, you will receive an error message like the following in the Flow Checker experience.

In addition, Microsoft has provided support for managing the HTTP connectors. Previously, this was something that you needed to use Powershell cmdlets to add them to a DLP policy. Now, HTTP connectors can be managed as part of an out-of-box experience and can be managed just like any other connector.

Conclusion

Governance is important when making transformative tools like Power Apps and Power Automate available to your organization. Microsoft continues to invest in governance experiences so that administrators continue to have control over what their uses have access to.