that usually means the project is still using old/deprecated Azure DevOps branch/check-in policies, and Team Explorer can’t process them anymore. Try updating Visual Studio to the latest version. Older Team Explorer clients can throw weird policy errors when the server/project has newer or changed policy handling.
If updating VS doesn’t fix it, ask the Azure DevOps project admin to review the repo/branch policies and remove any old custom/deprecated check-in policies. Then recreate them using current branch policies in Azure DevOps.
https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies
https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/add-check-policies
So, update the client first, then clean up deprecated policies on the Azure DevOps side.
rgds,
Alex
and “up-vote” wherever the information provided helps you, **this can be beneficial to other community members.