SharePoint Modern Lists - going to 10% of First Release tenants

There are interesting things going on in regards to Flow and PowerApps and I'd like to share some of my notes, and look for validation. 

1- Flow: I found out that It is fairly easy to control access to Flow. If a user doesn't have the license for 'Flow and PowerApps', s/he can not access to Flow. User will be prompted with a warning that says "The user with object identifier 'SOMEGUID' in tenant 'SOMEGUID' does not have an entitlement to use Power Apps". Licensing give some level of control to usage of Flow, and user can not continue to design surface. Note: Error message probably needs to be cleaned up a bit for clarity. GUIDs scare regular users.

2- PowerApps: This is where things get a little interesting. If a user without a license clicks on Power Apps, s/he gets a bit less gracious error message initially. "Error creating app from data. There was a problem saving your PowerApp to the cloud. Please try again." I am not sure if that initial error message is consistent behavior or it happened once.

However, after clicking CLOSE to this warning, user is presented with the PowerApps design surface and everything continued to function normally. This was a big wow moment for me.

Continuing my tests, I found out that without a Flow & PowerApps license user was able to create a Power App, save and publish it, and later make it public for other users. Please keep in mind, that test user had only "member" level permissions on the site collection, nothing else.

This is the part that's very concerning when you consider a big tenant with thousands of users. If users start building Power Apps that at some point their businesses depend on it (similar to workflows, and workflow solutions) - all of a sudden you can guess the challenge thrown at an IT organization to support these PowerApp solutions created, without any visibility to them. You can see how things will get really hectic, rapidly.

I believe in order to build sustainable solutions, IT organizations need to have some level of control to pace new functions introduced in SharePoint Online to their user base. We have to keep in mind that, although these are fantastic tools to empower users, without proper training and guides, all we are doing is creating an havoc on support teams. We have over and over again proven that providing regular users any level of somewhat complex tool without proper training guide, support expactions and general governance policy, is like handing a kid a loaded gun. It simply isn't good, and no good outcome can be expected out of it.  I believe these new tools (Flow and PowerApps) need proper exposure controls to help IT organizations define the governance framework around them.

If there are controls and I wasn't able to figure them out, I'd like to get more information regarding to them, so that I can plan and pace the exposure by defining a proper governance framework before things get out of control.

PS: I had some difficulty using Chrome as a browser accessing PowerApps, button were not visible. IE functioned properly.