PowerApps and Flow are becoming a more integral part of SharePoint Online with the imminent release of Custom Forms with PowerApps and the Flow Launch Panel. Starting in November, these features will no longer be considered as preview features. If you have the Preview Features switch turned off in SharePoint administration center today, you were not seeing the Flow and PowerApps buttons in modern lists and libraries. Once this change goes into effect, the buttons will become available, regardless of the setting: Flow button in modern libraries, and both Flow and PowerApps buttons in modern lists. The change will start with our First Release tenants, and then move forward into the rest of the production in two waves. We hope to complete the change over the month of November. PowerApps and Flow are still working on completing their certification for government and sovereign cloud environments with stricter compliance requirements, and the buttons will continue to remain invisible for these environments, independent of the preview features switch setting.

"So having these features off is not something we want to encourage to keep the product consistent for our users" This is all well & good, but things shouldn't be released & out of preview without the supporting administrative controls to restrict visibility/usage, until our Organisations are ready to do so, in line with our internal & very specific strategies. As a result, our 35k strong userbase will have ability to use tools they are not familiar with, without the correct guidance or best practices, subsequently causing large increases in resources in correcting user errors or addressing design duplications from separate users. We appreciate Microsoft have their own Change Management processes, which are adhered to with preview features then full release gradually over time; there needs to be an understanding that individual business, organisations & specific users within those may have their own Change Management & access policies that are being hindered by Microsoft's lack of understanding for administrative needs.

This is all good news, but for organisations that are not yet ready to roll this feature out to end users, there needs to be a way to hide these buttons on tenant or site collection level. For anyone of the same opinion, please vote up this user voice item to make Microsoft understand the importance allowing their customers to roll out new features in their own pace.

This is absolutely unacceptable for many large tenants including mine. New features are welcome, but this isnt about the features or buttons. Its the ability to control access to an apps that arent ready for prime time. Powerapps isnt even integrated in SP as a form solution yet, flows are still bound by personal execution limits. Microsoft is repeating the same mistakes all over again despite of assurances of not forcing new applications that cant be controlled before adoption. As a member of the CAB forum and ill make sure it gets escalated there as wellProblems:1-Azure AD Conditional access cant target these apps for blocking unautorized access.2- Signup via unlicensed Trial subscriptions cant be stopped to these apps. The trials it seems can even be extended after expiry.3- Anyone - even unlicensed can create Powerapps and publish to the whole org creating clutter and confusion.A solution to either of these 3 problems can grant some degree of control over all this and it seems MS is chosing not to resolve them.

Hi Kerem Yuceturk, thank you for your reply. I see your point but it is simply not rational thinking from Microsoft's side. As much as you want to empower users to get started with these great features, trust me that we as admins are of the same opinion, I really cannot see why it would not be in Microsoft's best interest to also allow your customers to roll them out with the best possible results. Multiple issues occur when end users get access to these tools with no training or applied governance. This just needs planning to remain secure, stable and successful. Just take Craig White's tenant size, and consider all the concerns around data governance when users can hook up their flow to a Twitter connector and send business sensitive data out in cyber space (#confidential). I know this can be controlled but users also needs to be informed and trained. Not to mention the internal support needed to back up the adoption of these tools. So I simply don't buy it. There are already many features and apps that can be controlled from central admin, which is extremely helpful (and essential) to organisations that needs to follow certain internal and external rules and regulations for their environment. Please consider this. We want to give our users all the new tools, but please leave us to option of controlling how and when this done. We do not want to revert back to classic UI to avoid this. Thank you.

