No DevOps Access

Question

No DevOps Access

Eric 0

Our Azure tenant with domain wibbis.com has a connected enterprise app for Azure DevOps. The user that created the app was [Email Removed]. This user was inadvertently deleted, so the DevOps account is orphaned. I re-create the user [Email removed], but cannot recover admin role in the DevOps account (https://dev.azure.com/wibbis-dev). Please help

Eric 0 Reputation points

2026-02-24T14:00:25.6133333+00:00

What you are suggesting does not work. The user that created the ADO organization was deleted and re-added. So that user's GUID identifier has changed and they cannot log into ADO. There is one other user in the organization that was added to ADO before the first user was deleted. The second user can log into ADO, but has no authority to add or modify users. So we are stuck
kagiyama yutaka 3,605 Reputation points

2026-02-24T14:15:47.69+00:00

I think that… once the creator acct got wiped the org’s orphaned for real, the re-made user’s GUID is diff so DevOps just wont see u anymore, so log in as a tenant Global Admin and reclaim it thru https://aka.ms/ado-org-admin… it’s the only thing that’s ever bailed me out in this kinda mess, sry…
Pravallika KV 16,945 Reputation points Microsoft External Staff Moderator

2026-02-26T12:40:42.4466667+00:00
@Eric,

Apologies for the delay in response.

It seems the original user who created the Azure DevOps organization was deleted and re-added, causing a GUID change. The second user can log in but lacks admin rights.

First, verify if the second user is an Organization Admin in ADO under Organization Settings => Security => Azure DevOps Administrators. If not, elevate their permissions in Azure Active Directory (AAD) by adding them as an admin under Enterprise Applications => Users and Groups.

If the second user is already an admin in ADO, ensure they’re also added to the Project Administrators group.

If needed, use the Azure DevOps REST API to modify permissions directly.

Authenticate using an existing Service Principal or another high-privileged account.

Use the API to manage users and assign the second user to Azure DevOps administrators or the Project Administrators group.
Pravallika KV 16,945 Reputation points Microsoft External Staff Moderator

2026-02-27T09:27:29.9466667+00:00

@Eric, following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

1 answer

Your answer

Eric 0 Reputation points

2026-02-24T14:00:25.6133333+00:00

What you are suggesting does not work. The user that created the ADO organization was deleted and re-added. So that user's GUID identifier has changed and they cannot log into ADO. There is one other user in the organization that was added to ADO before the first user was deleted. The second user can log into ADO, but has no authority to add or modify users. So we are stuck
kagiyama yutaka 3,605 Reputation points

2026-02-24T14:15:47.69+00:00

I think that… once the creator acct got wiped the org’s orphaned for real, the re-made user’s GUID is diff so DevOps just wont see u anymore, so log in as a tenant Global Admin and reclaim it thru https://aka.ms/ado-org-admin… it’s the only thing that’s ever bailed me out in this kinda mess, sry…
Pravallika KV 16,945 Reputation points Microsoft External Staff Moderator

2026-02-26T12:40:42.4466667+00:00

@Eric,

Apologies for the delay in response.

It seems the original user who created the Azure DevOps organization was deleted and re-added, causing a GUID change. The second user can log in but lacks admin rights.

First, verify if the second user is an Organization Admin in ADO under Organization Settings => Security => Azure DevOps Administrators. If not, elevate their permissions in Azure Active Directory (AAD) by adding them as an admin under Enterprise Applications => Users and Groups.

If the second user is already an admin in ADO, ensure they’re also added to the Project Administrators group.

If needed, use the Azure DevOps REST API to modify permissions directly.

Authenticate using an existing Service Principal or another high-privileged account.

Use the API to manage users and assign the second user to Azure DevOps administrators or the Project Administrators group.
Pravallika KV 16,945 Reputation points Microsoft External Staff Moderator

2026-02-27T09:27:29.9466667+00:00

@Eric, following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

Answer 1

Hi @Eric,

Thanks for reaching out to Microsoft Q&A.

It seems the original user who created the Azure DevOps organization was deleted and re-added, causing a GUID change. The second user can log in but lacks admin rights.

First, verify if the second user is an Organization Admin in ADO under Organization Settings => Security => Azure DevOps Administrators. If not, elevate their permissions in Azure Active Directory (AAD) by adding them as an admin under Enterprise Applications => Users and Groups.
If the second user is already an admin in ADO, ensure they’re also added to the Project Administrators group.
If needed, use the Azure DevOps REST API to modify permissions directly.

Authenticate using an existing Service Principal or another high-privileged account.
- Use the API to manage users and assign the second user to Azure DevOps administrators or the Project Administrators group.

Hope this helps!

Share via

No DevOps Access

1 answer

Your answer