Finance | Project Operations, Human Resources, ...

Provisioned environments are not visible to some users in PPAC

(4) Share

Report

Posted on by EK-26061005-0

441

There are two environments which are provisioned for F&O in admin.powerplatform.com, one with developer tools for working with unified developer experience. With an administrative account i have granted Basic user, Basic powerplatform user and System administrator roles to some users in these environments but they can't see the environments in PPAC (Environments can be accessed via F&O client and Visual Studio with these users). What should i do to grant the same rights to these users with the admin account?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

AR-01121610-0 4,967 Moderator on at

Like (0)

Report

Hy,

you need to assign Dynamics 365 Admin or Power Platform Admin role in the Entra ID to administrate UDE environments.

Hope this helps.

Was this reply helpful? Yes No
Jonas "Jones" Melgaard 4,988 Most Valuable Professional on at

Like (0)

Report

I have moved your question from the general forum to the D365 Finance forum, hope you don't mind.

Are these users normal users or guest users you have invited into your tenant? The system administrator role should be enough.

Was this reply helpful? Yes No
EK-26061005-0 441 on at

Like (0)

Report

The Dynamics 365 Admin and Power Platform Admin roles were assigned in the entra id but the environments are still not visible in PPAC. I am a guest user in entra id.

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

The Security cache and the environments displayed in PPAC can be really slow to refresh.

If you go to the environment page either in Admin.powerplatform.com or make.powerapps.com and select the environment from your admin account, or any account that already can see the environment, then copy and share the URL, you may find your users do have access, they just don't see the environments as selectable in the UI yet.

Was this reply helpful? Yes No
EK-26061005-0 441 on at

Like (0)

Report

Hello @Anthony Blake,

I got "Environment not found" error when tried to reach the environment via url.

Was this reply helpful? Yes No
Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

Interesting, I would think Admin should be enough.

Please will you try adding the Role System Customizer? Then retry the URL.

Was this reply helpful? Yes No
EK-26061005-0 441 on at

Like (0)

Report

@Anthony Blake,

System Customizer role in PPAC didn't work either.

The user roles are listed as:

In PPAC environment: Basic User, F&O DevOps Pipeline Manager, System Administrator and System Customizer

In Entra ID: Application Administrator, Application Developer, PowerPlatform Administrator.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,148 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

With a guest user account, you will not be able to see environments in PPAC. You will only be able to use the application and interact with the application data. You will need to use GDAP permissions for managing the environment in another tenant.

See also: Granular delegated admin privileges (GDAP) introduction - Partner Center | Microsoft Learn

1 people found this reply helpful.

Was this reply helpful? Yes No
Jonas "Jones" Melgaard 4,988 Most Valuable Professional on at

Like (2)

Report

@EK-26061005-0 Yep , that's an unfortunate downside of Power Platform—you can only change directories in the Maker portal (Power Apps, not Power Automate), and not in PPAC.

We create dedicated administrative accounts for our vendors that we retain full control over. It's easier for us to maintain, and the management effort is actually lower than what we might have otherwise spent on licensing.

On a side note (and unrelated to your question—possibly even to this forum, so I apologize if that's the case):
Do not, under any circumstances, assign global admin roles (e.g., Power Platform Administrator) to regular accounts in Entra ID—especially not to guest accounts—unless there’s an extremely good reason to do so.

If you absolutely must, implement Azure PIM, so you have at least some control regards to IT audits and in case the account gets compromised.

Was this reply helpful? Yes No