Learn about Power Automate environments

This article introduces you to Power Automate environments in which you can create, and securely isolate your flows, gateways, connections, and other resources.

You'll learn about:

  • The features that environments provide.
  • Switching between environments.
  • How to create a cloud flow in the right environment.

Environments overview

When you create a cloud flow, you choose an environment to host the flow and the resources the flow uses. You can use separate environments for different scenarios.

Here are a few scenarios for using environments

Scenario Recommendation
You want to create a cloud flow that uses a connection to Microsoft Dataverse. Place your flow and Dataverse into the same environment. This ensures all the data is isolated within that environment (isolation boundary).
You're creating a cloud flow for your Human Resources department. You want to ensure that only users in your Human Resources department have access to the flow. Create an environment and add only the HR users to it. Place the flow and any other resources the flow uses into this environment.
There are users in Europe who use a cloud flow to show SharePoint data. Create an environment in Europe, and then create your flow and the SharePoint connection in it. This Europe environment gives the European users the best performance, since all resources are local to Europe (data locality).

Any appropriately licensed user can create environments in the Power Platform admin center by default, unless the default setting for Who can create production environments has been changed from Everyone to Only specific admins.

For details on how you can create and manage environments, see the administer environments topic.

Switching environments

Power Automate makes it easy to switch between environments. When you switch environments, you see only items that are created in that specific environment; you won't see or have access to items in any other environment.

Here's an example.

You’ve created a cloud flow named NewEmployee in the Human Resources environment. In Power Automate, you open the Sales environment. The NewEmployee flow isn’t listed. To see the NewEmployee flow, open the Human Resources environment. Remember, the same rules apply to any other items you created in the environment, including connections, gateways, flows, and more.

Follow these steps to switch environments:

  1. Sign into Power Automate.

  2. In the top right corner, you will see the environment to which you are currently connected.

    profile image.

  3. Select the environment name. A drop-down list displays all the environments available to you. The environment in which you're currently signed in is checked:

    list of environments image.

  4. To switch to another environment, select that environment in the list:

    select an environment to switch to.

  5. Power Automate switches to the new environment.

Create flows in the right environment

Before you create a cloud flow, select the environment into which you'll add the flow and its resources.


If you create a cloud flow in the wrong environment, you can export it from the wrong environment and then import it into the correct environment. Alternatively, you can delete it from the wrong environment, and then create it in the correct environment.

Consider the following factors when choosing an environment to host your flows:

  • Dataverse is tied to a specific environment. So, if you want to create a cloud flow that uses Dataverse, you must create the flow in the environment that hosts the database.
  • You'll see all environments in which you can edit resources. However, you'll need to ask an administrator to add you as a maker to all environments in which you want to create flows.


You'll always be able to create flows in the default environment.

Next steps