Lost access to devops organization

Question

Hi,

I am the owner of an organization in azure devops, I was renaming the organization and setting up the permissions,

Somehow I lost access to it, I am the global administrator, I tried setting setting permissions on/off for azure devops administrator but still unable to access it. But I am able to access other organization in the account.

Firstly, I was getting no access error, and asked me to raise request, and I did same, and got the email to grant access to the email, but when I tried to login, it showed the same message no access. Later its showing page not found. However the organization still exists.

Answer 1

Hi @Balasubramanian Rajan ,

Thanks for the confirmation, glad the issue is resolved.

Solution:

The organization's settings had external/guest user access disabled by default, which caused to loose the access to it.

It sounds like your Azure DevOps organization ended up “orphaned” when you renamed it and tweaked permissions, so even though you’re a Global Admin you no longer show up as an active Owner or Project Collection Administrator.

Here’s how to get back in:

1. Verify you’re in the right Azure AD tenant • In the Azure portal, use “Directory + subscription” to confirm you’ve selected the same Entra ID tenant that the DevOps org uses. • Open a private/incognito browser and go to https://dev.azure.com/{YourOrganizationName} (use the new name if you renamed it).
2. Claim ownership of the orphaned organization • Make sure your account is a Microsoft Entra Global Administrator and has the Azure DevOps Administrator directory role assigned. • When you sign in to the org URL, you should see a banner or button labeled “Claim ownership” or “Change owner”. • Click it, pick yourself as the new owner, and provide justification. This will re-activate your Owner role.
3. Re-inflate your admin group for safety • In Organization settings > Permissions > Project Collection Administrators, add at least two human accounts (yourself plus a colleague) and a break-glass service account or group synced from Entra ID. • Avoid having only a single Owner or PCA—you’ll thank yourself later if someone loses access again.
4. Verify your URL and browser state • If you renamed the org, double-check you’re using the updated URL (for example, https://dev.azure.com/new-org-name). • Clear cookies or do an InPrivate session to rule out stale authentication tokens.

If you don’t see a Claim ownership option:

Confirm that the previous Owner and all PCA members are truly inactive (disabled or deleted) in your Entra ID tenantonly then does Azure DevOps expose the orphaned-org recovery controls.

Hope this helps!

---

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Use the following checks and recovery steps in order:

1. Confirm the organization still resolves and is not disabled
   • Browse directly to https://dev.azure.com/{orgName}.
   • If only this renamed org fails while others work, the issue is specific to this org’s access/ownership, not the account.
2. Verify sign-in account and UPN
   • Ensure sign-in is with the same UPN that was added to the Azure DevOps organization (for example, ******@contoso.com).
   • If there are multiple Microsoft accounts/Entra accounts with the same email, sign out of all accounts, clear browser site data, then sign in again with the correct UPN.
   • If the org is not connected to Microsoft Entra ID, and the first login used a different account type (personal vs work), have an admin remove and re-add the identity so the correct account type can be used again.
3. Check whether access level or billing changed
   Even as a global admin, Azure DevOps access can be lost if the access level is downgraded or billing moved:
   • Ask another user who still has access (for example, another Project Collection Administrator or the current organization owner) to go to Organization settings → Users and confirm:
     • The identity is present in the org.
     • Access level is Basic or higher, not Stakeholder.
   • If Visual Studio or Azure billing subscriptions were changed or moved, confirm the Azure subscription used for billing is still active and still linked to this organization. If it was removed or expired, re-link or fix billing and then sign in again.
4. Confirm permissions and group membership
   • Have a Project Collection Administrator check Organization settings → Security and ensure the identity is not in a group with explicit deny permissions for the org or projects.
   • For project-level access, check Project settings → Repos/Boards/Pipelines → Security and verify at least Read permissions on the relevant resources.
   • If the Limit user visibility and collaboration to specific projects feature is enabled, confirm the identity is not restricted via the Project-Scoped Users group.
5. Check organization owner and Project Collection Administrators
   • If access was lost while changing ownership or permissions, another Project Collection Administrator can restore permissions or reassign ownership.
   • If the organization has effectively become orphaned (owner and Project Collection Administrators are inactive in the connected Microsoft Entra tenant), Azure DevOps Administrators can claim ownership using the “Resolve inactive organization owner” process.
6. If self-service restore is not possible
   • If no one with Project Collection Administrator access can restore permissions and the org is still reachable (but shows “no access” or “page not found” only for this account), open a support request so Azure DevOps/Azure support can validate tenant and org ownership and help restore access.

---

References:

• Organization FAQs
• User and permissions management FAQs
• Troubleshoot access and permission issues
• Troubleshoot access and permission issues – Common access and permission issues
• Troubleshoot connecting to a project
• Troubleshoot access and permission issues – Determine a user's access level and subscription status
• Troubleshoot access and permission issues – Rules applied to a work item type that restrict select operations
• Lost access to all Repos - Microsoft Q&A
• Can not access Azure - Microsoft Q&A
• Unable to access this even after accesses - Microsoft Q&A
• Severity A Situation - Locked out of global admin account (MFA) - business down - Microsoft Q&A
• Tenant inaccessible due to inactivity - Microsoft Q&A