Error "environment is linked to a new CDS 2.0 instance" getting environment roles

(4) Share

Report

Posted on by leo85

609

Hi,

I want to restrict creation of apps and flows in an environment (users should still be able to see and run flows). To do this I want to t remove the Environment Maker roles from all users in the environment. Because there are over a thousand users I'm building a flow to do it. At the beginning of the flow, I want to get all users with the Environment Maker role. I'm using the Connector "Power Platform for Admins" and the action "List Environment Role Assignments". When I execute the flow I get an error message:

The environment 'xxx' is linked to a new CDS 2.0 instance. The operation 'GET/PROVIDERS/MICROSOFT.BUSINESSAPPPLATFORM/SCOPES/ADMIN/ENVIRONMENTS/ROLEASSIGNMENTS' is forbidden for linked environments.

This environment used to be our default environment. After some restructuring we set a different environment as the default environment.

What is causing this error and how can I get rid of it?

Categories:

General topics

I have the same question (0)

All responses (6)

Answers (0)

Zrouatbi 21 on at

Like (1)

Report

Hi @leo85

Did you manage to fix this?

I am getting the same error and I have no clue what this error mean.

Thank you

Was this reply helpful? Yes No
VVS_Pothan 3 on at

Like (1)

Report

Hi all,

I'm facing the same issue.
Error: The environment ' ' is linked to a new CDS 2.0 instance. The operation 'GET/PROVIDERS/MICROSOFT.BUSINESSAPPPLATFORM/SCOPES/ADMIN/ENVIRONMENTS/ROLEASSIGNMENTS' is forbidden for linked environments.

Do any one has any resolution?

Thanks in advance

Was this reply helpful? Yes No
FemaleMarvel365 57 on at

Like (1)

Report

I'm Also receiving this same message is there a reason? I see no one has responded to this issue yet.

Was this reply helpful? Yes No
RandomDept 696 on at

Like (1)

Report

Same error, piggybacking to see if there is an update

Was this reply helpful? Yes No
Suggested answer

_daveB 6 on at

Like (2)

Report

Hi,

There is a solution with dataverse tables for this.

To read the roles you can List the User Rows, expand the systemuserroles_Association and the fetch the json-Body. Afer you loop over the users as well as the roles per user in the fetched json to access the roles.

Afterwards you can perform any bound/unbound action with the Microsoft Dataverse connector.

Here it is important to expant the query with "systemuserroles_association". For your use case the filter as well as the row count will look differently.

Then you fetch the response body json from the action before.

Afterwards you are able to loop through every user and the assigned roles to read data:

Afterwards you can perform any actions of the existing data or add some new. I needed to assign Security roles to a User, so here I used the "Relate rows in selected environment" action.

Was this reply helpful? Yes No
Suggested answer

DT-15010503-0 2 on at

Like (0)

Report

I know this is an old post, but it looks like there have been some users (like myself) that are still getting hung up on this error.

After looking into it further, the answer I've come to is that this connector is not designed by Microsoft to be used with environments that are connected to dataverse. https://learn.microsoft.com/en-us/connectors/powerplatformforadmins/#list-environment-role-assignments

It's not spelled out in the documentation, but my guess is because environments without a Dataverse database have only the two roles of Environment Maker and Environment Admin. So the connector is set up to just check those two roles. But environments with Dataverse have theoretically unlimited custom security roles that can be assigned, so the connector is not designed to handle those environments.

As far as a way to get to that role information for those environments with Dataverse, daveB's solution is what I'm going to be implementing.

Was this reply helpful? Yes No