cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Super User
Super User

URGENT: Ability for Admins to COMPLETELY remove Connectors from an Environment

Please take the time to vote for this idea. 
This is a HUGE deal. PowerApps is at risk of being dropped by big companies if the ability to COMPLETELY REMOVE connectors from ANY environment is not supported. 

https://powerusers.microsoft.com/t5/PowerApps-Ideas/URGENT-Ability-for-Admins-to-COMPLETELY-remove-C...

Don't say I didn't warn ya!

5 REPLIES 5
Community Support
Community Support

Re: URGENT: Ability for Admins to COMPLETELY remove Connectors from an Environment

Hi @ericonline ,

 

Thanks for your feedback and let others who have the same request vote on your idea.

 

Regards,

Mona

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
TopShelf-MSFT Community Champion
Community Champion

Re: URGENT: Ability for Admins to COMPLETELY remove Connectors from an Environment

Thanks for bringing this to our attention @ericonline. This will be reviewed. 

 

@TopShelf-MSFT 

Highlighted
Super User
Super User

Re: URGENT: Ability for Admins to COMPLETELY remove Connectors from an Environment

Thanks @TopShelf-MSFT ,

Please also consider updating the Idea Status from "New" to "Under Review". 

image.png

TopShelf-MSFT Community Champion
Community Champion

Re: URGENT: Ability for Admins to COMPLETELY remove Connectors from an Environment

@ericonline That's not how the ideas board works, but I will get more information for you. 

@TopShelf-MSFT  

CantankerousOne
New Member

Re: URGENT: Ability for Admins to COMPLETELY remove Connectors from an Environment

We have the same requirement but we found a work-around that appears to meet our immediate need (until a better solution comes along). It takes about a day to implement (manually) or it could be scripted: https://docs.microsoft.com/en-us/power-platform/admin/powerapps-powershell

 

The work-around is to create a crap-ton of DLP policies... each with their own connector that would otherwise be deleted or blocked. It doesn't matter which data group you put each connector in but, essentially, one DLP policy per connector works like a jersey barrier between each one. This prevents things like the following scenario:

 

Beth wants to use her personal accounts to move items between her Dropbox and Gmail (both in our no-business-data-allowed data group). The terms "business-data-only" and "no-business-data-allowed" mean nothing (unfortunately) -- they really only act as walled gardens between the two sets. Meaning, by default, Beth can have at it - she can use our company tenant's flow count to conduct her personal business (which, besides being annoying, might also be embarrassing/detrimental to our company if she got caught doing something nefarious).

 

By creating a separate DLP policy for Dropbox and another for Gmail, they become isolated from each other and her flow gets suspended. Again, it doesn't matter which data group I put these in. In my case, I put both in the "business-data-only" group in both policies and not only do they stop working with each other, but none of the other connectors in our main DLP policy for our self-service environment work with any connectors that are "walled-off" in these other DLP policies.  Awkward but it works.

If/when the per-connector block becomes available, we'll switch to that ...hopefully soon. 🙂   Else, we'll just script this and automate it so that new connectors automatically get their own DLP policy until they can be reviewed.

Helpful resources

Announcements
MBAS Gallery 2020

MBAS Gallery 2020

Watch Microsoft Business Applications Summit sessions on-demand.

firstImage

New Ranks and Rank Icons released on April 21!

The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Apps Community!

Top Solution Authors
Top Kudoed Authors
Users online (6,389)