Thanks Craig for your reply. It is really bummer!! Most of user base is not tech savvy. We do not want to expose them to PowerApps and Flows until we train them and they are ready. Apart from this, If license is automatically assigned to the user (without Admin's knowledge) then it defeat the purpose of governance. Kerem Yuceturk - How is Microsoft going to solve a problem when we do not want our user to see "PowerApps" and "Flows" button on Modern forms.

PowerApps and Flow buttons are graduating out of preview!

Trevor Seward
MVP
Nov 17, 2017
Kerem Yuceturk Without Flow Plan 2, is there _any_ Enterprise control over what type of data sources one can connect to? Or can I get away with a single Plan 2 license to have that enterprise control? It's really unclear as to what Flow license is included in the E3/E5 plans.
- Kerem Yuceturk
  Microsoft
  Nov 17, 2017
  Hi Trevor Seward, Office 365 administrators can go to Flow and PowerApps admin centers, and can set data policies for the default environment, without requiring a P2 license. You do not need any additional licenses.
  
  You could get P2 licenses to be able to create and manage additional environments, and set policies in those additional environments.
  - Trevor Seward
    MVP
    Nov 17, 2017
    With an E3 license, when I go to https://admin.flow.microsoft.com/environments I'm getting redirected to upgrade my license to manage policies.
VigneshGanesan
MVP
Nov 16, 2017
Hi ,
I would like to know if we set the list /library experience to classic in the list or library settings would I still be able to see the Flow and PowerApps button in the SharePoint list/library despite of the preview feature being enforced now ? Could you please confirm .
- Kerem Yuceturk
  Microsoft
  Nov 17, 2017
  Hi VigneshGanesan, Craig White is correct, these buttons are only available in modern lists and libraries.
- Craig White
  Brass Contributor
  Nov 16, 2017
  They’ll only be available in Modern View
Paul Alvarez
Copper Contributor
Nov 06, 2017
Hello,

Has the "Create Flow on Selected Item" trigger been completed in Flow? That was one that seemed to be a work in progress several weeks ago.

thanks
- Kerem Yuceturk
  Microsoft
  Nov 07, 2017
  Hi Paul Alvarez, Flow launch panel changes have been released to First Release tenants last week.
Craig White
Brass Contributor
Nov 03, 2017
To add further to my points raised above, a generic end user with a free licence also has access to the 'Admin Centre' option within the Flow/PowerApps browsers, so can not only create apps but also provision new PowerApps environments without prior governance or approval.

An Admin Centre should only be accessible by O365 administrators. Why is this not so?
Craig White
Brass Contributor
Nov 03, 2017
"So having these features off is not something we want to encourage to keep the product consistent for our users"

This is all well & good, but things shouldn't be released & out of preview without the supporting administrative controls to restrict visibility/usage, until our Organisations are ready to do so, in line with our internal & very specific strategies.

As a result, our 35k strong userbase will have ability to use tools they are not familiar with, without the correct guidance or best practices, subsequently causing large increases in resources in correcting user errors or addressing design duplications from separate users.

We appreciate Microsoft have their own Change Management processes, which are adhered to with preview features then full release gradually over time; there needs to be an understanding that individual business, organisations & specific users within those may have their own Change Management & access policies that are being hindered by Microsoft's lack of understanding for administrative needs.
Sunny Rajpal
Brass Contributor
Nov 03, 2017
I think this should be security based so that administrator can control who can see these button and who can't.
Jaymin Patel
Brass Contributor
Nov 02, 2017
Does PowerApps and Flow button appears even though user do not have PowerApps\Flows license enabled in our tenant?
- Craig White
  Brass Contributor
  Nov 03, 2017
  Jaymin Patel, when the user clicks on the ribbon icon for PowerApps/Flow, it should open a separate browser tab for the app in question. Once the user logs in with their standard O365 credentials, it will AUTOMATICALLY grant them a free licence.
  
  We just tested this with a dummy account & saw the change instantly in the licencing part of the O365 admin centre for the associated account. Again this is a worry if licences are automatically being applied to users without correct governance applied "on the ground"
  - Jaymin Patel
    Brass Contributor
    Nov 03, 2017
    Thanks Craig for your reply. It is really bummer!! Most of user base is not tech savvy. We do not want to expose them to PowerApps and Flows until we train them and they are ready. Apart from this, If license is automatically assigned to the user (without Admin's knowledge) then it defeat the purpose of governance.
    
    Kerem Yuceturk - How is Microsoft going to solve a problem when we do not want our user to see "PowerApps" and "Flows" button on Modern forms.
Pontus T
Iron Contributor
Nov 02, 2017
This is all good news, but for organisations that are not yet ready to roll this feature out to end users, there needs to be a way to hide these buttons on tenant or site collection level.

For anyone of the same opinion, please vote up this user voice item to make Microsoft understand the importance allowing their customers to roll out new features in their own pace.
- Tami Shaw
  Brass Contributor
  Nov 03, 2017
  It's unbelievable that MS won't empower their customers to control their environment. It's irresponsible - no thought given to training or security concerns; other initiatives that may be a high value priority to the business. It puts teams supporting Office 365 in a reactive position and doesn't set them up for success. I'm sending the user voice link to people in my company to vote.
- Kerem Yuceturk
  Microsoft
  Nov 02, 2017
  Hi Pontus T, we are starting to take big dependencies on Flow and PowerApps: Custom Forms in the PowerApps case, and out of box review/approval flows for lists and libraries on the Flow side. So having these features off is not something we want to encourage to keep the product consistent for our users.
  
  We do appreciate the feedback, and will be watching the discussion under the user voice item to be sure.
  - Rob Bowman
    Iron Contributor
    Nov 06, 2017
    Kerem, based on your statements that PowerApps and Flow are still catching up with meeting all regulatory and security features, dependent or not to the future of SharePoint, the decision to release to a company should be based on the Admins and companies decision, not Microsoft. Some of us are keeping SharePoint on Premise around for just this reason. The decision to "Push" companies keeps our team (a highly regulated Global Financial Firm) continuously explaining situations that we should not have to.

Forum Discussion

PowerApps and Flow buttons are graduating out of preview!

Share

Resources