Hi @Anonymous,
If you would like the user not be able to create App in the environments, then you may remove the user from the Environment Admin and the Environment Maker, only share the App (set with Can use permission) created in the Environments with the user.
Doing in this way would have those users only be able to use the App shared with them, but have no rights to create new app in the corresponding Environments.
For now, permission configured through the environments have two roles:
Environment Admin, Environment Maker.
Please check the Manage security for your environments part in the following article for more details:
Environments administration in PowerApps
"
The Environment Maker role can create resources within an environment including apps, connections, custom connectors, gateways, and flows using Microsoft Flow. Environment Makers can also distribute the apps they build in an environment to other users in your organization. They can share the app with individual users, security groups, or all users in the organization. For more information, seeShare an app in PowerApps.
"
If your company wishes to restrict the use of organizational-only data inside of Microsoft Flow, that is possible through Data loss prevention (DLP) policies.
Data loss prevention (DLP) policies
https://docs.microsoft.com/en-us/flow/prevent-data-loss
Any individual can try out the paid features of Microsoft Flow for 90 days, and incur no costs. However, you can fully manage the assignment of the perpetual paid licenses inside of your organization through the Office 365 admin portal.
For your reference:
https://docs.microsoft.com/en-us/flow/organization-q-and-a
Regards,
Mona
