Data loss prevention enhancements to manage custom connectors seamlessly at the tenant and environment level
Important
This content is archived and is not being updated. For the latest documentation, go to Administer Microsoft Power Platform. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Aug 3, 2021 |
To be announced |
Business value
Significantly reduce admin overhead to manage individual custom connectors at a per environment level one-by-one and help improve the security posture by consistently and proactively applying custom connector classification based on the URL that they connect to. Admins can define custom connector URLs using tenant-level data loss prevention (DLP) policies in order to classify them as Business, Non-Business, or Blocked. All individual custom connectors created within environments covered by the DLP policy will inherit the tenant-level classification (Business, Non-Business, Blocked) of the associated host URL.
Feature details
In 2021 release wave 1, we're providing support to define an ordered access control list in order to classify custom connector host URL endpoints as Business, Non-Business, or Blocked at a tenant level. Wildcard * is supported for pattern matching within host URLs. In addition to pattern matching based capability for customer connectors in tenant level DLP policies, we'll also support individual custom connector classifications for environment-level policies using Power Platform admin center user interface (UI). This will remove the current restriction for custom connectors where their classification in environment-level policies is limited to PowerShell only.
See also
Custom connector parity (docs)