Share via

cannot see repository in devops

pierre shiraziefard 45 Reputation points
2026-06-01T14:22:35.7066667+00:00

This used to work last month, I do not see the repository anymore. Last time it was a mystery after submitting a support request and then in a few days it started working. Now it's off again.

Azure DevOps

1 answer

Sort by: Most helpful
  1. AI answer

    2026-06-01T14:22:59.2666667+00:00

    Based on similar issues, the most common causes when repositories disappear in Azure DevOps are:

    1. 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:
      1. Close all browsers.
      2. Open a private/incognito window.
      3. Go to https://aka.ms/vssignout to sign out.
      4. 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.
    1. 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.
    1. 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:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.