In plain words
Before you can build anything, you need a place to build it. In Power Platform, that place is an environment. Think of it as your own private workshop. Your tools, your materials and your half-finished projects all stay inside it.
To get that workshop for free, you need the right kind of account. You also need to understand a few words Microsoft uses everywhere: account, tenant, Microsoft Entra ID and environment. This lesson explains each one, then walks you through the setup.
An everyday picture helps. A tenant is like a whole college campus. Entra ID is the campus ID-card office that knows every student and staff member. An environment is one lab room on that campus, with its own door and its own key list. Your account is your personal ID card.
Why it matters
Real companies never build and test in the same place their staff use every day. A broken test app in the live system could stop real work. So they separate work into environments, and they control who gets in with identities and licences.
You will copy that habit from day one. Every lab in this course happens in your own developer environment. You can break things, delete things and try again. Nobody else is affected.
There is a second reason. The exam does not test the sign-up steps, but it does test the ideas behind them. Questions about environments, security and who can access what all build on the words in this lesson.
How it works
1. Two accounts, two jobs. You need two separate identities.
| Account | Example | Used for | Why this one |
|---|---|---|---|
| Personal Microsoft account | An Outlook.com or Hotmail address | Your Microsoft Learn profile, exam booking and certificates | It belongs to you for life. A college email may stop working after you graduate. |
| Work or school account | An address issued by a college or company that runs on Microsoft 365 | The free Power Apps Developer Plan and all the labs | Power Platform needs an organisation identity in Microsoft Entra ID. |
Gmail and other personal addresses cannot sign up for the Developer Plan. If your college email is not on Microsoft 365, follow Microsoft's developer environment guidance to get a test tenant instead.
2. Tenant. A tenant is an organisation's own space in Microsoft's cloud. When a college signs up for Microsoft 365, it gets one tenant. All its users, licences and services live inside it. Two tenants are fully separate, like two different campuses.
3. Microsoft Entra ID. Entra ID is Microsoft's identity service. It used to be called Azure Active Directory (Azure AD). Every tenant has one Entra ID directory. It stores the users and groups and checks passwords when people sign in. Power Platform trusts Entra ID to answer the question "who is this person?"
4. Environment. An environment is a container inside a tenant. It holds apps, flows, agents, connections and, optionally, one Dataverse database. Each environment has its own security. One tenant can hold many environments.
| Idea | Tenant | Environment |
|---|---|---|
| What it is | The whole organisation in Microsoft's cloud | A working area for Power Platform inside that organisation |
| How many | Usually one per organisation | Many per tenant |
| Holds | Users, groups, licences, all Microsoft 365 services | Apps, flows, agents, connections and a Dataverse database |
| Security | Who belongs to the organisation (Entra ID) | Who can make or use things in this specific area (roles) |
| Campus picture | The campus | One lab room |
Every tenant also has a default environment that licensed users can build in. Companies usually add others, such as development, test and production. Lesson 2.6 covers the environment types in detail.
5. Developer Plan versus trial. Microsoft offers two common free ways to try the platform.
| Power Apps Developer Plan | Trial | |
|---|---|---|
| Cost | Free | Free |
| Time limit | No fixed end date while you keep using it | Time-limited, then it expires unless you buy licences |
| Purpose | Learning, building and testing for yourself | Evaluating the product before buying |
| Can run real business work? | No, non-production only | No, it is for evaluation |
| Includes | Power Apps, Power Automate and Dataverse, including premium connectors, in a developer environment | Depends on the product being trialled |
For this course, the Developer Plan is your main home. You can have up to three developer environments. Copilot Studio is licensed separately, so it may ask you to start a Copilot Studio trial. That is expected and fine.
6. The studios. Each product has its own website, called a studio or portal. They all open the same environment if you pick it in the environment picker at the top right.
| Studio | Address | What you do there |
|---|---|---|
| Power Apps | make.powerapps.com | Build canvas and model-driven apps, create Dataverse tables, manage solutions |
| Power Automate | make.powerautomate.com | Build cloud flows, see connectors, check run history |
| Copilot Studio | copilotstudio.microsoft.com | Build, test and publish AI agents |
| Power Platform admin center | admin.powerplatform.microsoft.com | Manage environments, data policies, capacity and settings |
| Microsoft Learn | learn.microsoft.com | Study modules, track progress, book the exam, keep certificates |
Example: Campus Help Desk
Here is how the Campus Help Desk project maps onto these ideas.
- Your college (or your test tenant) is the tenant. Its Entra ID knows you, your classmates and the help desk staff.
- You sign up for the Developer Plan with your college account. Microsoft creates a developer environment for you, for example "Asha's Developer Environment".
- In make.powerapps.com you pick that environment. Later, you will create the Ticket and Category tables here, in its Dataverse database.
- In the same environment you will build the student canvas app and the "Help Desk Staff" model-driven app.
- In make.powerautomate.com, still in the same environment, you will build flows that email staff when a ticket arrives.
- In Copilot Studio you will build the "Help Desk Assistant" agent. It must be in the same environment so it can reach the Ticket table.
- In the admin center you can see your environment in the list, and later look at its settings and data policies.
If everything lives in one environment, every part can find the others. If you build the app in one environment and the agent in another, they cannot see each other's data without extra work.
Common mistakes
- Using a college email for your Learn profile. Your certificates are tied to it. Use a personal Microsoft account so they stay yours after graduation.
- Thinking a tenant and an environment are the same thing. A tenant is the whole organisation. An environment is one working area inside it.
- Building in the wrong environment. Each studio remembers its own choice. Always check the environment picker before you create something.
- Treating the Developer Plan as a free production licence. It is only for learning and testing. Real users doing real work need proper licences.
- Forgetting to sign in. Unused developer environments get disabled. A weekly visit keeps yours active.
What you should have after this lesson
- A personal Microsoft account with a completed Microsoft Learn profile.
- A work or school account signed up for the Power Apps Developer Plan.
- A developer environment that you can select in Power Apps and Power Automate.
- Copilot Studio open in the same environment, with a trial started if it asked for one.
- Your environment visible in the Power Platform admin center.
- A look at the exam sandbox so the question formats hold no surprises.
- Clear answers, in your own words, to: What is a tenant? What is Entra ID? What is an environment?