You can define policies in Power Platform Admin to restrict the use of certain connectors, both – prebuilt and custom connectors in the Power Platform.
Setting DLP Policy for Connectors – Blocking connectors
You’ll need to go to Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)
In Power Platform Admin Center, you’ll need to expand the section called as Policies and you’ll find the option called as Data Policies
- In this, you can create Policies for the Connectors which are used in Power Automate / Power Apps
- Once you start to create your Policy, give it a suitable name –
- Next, I’ll get a list all uncategorized Connectors which I can either choose to select and start Blocking them or send them to Business category.
- Let’s say you want to set a policy to restrict certain Actions on the connector called as Power Automate Admins connector. I want to now move this connector to Blocked category.
So, I find the connector, select and and click on Block as shown below.
- Now, I’ll see this connector in the Blocked section.
- For now, I’ll ignore the Custom Connectors because I don’t have any for now.
- And then, proceed further to define the Scope of this policy i.e. on Environment level.
For this example, Add all environments is selected since I want to have this for all environments and not selective ones. Quite self-explanatory.
- Finally, I’ll Create this Policy.
- And you’ll see your Policy created like this –
Now, let’s review how this policy will work.
- Now, in a Flow, I’ll select the Connector for which we’ve set the Policy for. The policy doesn’t hide anything, it let’s you select it first.
- And if you select any Action from the Flow, the Flow Checker indicator will light up indicating an error.
- And if you expand, it’ll state that the connector is not allowed to be used.
This won’t allow you to save the flow, forcing you to revoke the step you have performed.
Blocking selective Actions in Connectors
Given you don’t want to Block the whole connector but want to only restrict selective Actions in a connector, here’s what you can do –
- While we are tweaking our existing policy, let me take a chance to also show you that you can edit the Policy from the List. Select it, and then click on Edit Policy.
- Now, let’s assume our Connector not blocked in the first place and exists in either of the categories i.e. Business or Non-Business.
Find the connector. Then find the three dots and expand the menu to further show Configure connector (preview) and then select Connector actions
Remember, this is in Preview and we’ll need to wait to use it for Production once in GA.
- Now, you can select what all Actions should be allowed and what all shouldn’t be in order to restrict any unwanted operations configured by other Admins.
In this scenario, let’s just allow ‘Disable Flow as Admin‘ action and restrict all other ones.
- Now, the allowed one will not have any issues.
- And the ones we have not allowed, will show the error in the Flow Checker.
Here are some Power Automate posts you want to check out –
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform\
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate