Flow and PowerApps — How to disable?

Flow and PowerApps are built on same platform and as such shares many of the settings. Both of these services are available to any user i.e. users can also signup for these individually. However, for an Office 365 Administrator or specifically, a SharePoint admin, their integration with Modern Lists cause significant concerns if organization is not ready for their roll-out.

As indicated in below screenshot, any user with Contribute rights on List will see Flow on list menu bar as well as individual list item context menu and users with ownership permissions will see PowerApps.




If you want to turn these off, you are out-of-luck as Microsoft has really not made any one-click setting that will make these disappear. In sections below, I have outlined the options available today to disable (hide) these buttons.


Remove plans from License

First option is to remove Flow and PowerApps plan from user license. Doing this will remove the app tiles from App Launcher. However, this setting have no impact on buttons on Modern Lists menu bar.

Disable at Site Collection level

Use the PowerShell below to disable these buttons at each Site Collection level. “DisableFlows” property, hides the Flow button and ‘DisableAppViews’, hides the ‘Create an App’ link. PowerApps, button will still appear though with only one option ‘Customize forms’. Clicking this button takes the user to PowerApps studio which doesn’t load correctly if user doesn’t have any license.

You could use CSOM to disable these services for all sites or use Set-SPOSite –Identity <site url> -DisableAppViews Disabled -DisableFlows Disabled. However, note that this command doesn’t work for Group based sites.

1. Review all your site collections, you would want to exclude the built-in sites such as video portal sites and App Catalog site etc.

2. PowerShell script disables these settings for all sites using STS#0 and BLANKINTERNET#0 templates.

Github: Disable-PowerAppsAndFlowPerSite.ps1

Group based sites

Update Group based site collections using CSOM as above Set-SPOSite command doesn’t work for these.

You can find the CSOM required here.

Data loss prevention policies

Lastly, create a DLP policy in either Flow or PowerApps admin center to prevent the possibility of business data leaking to Internet based services like Twitter.

A single policy applies to both Flow & PowerApps, doesn’t matter which admin center you create it.

Comments

Popular posts from this blog

Hybrid Apps using Cordova/PhoneGap: Ditch JQuery Mobile

SharePoint 2013 Search Service Activation Error

VMWare Workstation - Assign a static IP address