Dataverse Admin Lockout – Environment Not Visible After Removing System Administrator Role

Question

Hello,

I am facing an issue with Microsoft Power Platform / Dataverse and would like confirmation and guidance.

Environment name: Env-CRM-IA-PFE

Environment type: Developer environment

Users: I am the only user of this environment.

What happened:

While testing custom security roles, I accidentally removed the built-in

“System Administrator” role from my own user account and kept only a custom

role (Data Scientist).

After this change:

• I no longer have permissions to manage users or security roles
• I cannot access solutions (I receive missing privilege errors such as prvReadSolution)
• I cannot reassign the System Administrator role back to myself
• The environment no longer appears in Power Platform Admin Center for my account

Important clarification:

• The environment is NOT deleted
• It does not appear under deleted environments
• All data, solutions, and configurations should still exist
• The issue is caused by missing Dataverse administrative privileges

Current situation:

Because I am the sole user and I no longer have:

• The System Administrator role in Dataverse
• Any Global Admin or Power Platform Admin role in Microsoft Entra

I am fully locked out and cannot recover access on my own.

Answer 1

The environment lockout is caused by Dataverse security role removal and can’t be fixed from inside the environment because no user currently has the System Administrator role or higher-privileged access.

Key points from the platform behavior in the provided context:

1. System Administrator is no longer auto-assigned to tenant admins
   Power Platform admins, Dynamics 365 admins, and global admins are no longer automatically given the System Administrator role in Dataverse environments. They must explicitly elevate themselves to System Administrator in each environment where they need Dataverse-level admin access. Because there is no other admin (Power Platform / Global / Dynamics 365) with Dataverse System Administrator in this environment, there is no built-in automatic recovery path from within the tenant.
2. Environment visibility and missing environments
   The environment not appearing in Power Platform admin center for the affected user is consistent with missing required Dataverse role assignments. When a user lacks the necessary roles, the environment can disappear from the environment list in admin and maker experiences.
   The troubleshooting guidance for missing environments assumes that another admin (Power Platform admin or environment admin with System Administrator) is available to:
   • Check role assignments.
   • Run user access diagnostics.
   • Add or fix user records and roles.
   In this case, there is no such admin with sufficient privileges, so those steps can’t be executed by the locked-out user.
3. Developer environment special behavior
   Developer environments with Dataverse have special user sync behavior where only the initial user is added to SystemUsers. Additional admins often must be explicitly added to the environment to gain full access. With the only user having removed their own System Administrator role, there is no remaining principal with the privileges required to repair access.
4. No self-recovery once all System Administrators are removed
   The guidance for managing high-privileged roles and for troubleshooting user access assumes that at least one System Administrator (or an admin who can elevate to that role) still exists. Once all System Administrator assignments are removed and no other tenant-level admin can elevate, the tenant is effectively locked out of that environment’s Dataverse administration.
5. Required next step: Microsoft support
   When an environment is missing from the list and role assignments and diagnostics cannot resolve the issue, the official guidance is to open a support request so Microsoft can perform backend diagnostics and remediation.
   In this scenario, because:
   • The environment is confirmed not deleted.
   • No user has System Administrator in Dataverse.
   • The only user is locked out of admin capabilities.
   The only supported recovery path is to contact Microsoft support and request environment access restoration. Support can validate ownership/tenant information and then restore appropriate administrative access (for example, reassign System Administrator to the correct user) from the service side.

Practical actions:

1. From a work or school account in the same tenant, sign in to the Microsoft 365 / Azure portal.
2. If any other account in the organization has a Microsoft Entra admin role (Global Admin, Privileged Role Admin, or Power Platform Admin), that person should:
   • Open the Power Platform admin center and verify whether they can see the environment.
   • If they still cannot manage Dataverse roles (due to the System Administrator requirement), proceed to step 3.
3. Create a Power Platform support request for “environment access / admin lockout” and include:
   • Environment identifier or URL (Env-CRM-IA-PFE details).
   • Tenant ID.
   • UPN/Object ID of the user who needs System Administrator restored.
   • Confirmation that the environment is a Developer environment and that the only System Administrator role was removed from that user.
4. Work with Microsoft support to have System Administrator re-assigned to the appropriate user in that environment.

There is no supported in-product method for a user without System Administrator (and without a higher-privileged Entra admin who can elevate) to regain Dataverse admin access on their own. Recovery requires Microsoft support intervention.

---

References:

• Troubleshoot missing environments
• Troubleshoot user access problems for different environments
• Assign a security role to a user
• Power Platform environments overview
• Manage admin roles with Microsoft Entra Privileged Identity Management