Reason to choose TFS over Svn/Jenkins/Jira

I'm aware that there are a lot of questions on SO with similar content, but I can assure you that I have read the most of them completely with answers and comments.

My situation is slightly different in means that our company is mostly Java-oriented and thus the standard ALM tool set is already set up:

SVN for Source Control
Jira for task/issue tracking
Jenkins for continuous integration
Now, I run a team of .NET developers and we need to set up something similar for our dev process and the discussion is whether to go separately with TFS or to reuse the existing infrastructure and plug in the .NET projects there as well.

I realize that the biggest pro-TFS argument is good integration with VS, but with our current setup I am wondering if there are some good arguments for not using TFS at all.

Hy there i can see your post and i must say

Integrated Ecosystem: TFS provides an integrated ecosystem for software development, including version control (Git or TFVC), continuous integration and continuous delivery (CI/CD) pipelines, and work item tracking, all within a single platform. This can streamline collaboration and reduce the complexity of managing multiple tools. ADPWorkforceNow

Seamless Integration: Azure DevOps offers seamless integration between its different components. Work items, source code changes, builds, and releases can be linked together, providing end-to-end visibility and traceability.

Work Item Tracking: TFS includes robust work item tracking capabilities that can be customized to match your team's specific processes. It's well-suited for Agile and Scrum methodologies.

Thanks and regards
FranciBaker