Ok there is a solution -- plus I have additional information regards to error in visual studio when attempting to connect to your azure devopos repo and get an error "We could not refresh your credentials"enter image description here

With the above issue regarding invites not being sent -- Yesterday as mentioned, a new organization was created, users added and invites sent out which were not received -- Attempting to login to azure devops yesterday was denied -- As of today, 12hrs + later, I still had not received invite, however attempted to log in and was granted access -- Not sure if a fluke, definitely a bug in Azure Devops.....

Regards the second issue relating to the picture above -- Cloning a repo in visual studio is generally pretty straight forward, Team Explorer -> Connect to Project. If you're already signed into account you should see a list of servers available with associated repos -- another bug from Azure Devops & VS, is if / when servers are not found you can enter in the url directly, however this will result in an error advising to select an account from the dropdown list which will inevitably advise you no servers were found.

Solution := Don't muck around using VS, open a git bash, create a dir where proj should live then cmd git clone < link to repo > which will force git credential manager to ask for a PAT.

DONT waste your time trying to remove cred's from windows cred manager.