Check Your Dataverse Environment Before You Build

You sign in to Power Apps and see a name near the top of the page. That name matters: it tells you which separate part of your organisation's Power Apps setup you are working in. Choose the wrong one and you may not see the app or data you expected. Choose the right one without the right permission and the create button may still fail.

First identify that place. Then ask the right person whether you may take one small first step. You do not need to understand Power Platform administration.

Three terms you need before you start

A Power Platform environment is a separate area inside your organisation's Power Apps setup. It contains its own apps, data, connections and permissions. An organisation can have several environments—for example, one for building, one for testing and one used by the live business. An app created in one environment does not automatically appear in another.

Think of environments as separate rooms. Your work account may let you enter more than one room, but that does not mean you are allowed to build the same things in every room.

Dataverse is Microsoft's system for storing business information in tables. This guide is only for an app that will use Dataverse.

A Canvas app is a Power Apps app where the maker arranges the screens and controls. This guide is only for a Canvas app.

This map shows the choices before you begin. The numbered steps below explain each one.

Do not create anything yet. First complete the steps below.

Step 1: write down one small first task

Do this

Write one action you want to take first. It must be small enough for someone to approve on its own.

Use one of these patterns:

• create an empty Canvas app, close it and open it again;
• create one empty table called Courses, close it and open it again;
• create one empty Solution—a container that groups the parts of a Power Apps app—close it and open it again.

Write this down

App name or short label:
What the app is for:
My first task:
What this task will create:
What this task will not do:
Other services it will connect to: NONE / list them
Data used in this first task: MADE-UP DATA ONLY

Made-up data means no real customer, employee, financial, health or confidential information.

If you cannot complete this step

Do not write “start the app”, “test Dataverse” or “see if it works”. Those are too vague for someone to approve. Ask the person requesting the app to choose one small first action. Until that is clear, your answer is CHECK WITH YOUR IT TEAM OR POWER PLATFORM ADMIN.

Step 2: find the environment name shown in Power Apps

Do this

1. Open Power Apps in your browser.
2. Sign in with the work account you would use to build the app.
3. Look along the top of the page, near the right-hand side.
4. Find the environment selector. This is the control that shows the name of the environment you are currently in and lets authorised users switch to another one.
5. Copy the displayed name exactly, including spaces, numbers and punctuation.
6. Do not switch to a different environment just because its name looks more suitable. Wait for your IT team or Power Platform administrator to tell you which one to use.

Microsoft's current instructions place the environment selector near the right side of the page header. Your organisation may give its environments names such as “Default”, “Development” or “Sales”, but a name alone does not tell you what you are allowed to do there.

Write this down

Environment name shown in Power Apps:
Date I checked it:
Work account I used:

If you cannot find it

Write ENVIRONMENT NAME NOT FOUND. If appropriate under your organisation's rules, take a screenshot of the top of the page without exposing private information. Send the request in Step 4 to IT and say that you could not find the environment name.

Do not try to work out the environment's technical settings, what type it is or whether it contains Dataverse. Those are administrator checks in Step 4.

Step 3: find the person who can approve the first task

A Power Platform administrator is the person or team that manages Power Apps settings and access for your organisation. You may not know who this is yet.

Do this

1. Ask your normal IT support team: “Who manages Power Platform environments for our organisation?”
2. Ask them to identify the person or team responsible for the environment name you copied in Step 2.
3. Ask who can give written approval for your exact first task.

The same person may answer all three questions, or your IT team may involve a licensing administrator and an environment owner.

Write this down

IT contact:
Power Platform administrator:
Person or team that approves work in this environment:

If you cannot find the right person

Send the request in Step 4 to your usual IT support address and ask them to pass it to the right team. If your organisation has no IT support address, ask your line manager or the person who requested the app. Do not create anything while the owner is unknown.

Step 4: send one plain-English request

Do this

Copy the message below. Replace the brackets and send it to the contact from Step 3. Ask them to reply beside every numbered line.

One technical term appears in the request. A Managed Environment is an environment where an administrator has turned on extra management features. That setting can affect licence requirements. You do not need to identify or interpret it yourself; the administrator only needs to answer the question.

Subject: Can I take this first step with a Dataverse app?

I want to check one small first task before I build anything.

App purpose: [short purpose]
First task: [copy the exact task from Step 1]

For this guide, the first task must happen in an environment approved for building or testing, not one used for live business work. This is a safety rule for this guide.

If an administrator uses unfamiliar terms

If someone replies only with a role name such as “Environment Maker” or “System Customizer”, ask them to answer line 7 as YES or NO for your exact task. A role name is not a clear answer about what you may do.

Step 5: copy every answer into one record

Do this

When the reply arrives, copy each answer into the record below. Do not improve, shorten or guess an answer.

If a line is blank, indirect or waiting for someone else, write NOT YET KNOWN.

DATAVERSE APP START CHECK

Checked on:
Checked by:

App name or short label:

If the answers conflict

Do not choose the answer you prefer. Send both statements back to IT and ask which one is current. Record NOT YET KNOWN until they resolve it.

Step 6: check that both environment names match

Do this

1. Open Power Apps again with the same work account.
2. Look near the right side of the top header.
3. Copy the environment name shown there again.
4. Compare it character by character with the exact environment the administrator approved.

Record the result

Name shown in Power Apps now:
Name approved by the administrator:
Exact match: YES / NO

If the names do not match

Stop. Do not create anything. Ask the administrator how to switch to the approved environment. If they approve a different environment instead, start a new Dataverse App Start Check for that environment so that all answers refer to the same place.

