Answered

Failed to assign role 0x80050201 in Power Platform Admin Center

(0) Share

Report

Posted on by sbrusse

I'm having issues with assigning a custom security role to a user in Power Platform Admin Center. The security role is part of a managed solution that was deployed from a Development environment to a Acceptance environment. The error message when adding the role to the user is "Failed to assign role XXXX: 0x80050201".

Technical details:
Non success http status code: '401' received from server for OrgId: '2e37fc31-5691-43bb-a8b3-4e526dd6fb73', serviceEndpointId: '6f8b7840-f4f3-ed11-8848-000d3a208059', name: 'TriggerNtoN', retryCount: '0' - [ Timestamp : 9:25 am, 12/9/2025, Session ID: d23157d0-d4df-11f0-8f51-47e1fb057336 ]

I'm only experiencing this issue on my Acceptance environment, not on the Development environment. I have the System Admin role in both environments.

Categories:

Governance & administering

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Suggested answer

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

HI @sbrusse

I am sorry for your hassles. For Roles when you deploy them, you have to make sure that in the secondary environments that the objects they reference exist and that the permissions are identical (or more) than the previous environment.

Since in development you are an Admin its possible you created the role and it has requirements that were are not part of the Acceptance environment.

Make sure to compare tables, connections (if any are shared to it or from it) etc all exist, that the Role itself has the properly assigned permissions (not just from the role, but any security groups etc).

After deployment publish all customizations and then check all the dependencies of that Role in the new environment (click ..., advanced, show dependencies).

Either something is missing, something is broken (connection, connection reference, table, plugin, security group, other roles, base role, any user accounts or service accounts or heck even environment variables) look at them all in Dataverse and make sure they are in all there and in good order. If you have external dependencies you configured in Entra, check that too for that environment.

Note: if you are in a GOV tenant there were outages yesterday so depending on when you deployed it could be that.

1 people found this reply helpful.

Was this reply helpful? Yes No
sbrusse 24 on at

Like (0)

Report
Copy link

Link copied!

Hi @Michael E. Gernaey , thanks for your help.

I'm not in a GOV tenant.

I've checked all custom security roles, tables, connections, connection references that are in my managed solution, but I can't find the cause of the issue. I have 4 custom security roles in my solution, but I'm unable to assign any of these roles to my users.

Some users already have a security role in the environment. Removing the existing role from a user also fails with the same error message.

So, I'm basically stuck here, unable to assign new roles or remove existing roles to my users. Is there some way to troubleshoot this issue to find the reason for the error?

Thanks

Steven

Was this reply helpful? Yes No
Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @sbrusse

If you checked all that and it wasn't the issue then I am at a loss as one of them has to be it, as it its definition a configuration/permission problem, well that is the issue 99% of the time.

If you go look at the role itself in the new environment, what tables are listed as having permissions based on that role? What custom ones versus built in ones?

And when you compare that to what it has in Dev its exactly the same?

Then what I would do is create a new user, only assign them either basic user or nothing but your own role and see if that works. If a user with blank roles isn't able to be assigned your role, then you have to really validate again what tables, what groups everything assigned to that role or is used to create the role as one of them is not correct.

Without seeing your environment that is the only advice I can give you.

2 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

sbrusse 24 on at

Like (0)

Report
Copy link

Link copied!

Hi @Michael E. Gernaey

After contacting Microsoft Support, I was able to solve this issue. There was plug-in (webhook) configured in my environment that was triggered when updating any M-to-M relationship in Dataverse. The webhook was configured with a legacy URL which was not valid anymore, causing the error message, and prevented me from updating the security role.

thanks

Steven

Was this reply helpful? Yes No