Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 38 ยท Getting Started

Power Automate Environments, Solutions and the Maker Portal

Understand environments, solutions, publishers, My flows versus Solutions, sharing and ownership, and how to move flows from development to production.

A flow that lives only in My flows is fine for learning, but real work needs structure: separate places for testing and production, a way to move flows between them, and shared ownership. Power Platform gives you environments and solutions for that.

The maker portal

The web home for building is the Power Automate maker portal. Its main areas:

  • Home: shortcuts, learning and recent items.
  • Create: start a flow from blank, a template, a description or a connector.
  • My flows: flows you own, flows shared with you, and team flows (tabs at the top).
  • Solutions: packages of components, covered below.
  • Monitor and Process mining: analytics and insight (premium areas).
  • Connections and Data (under More): saved connections, custom connectors, tables and gateways.

Use the environment picker in the top right to switch environments. Everything you see in the lists belongs to the selected environment.

Environments

An environment is a container for flows, apps, connections and data. Environments have their own security, data and settings.

Environment type Purpose
Default One per tenant; everyone can build here, so it gets messy
Production Real business processes
Sandbox Safe copy for testing; can be reset
Developer Personal playground for one maker
Trial Temporary, expires

Good practice: build in a developer or sandbox environment, then move to production. Keep personal experiments out of the default environment, because that is where every colleague's flows end up.

Dataverse can be added to an environment; many premium features and solutions need it.

My flows versus solutions

A flow created from My flows is a non-solution flow: it belongs to you, cannot be exported cleanly, and is tied to your connections. A flow created inside a solution is a solution-aware flow that can be packaged, versioned and deployed.

Solutions bring several advantages:

  • Export and import the whole package as a .zip.
  • Connection references instead of personal connections, so the target environment maps its own login.
  • Environment variables for values that change per environment (a SharePoint site URL, an email address).
  • Run-only users, child flows, and ALM tooling that only exist for solution flows.
  • Flows can be owned by a service principal or shared team in some setups.

Start every serious flow inside a solution, even if it is small. Moving a flow into a solution later is possible but slower than starting there.

Create a solution

  1. In Solutions choose New solution.
  2. Enter a display name and pick a publisher. The publisher adds a prefix to the names of components. Create one (for example Finance team, prefix fin) instead of using the default publisher.
  3. Select Create, open the solution, then New > Automation > Cloud flow > Automated (or other type).
  4. Add the connection reference or environment variable when asked.

Typical components: cloud flows, connection references, environment variables, tables, apps, custom connectors.

Moving a flow between environments

The pattern is dev, test, prod.

TEXT
Dev environment  --export (unmanaged)-->  Test environment (import)
Test environment --export (managed)-->    Production (import)
  • An unmanaged solution can be edited. Use it in development.
  • A managed solution is locked; the target cannot edit components directly. Use it for production, so changes come only through new versions.

During import, the tool asks you to map connection references to connections and to supply environment variable values.

A stand-in for environment variables

This Python stand-in shows why environment variables help: the flow logic stays the same, only the values change per environment. It is not a real solution package.

Python Stand-in: same flow, different environment values

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Sharing and ownership

Flows are tied to their owner. Think about this before going live.

  • Co-owners can edit and manage a flow. Add at least one colleague as a co-owner of every important flow.
  • Run-only users can run an instant flow, using their own connections or the owner's.
  • When an owner leaves, the flow can break: their connections are disabled with their account. Co-owners can re-assign connections.
  • Administrators can list and take over flows in the admin center.
Python Stand-in: find flows with a single owner

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common mistakes

  • Building everything in the default environment.
  • Leaving personal connections inside production flows.
  • Forgetting to turn the flow on after import. Imported flows often arrive turned off.
  • Hard-coding site URLs and email addresses instead of using environment variables.

More governance ideas appear in Governance and patterns.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is an environment?

    Environments separate resources so that development, testing and production do not mix.
  2. 2. Which flows can be exported and deployed as a package?

    Flows created in a solution can be packaged, versioned and deployed through export and import.
  3. 3. What do environment variables solve?

    Environment variables keep flow logic identical while values change between dev and prod.
  4. 4. Which solution type should go to production?

    Managed solutions are locked, so production changes come only through new versions.

Summary

  • The maker portal is where you create, run and manage flows; the environment picker selects the container.
  • Use developer or sandbox environments for building and production for the real process.
  • Solutions package flows with connection references and environment variables.
  • Always add a co-owner and avoid personal connections in production.

Next: Automated flows and triggers