VS 2017 Bug?

In our scenario we had this error in VS2017 when trying to connect to Team Explorer, but it works fine in VS2022. So after exploring a lot, I finally found the problem in our case: we have two different projects, ProjectA, and ProjectB in the collection, and each project has an ACL group with the same name "My Group" (with different IDs). One of them lacks "View Project-level Information".

Because I need to access ProjectA, and the error "TF50309: The following account does not have sufficient permissions to complete the operation (...) The following permission is needed to perform this operation: View Project-level Information" is happening in ProjectA, I reviewed all permissions related to ProjectA.

Then I realized the ProjectB also has the same issue. So I added "View Project-level Information" to Project's B "My Group", and suddenly it started to work in both ProjectA and ProjectB. The access error has gone in VS2017. ✅

Double Check: I removed from ProjectB again, and also ProjectA stop working too. 💥

So IMHO I think the VS2017 is doing a bad permissions join. This was seen in VS2017 versions 15.9.61 and 15.9.68 (latest one).

But as I mention, it doesn't impact Visual Studio 2022.

I think it is not related to the Azure DevOps Server 2019 Server (on Premise)