Based on similar issues, the most common causes when repositories disappear in Azure DevOps are:
- The signed-in identity or directory changed
- Being signed in with the wrong identity or tenant can hide organizations and repos.
- Sign out completely, then sign back in with the correct identity:
- Close all browsers.
- Open a private/incognito window.
- Go to
https://aka.ms/vssignoutto sign out. - After redirect to
dev.azure.microsoft.com, sign in again and choose the correct identity/tenant.
- Also verify which account is signed in at https://app.vssps.visualstudio.com/profile/view and select the directory that contains the Azure DevOps organization.
- Access level or permissions changed
- After subscription or billing changes, users can lose access to Azure Repos if their access level is downgraded (for example, to Stakeholder) or repo permissions are removed.
- Ask an organization/project admin to:
- Go to Organization settings → Users and confirm the account has a Basic (or higher) access level, not Stakeholder.
- Go to Project settings → Repos → Security and ensure the account has at least Read (and if needed, Contribute) permissions on the missing repositories.
- Organization/repo moved or renamed
- If the Azure DevOps organization URL, project, or repo was renamed or moved, it can appear as if the repo disappeared when actually it is under a different org/project path. Confirm with an admin whether any structural changes were made.
If the issue is intermittent and previously resolved after support intervention, it is likely related to identity/tenant selection or access configuration rather than a problem with the repo itself.
References:
- Troubleshoot access and permission issues
- Common questions about DevOps Security
- Lost access to all Repos - Microsoft Q&A
- https://learn.microsoft.com/en-us/answers/questions/ask/?wt.mc_id=pcs_inproduct_azportal_caseask&portal=azure&context=sso&source=azure-portal Unable to access this even after accesses - Microsoft Q&A