Azure DevOps - Lost Access to Organisation - 401 - Uh-oh, you do not have access
Hi, I’m the owner of an Azure DevOps organisation I was trying to raise & merge a pull request today and suddenly started getting the following error for the organisation at https://dev.azure.com/phoenix427/
I’ve followed the steps listed in https://learn.microsoft.com/en-us/azure/devops/user-guide/troubleshoot-connection?view=azure-devops but nothing has helped. I’ve also tried logging in via my mobile phone and get the same error message.
Azure DevOps
-
Pravallika KV • 18,850 Reputation points • Microsoft External Staff • Moderator
2026-04-20T03:36:09.85+00:00 Hi @Iain Rowson ,
Thanks for reaching out to Microsoft Q&A.
That 401-error means Azure DevOps no longer sees your identity as having any permissions in the org.
Since you say you were the owner, here’s what you can check further:
- Make sure you’re signing in with the exact UPN that’s listed in the org
- If you use an alias (like a secondary email) it won’t work – you must use the full User Principal Name.
- If you’re a B2B guest, verify you’ve accepted the invite in your home tenant.
- Confirm you’re in the right Azure AD directory
- Go to your profile at https://app.vsaex.visualstudio.com/profile/view and see which tenant you’re in.
- Switch directories if you’ve ended up in the wrong one.
- Sign out everywhere, clear cookies, and try in Incognito/Private mode
- Hit https://aka.ms/vssignout, close all browsers/IDE, clear cookies, then browse to https://dev.azure.com/phoenix427/ directly.
- Check your user listing in the org (from another admin or via the Azure portal)
- In Azure portal > Azure Active Directory > Enterprise applications > Azure DevOps, look for your account under Users and verify you still have Owner or Basic access.
- If someone accidentally removed you, have an AAD Global Admin re-add you as an Azure DevOps Administrator and Owner.
- If the org really is orphaned (all owners/PCA inactive) you can “claim ownership”
- A global administrator in the backing Azure AD tenant can go to Organization settings > Overview in Azure DevOps and click Claim ownership.
References:
- Make sure you’re signing in with the exact UPN that’s listed in the org
-
Pravallika KV • 18,850 Reputation points • Microsoft External Staff • Moderator
2026-04-21T00:41:28.7066667+00:00 Hi @Iain Rowson , Following up to see if the provided answer was helpful. If this answers your query, do click
Accept Answer=>Yes, and upvote it. If you have any further queries do let us know. -
Iain Rowson • 0 Reputation points
2026-04-21T09:15:39.6066667+00:00 Hi Pravallika,
I've just tried the above but have unfortunately had no success:
- Make sure you’re signing in with the exact UPN that’s listed in the org
I've double checked my email address is correct and that I am logging in with the Microsoft account I signed up with - Confirm you’re in the right Azure AD directory When I visit https://app.vsaex.visualstudio.com/profile/view
I can't see the organisation that I am the owner of (https://dev.azure.com/phoenix427/), but I can see a different organisation which I am a member of. The organisation did show on that page for a couple of days after I lost access, but it was just "loading" indefinitely. - Sign out everywhere, clear cookies, and try in Incognito/Private mode
No success there unfortunately, I just get the same error message: - Check your user listing in the org (from another admin or via the Azure portal)
I can't see Azure DevOps listed under Enterprise Applications - If the org really is orphaned (all owners/PCA inactive) you can “claim ownership”
Same as above unfortunately, I can't see Azure Devops under Enterprise Applications
Cheers
Iain
- Make sure you’re signing in with the exact UPN that’s listed in the org
-
Pravallika KV • 18,850 Reputation points • Microsoft External Staff • Moderator
2026-04-21T09:17:36.1633333+00:00 Hi @Iain Rowson , have you tried the same through incognito window?
- Sign out completely from Visual Studio / Azure DevOps profile.
- Retry access using an InPrivate/Incognito browser window and log in only with the intended account.
- This helps rule out cached or token-related issues but will not resolve orphaned organizations.
-
Iain Rowson • 0 Reputation points
2026-04-21T10:37:42.95+00:00 Hi Pravallika, yes, I am getting the same error message after signing out of my VS/ADO profile as well as with a fresh private window in Firefox
-
Pravallika KV • 18,850 Reputation points • Microsoft External Staff • Moderator
2026-04-22T07:08:19.11+00:00 Try these steps once again and let me know if the issue still persists:
- Clear Browser cache (or)
- Try to create a new incognito window and sign in to your organization:
https://dev.azure.com/{organizationName}with the invited account in this incognito window. When the user clicked the email invitation, this will automatically jump to the browser to use the default account cached by the browser to log in to the organization, and this default account could not be the invited account.
-
Iain Rowson • 0 Reputation points
2026-04-22T07:50:24.0133333+00:00 Hi Pravallika, it looks like the issue is still occurring with an incognito window:
Regards
Iain
-
Pravallika KV • 18,850 Reputation points • Microsoft External Staff • Moderator
2026-04-22T08:50:14.8433333+00:00 - Go to Azure DevOps Organizations or click on "here" in the error screenshot
- Sign in with your account (
******@aberdeen.ac.uk). - Look at the list of organizations you have access to. If
phoenix427isn’t listed, you don't have access yet. - If the organization appears but is restricted, click Request Access.
- Add a short note explaining why you need access (e.g., “I need access for the Phoenix427 project tasks”).
- Submit the request. The admin will receive a notification and can approve it.
-
Iain Rowson • 0 Reputation points
2026-04-22T10:23:34.2766667+00:00 Hi, I clicked the "here" link on the error page and my organisation still does not appear on my list of organisations
-
Pravallika KV • 18,850 Reputation points • Microsoft External Staff • Moderator
2026-04-22T14:01:02.5566667+00:00 I have reached out to you over private message, please check and confirm.
Sign in to comment