If the environment name is still not visible, record ENVIRONMENT NAME NOT FOUND, stop, and ask IT to help you identify or select the approved environment. Your decision remains CHECK WITH YOUR IT TEAM OR POWER PLATFORM ADMIN.

Step 7: choose one answer

Use the first rule below that applies.

1. Choose CHOOSE A DIFFERENT APPROACH if Dataverse has not been chosen, the app is not a Canvas app using Dataverse, or the first task cannot use made-up data only.
2. Choose CANNOT USE THIS ENVIRONMENT if the approved environment has no Dataverse database, is used for live business work, the two environment names do not match, your licence does not cover the task, your account may not perform it, current company rules do not allow it or approval was refused.
3. Choose CHECK WITH YOUR IT TEAM OR POWER PLATFORM ADMIN if any answer is NOT YET KNOWN, assumed, out of date, indirect or still waiting for confirmation.
4. Choose READY TO START THE AGREED FIRST STEP only if every answer is current, both environment names match, and you have written approval for the exact first task.

A missing answer is not “probably fine”. Four confirmed answers and one missing answer still mean CHECK WITH YOUR IT TEAM OR POWER PLATFORM ADMIN.

Finish the record

Decision:
READY TO START THE AGREED FIRST STEP
CHECK WITH YOUR IT TEAM OR POWER PLATFORM ADMIN
CANNOT USE THIS ENVIRONMENT
CHOOSE A DIFFERENT APPROACH

Reason for the decision:
Next thing I am allowed to do:

Keep the record inside your organisation. Remove names, private links, screenshots and technical identifiers before sharing it elsewhere.

Step 8: follow the decision

• If your record says READY TO START THE AGREED FIRST STEP, do only the first task written in the record. It is not approval to build the whole app.
• If it says CHECK WITH YOUR IT TEAM OR POWER PLATFORM ADMIN, ask for the missing answer and update the date when it arrives.
• If it says CANNOT USE THIS ENVIRONMENT, stop using that environment for this task. If IT offers another one, begin again at Step 2.
• If it says CHOOSE A DIFFERENT APPROACH, decide what kind of app you are building and where its data will be stored before using this guide again.

If IT says a new environment is needed

Do not create a new environment simply because the current one failed a check. First ask IT whether a suitable building or testing environment already exists. Reusing an approved environment avoids creating another place that someone must own, secure and manage over time.

If none exists, a new environment can keep made-up data and unfinished work away from live business apps. It also gives the work a clear name and owner. That is the reason to create one—not to get around a failed permission or company rule.

Creating an environment does not make the app approved. When the new environment appears, you must repeat the checks in this Briefing for its exact name.

A Developer environment is a personal area for one person's building and learning. A Sandbox is an organisation-owned area for team building and testing, away from live business work. A Trial environment is temporary and has an expiry date. IT must approve which kind fits your work.

For one person's learning or development work

Use this option only when IT has said that your organisation allows personal Developer environments and has approved you creating one for the task in Step 1.

1. Sign in with your work or school account.
2. Open Microsoft's Power Apps Developer Plan page and start the free Developer Plan signup.
3. Complete the signup. Microsoft creates a Developer environment and returns you to Power Apps.
4. Allow a few minutes for the environment to appear.
5. In Power Apps, open the environment selector near the top-right of the page.
6. Look for the newly created Developer environment. Its name will often include your name.
7. Copy the name exactly and send it to IT.
8. Return to Step 2 and complete a new Dataverse App Start Check for that name.

A Developer environment includes Dataverse and is for building and testing. It is not a permanent home for a live business app.

If signup is blocked, the new environment does not appear or you cannot tell which environment was created, stop and ask IT. Organisations can turn off personal Developer-environment creation. Do not use the Default environment as a substitute.

For a team or organisation-owned app

Ask the Power Platform administrator to create or approve the environment. An administrator normally does this in the Power Platform admin center under Manage → Environments → New. The administrator chooses the region, available capacity, access and security restrictions, and how long the environment should exist. These are company decisions; the app maker should not guess them.

Ask for:

• a non-production Sandbox or an approved time-limited Trial environment;
• a Dataverse database;
• the exact environment name and the person or team responsible for it;
• confirmation of whether it is a Managed Environment and whether your licence covers the first task;
• the Trial expiry date, if applicable; and
• instructions for keeping or removing anything the first task creates.

When the administrator sends the exact name, return to Step 2. Start a new record and use that name for every later answer. Do not carry approval from the rejected environment into the new one.

Worked example: the Microsoft 365 LMS Board

LMS means learning management system. This is a fictional example of the same steps, not a design every reader should copy.

1. First task: Create one empty Solution, close it and open it again. It will contain no real learner data.
2. Environment name shown: LMS Build Lab - Development.
3. Request sent: The maker asks IT to confirm that exact environment, Dataverse, licence, permission, company rules and written approval.
4. Administrator reply: Every line is answered for LMS Build Lab - Development; the environment is for building, contains Dataverse and the exact empty-Solution task is approved.
5. Name checked again: The name shown in Power Apps exactly matches the approved name.
6. Decision: READY TO START THE AGREED FIRST STEP.
7. Next action: Create only the empty Solution, then close and open it as agreed.

This does not prove that the maker can create the full LMS, create its six planned tables, use real learner records or release an app. It proves only that the checks are complete for the named first task.

If your app is not an LMS, replace the example task and app purpose with your own. The eight steps stay the same.

What the evidence can and cannot tell you

Microsoft documentation explains where the environment selector appears and how environments, Dataverse, roles and licences work. Reports from Power Apps users show that people do get stuck with wrong environments, missing table controls and confusing permissions.

Neither kind of source can inspect your organisation's setup or approve your work. Only current answers from your own administrators and written approval for the exact first task settle your case.