This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 34%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
Hello, We are unable to perform TFVC check-ins due to deprecated check-in policies.
Error message: "It's not possible to operate with deprecated policies, please see Azure DevOps blog for more information. https://aka.ms/tfvc-policy-blogpost"
Details:
What we already tried:
Error message: "It's not possible to operate with deprecated policies, please see Azure DevOps blog for more information. https://aka.ms/tfvc-policy-blogpost"A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.
Hi @Jinki Lee
Thank you for providing the details and screenshots.
Based on what you've described, this appears to be a project-level TFVC policy configuration issue rather than a client-side Visual Studio issue.
A few observations stand out:
➜ Visual Studio's Check-in Policy tab reports that current and obsolete policies cannot be mixed, which indicates Azure DevOps still detects at least one deprecated policy associated with the Team Project.
➜ Your cleanup utility reports "No check-in policies found", yet the check-in operation continues to be blocked. This suggests that the obsolete policy reference may no longer be visible through the standard policy APIs but is still present in the Team Project metadata.
➜ Since the issue persists after running SetCheckinPolicies(null) and no policies are visible in either Team Explorer or the Azure DevOps portal, this is unlikely to be caused by a local workspace, Visual Studio cache, or client version mismatch.
At this point, I would recommend:
➜ Verifying whether the issue occurs for all users and all workspaces within the affected Team Project.
➜ Testing check-in against a newly created TFVC Team Project to determine whether the problem is isolated to a specific project.
➜ Checking whether any custom or third-party TFVC check-in policies were previously installed and later removed from the environment.
➜ Opening a support request with Azure DevOps Support, as the project metadata may still contain a legacy policy reference that is no longer exposed through the normal management interfaces.
The screenshots strongly suggest that Azure DevOps still believes an obsolete policy exists somewhere in the Team Project configuration even though it is not visible through the current administration tools.
If you can confirm whether the issue affects all Team Projects or only a specific TFVC project, that would help narrow down whether this is a project metadata issue or an organization-wide configuration problem.
If this answer was helpful, please click Accept Answer and consider giving it an upvote.