In the world of Power Platform governance, it is essential for organizations to have strict control over which connectors are allowed and which should be restricted. Many organizations still follow the older approach of classifying connectors as Business and Non-Business to control data loss prevention (DLP) policies.
However, this approach comes with challenges.
In the early days of Power Platform, there was no option to directly block connectors. Organizations had to rely on segregating connectors between Business and Non-Business groups within DLP policies. But with the latest improvements in the platform, Microsoft now allows administrators to explicitly block specific connectors.
Recently, we worked with one of our customers and performed a detailed analysis of their Power Platform usage.
We discovered that several users were actively using Non-Business connectors — assuming that they were safe to use since these connectors were not combined with Business connectors in their flows or apps.
However, the business leadership team expected these connectors not to be used at all — regardless of whether they were combined with Business connectors or not.
This mismatch between expectation and implementation highlighted a governance gap.
Blocking connectors is a powerful control, but it should be implemented carefully:
1. Analyze Before You Block
Perform an in-depth usage analysis of your environment. Understand:
- Which connectors are being used?
- What kind of solutions depend on them?
- Are they critical to any business process?
2. Coordinate with Stakeholders
Communicate with your user base. Blocking a connector without notice can break existing apps and flows. Set up a process to:
- Notify users
- Provide alternatives
- Offer migration support
3. Implement Connector Blocking
Once ready, you can block connectors from the Power Platform Admin Center directly in your DLP policies.
This is far more effective than relying solely on Business/Non-Business grouping — especially for connectors that should not be used in any context.
Here is the snippet from DLP policies:
Thanks for reading and downloading…
Tech Wizard
Tech Wizard 