Identify Microsoft Power Platform environments

Completed

Environments are a vital aspect of securing and managing Power Apps and Power Automate usage. They act as secure containers where apps and flows run. Each app and flow must be associated with an environment, and every licensed user is part of the default environment.

More environments can be created, typically to enable opt-in access. Some organizations choose to rename the default environment as Personal Productivity, indicating its purpose is for building flows that enhance personal productivity.

As an organization evolves, it can set up separate environments for development, testing, and production purposes. This approach aligns app and flow creation with established IT change management requirements.

By default, makers can create environments. However, administrators have the ability to control environment creation and management using the Microsoft Power Platform Admin center, limiting who can create and manage environments. This control helps maintain security and compliance within the organization.

Screenshot of Microsoft Power Platform Admin Center displaying a list of environments including Fundraiser and Contoso (default).

When creating an environment, organizations can choose the region where the environment resides. This choice is important because it allows organizations to store data closer to actual users and to meet and maintain compliance requirements for their company's location. Regions already available to store data include Asia, Australia, Canada, Europe, France, India, Japan, South America, United Kingdom, United States, and US Government (GCC).

Screenshot of Microsoft Power Platform Admin Center displaying a list of environment regions.

Choice of region is also important for analytics because the Microsoft Power Platform isolates analytics through environments. The customer data that is generated in one region isn't allowed to leave that region.