Hi @prathyoo ,
Please take a look at the considerations for custom environments:
- Work with the project teams or business units to establish if they require dedicated development, test, and production environments or if a dedicated development environment and shared test and production environments are more suitable to their use case.
- Consider dedicated environments for critical projects and workloads. Developers have Environment Maker access in the development environment, but only user access in the test and production environments. End users only have end user access to the production solution so no one can modify the production applications.
- Consider sharing test and production environments between important but medium complex apps. Individual projects and business units have their own development environment to protect data, but solutions are deployed to shared test and production environments. Developers are end users in the test environment, and end users only have basic user access to solutions and data in the production environment.
- Work with the business unit to establish which connectors are required and create an exception policy.
- Work with the business unit to establish who will be a maker in this environment, and who will be the environment administrator.
- Each environment consumes 1 GB of data capacity, so manage custom environments wisely.
Refer to:
What Is Power Automate or Microsoft Flow? - Whizlabs Blog
Establishing an Environment Strategy for Microsoft Power Platform | Microsoft Power Apps
Microsoft Power Automate Tutorials || Module 19 : Create and Manage Environments - YouTube
Create a dedicated Custom Connector – Encodian Customer Help
Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
