This usually points to an access-level, identity, or permissions issue rather than the repository being deleted, especially since other users can still see and use Repos.
Try these checks in order:
- Verify the signed-in identity
- If the same sign-in address exists as both a work or school account and a personal account, Azure DevOps can sign in with the wrong identity.
- Fully sign out of Azure DevOps:
- Close all browsers.
- Open an incognito/private window.
- Go to
https://aka.ms/vssignout. - Sign in again and select the other identity if prompted.
- This is especially relevant when one identity can access the org but another cannot.
- Check access level in Azure DevOps
- In Organization settings > Users, confirm the account is assigned Basic or higher.
- Users with Stakeholder access can lose access to Azure Repos features.
- If access changed overnight, a subscription or assigned access level may have changed.
- Check repository permissions
- In Project settings > Repositories > Security, verify the account or its group has at least Read permission on the repo.
- If code needs to be pushed, also verify Contribute.
- Project access alone does not guarantee repo access.
- Check whether Repos is disabled for the project
- If the Repos service was turned off at the project level, it won’t appear in the services list.
- Check Project settings > Overview > Azure DevOps services and confirm Repos is enabled.
- Refresh permission state
- If permissions were recently changed, the client might need a refresh to recognize them.
- After confirming access level and repo permissions, sign out and back in again.
- If the account is the only admin and still cannot see Repos
- If the organization or identity state changed in a way Azure DevOps no longer recognizes correctly, this may require Microsoft investigation.
- File a problem report on Developer Community.
The error message:
The Git repository with name or identifier {RepoName} does not exist or you do not have permissions for the operation you are attempting.
fits a permissions or identity mismatch scenario. Since other users still have access, the repo most likely still exists.