Seeing Environments in PowerApps

(1) Share

Report

Posted on by AH-31052106-0

Hello, I have been troubleshooting access for a D365/PowerApps user. He can log into PowerApps and D365 successfully but not see his own environments. Has an E3 and a Sales Pro license. I am not sure if there is a specific security role that he should have at this point. Any ideas? See attached screenshot, it's the "Build apps with Dataverse (0)" tab.

Thanks!

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Haque 1,729 on at

Like (1)

Report
Copy link

Link copied!

Hi @AH-31052106-0,

Let's first check licensing: Probably, an E3 license plus Dynamics 365 Sales Professional gives access to apps, but not automatically to environments. To see environments, the license must include a recognized Power Platform or Dynamics 365 service plan (troubleshoot).

Second, the environment security group: If the environment is tied to a security group, the user must be a member of that group. Otherwise, the environment won’t appear in their list.

Third, the security roles: Let's make sure, the user needs at least one Dataverse security role assigned in that environment (e.g., Environment Maker, System Administrator, or a custom role), even we have the right license.

Finally, Let's use diagnostics tool: Power Platform Admin Center has a built-in user access diagnostics tool that will flag missing roles or group memberships. You can give a run.

However, I suspect, in your case, the missing piece is almost certainly a security role assignment in the environment. Without it, the user won’t see the environment even though they can sign in.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

deepakmehta13a 310 on at

Like (1)

Report
Copy link

Link copied!
Hi,
This is a common issue often related to how Dataverse "Syncs" users or specific environment-level restrictions. Since he can log in but sees (0) under the "Build apps with Dataverse" tab, it means he hasn't been recognized as a Maker in those environments.

1. The Missing "Environment Maker" Role

Even with a Sales Pro license, a user cannot see an environment in the "Build" tab unless they have been granted permission to create content there.

The Fix: Go to the Power Platform Admin Center > Environments > [Select Environment] > Settings > Users + permissions > Users.

Select the user and click Manage security roles.

Ensure the Environment Maker role is assigned.

Why: Without this role, the environment is hidden from the "Maker" portal (make.powerapps.com) even if they have access to play apps in it.

2. Check the Environment Security Group

If your environments have an Entra ID (Azure AD) Security Group assigned to them, and the user is not a member of that group, they will be completely blocked from seeing the environment, regardless of their licenses.

The Fix: In the Environment settings in the Admin Center, check the Edit button under "Details." If a "Security Group" is listed, verify the user is added to that group in the Microsoft 365 Admin Center.

3. The "Force Sync" (If Roles are already assigned)

Sometimes Dataverse doesn't "know" the user has a license yet. You can force a sync:

Go to the Power Platform Admin Center.

Select the Environment > Settings > Users + permissions > Users.

Click Add user and search for him. This forces Dataverse to re-pull his license and object ID from Microsoft 365.

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated

Was this reply helpful? Yes No
Haque 1,729 on at

Like (0)

Report
Copy link

Link copied!

Hi @AH-31052106-0,

I was following up on this, did you overcome the issue?

Was this reply helpful? Yes No
Suggested answer

11manish 1,185 on at

Like (0)

Report
Copy link

Link copied!
This is typically not a license problem, but a security role or environment access configuration issue.

verify these in order:

User added in Power Platform Admin Center → Environment Users

Assign Basic User or Salesperson role in Dataverse

Assign Environment Maker role

Ensure user is in environment security group (if configured)

Ask user to log out and back in

Was this reply helpful? Yes No