Talk:Azure DevOps Server

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

Microsoft Mid‑importance

	This article is within the scope of WikiProject Microsoft, a collaborative effort to improve the coverage of articles relating to Microsoft on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MicrosoftWikipedia:WikiProject MicrosoftTemplate:WikiProject MicrosoftMicrosoft articles
Mid	This article has been rated as Mid-importance on the project's importance scale.

The Wikimedia Foundation's Terms of Use require that editors disclose their "employer, client, and affiliation" with respect to any paid contribution; see WP:PAID. For advice about reviewing paid contributions, see WP:COIRESPONSE.

Aupsy (talk · contribs) has been paid by Microsoft Corporation. Their editing has included contributions to this article. [1]

Wrong Logo

The logo for this page is incorrect. I'm not sure how to replace it Coyote1982 (talk) 07:20, 12 January 2022 (UTC)[reply]

SVNbridge

I just added a link to SVNBridge in the See Also section, but suspect that this is better placed in the main article. SVNbridge provides a path for Subversion clients, especially on *nix and Mac, to access (read and write) TFS hosted revision control items. EasyTarget (talk) 15:06, 11 May 2009 (UTC)[reply]

SVNBridge doesn't appear notable (nothing in the topic nor googling supports that), and the topic itself appears to have been the work of the developer. Tedickey (talk) 15:14, 11 May 2009 (UTC)[reply]

Architecture - Paragraph 2 "Most activity in Team Foundation Server revolves around a "work item"."

Quote - Architecture P2: "Most activity in Team Foundation Server revolves around a "work item"."

This is not correct - activity in TFS revolves around three distinct functions: Revision Control, work items and project portals. Work items can relate to a change set in the revision control system or documentation on the project portal; but, this is certainly not a requirement - each function can be used effectively independently of each other. —Preceding unsigned comment added by 165.12.252.113 (talk) 23:16, 5 April 2010 (UTC)[reply]

When do we go for TFS?

What is the minimul and maximum requirements that we should optimum for TFS.????

What are the benefits we will get using this tool????( some extent i understood)but still want more clarification  —Preceding unsigned comment added by 121.244.164.137 (talk) 07:03, 7 July 2010 (UTC)[reply]

Tone/content of article seems like a sales pitch

Discussion of TFS capabilities and architecture seems to be dominated by vendor claims. I don't think the article should be dominated by such material. External links to vendor pages would be a better alternative to the present lengthy exposition, and Wikipedia's ends would be better served by more history of the product and (as it becomes available) independent comparison to competing solutions. Hardmath (talk) 02:27, 17 November 2010 (UTC)[reply]

while i wouldn't say it's too much of a venders pitch, it doesn't have the standard Critisms and Comparasion I'ld expect. I think it would benifit greatly from them. --Oxinabox (talk) 03:03, 11 June 2011 (UTC)[reply]

+1 on that one! Also almost all links and reference go to Microsoft's website--MarmotteiNoZ 00:19, 13 September 2011 (UTC)[reply]

I, too, agree. Especially, I'd like to see a comparison of this with Microsoft's OTHER source code control system - Visual SourceSafe, since that article states that Microsoft internally prefers this product over that one. --Eliyahu S ^Talk 05:18, 26 August 2012 (UTC)[reply]

I love the way "gated check-ins" are billed as "unique", this is simply untrue, this concept is a bog standard feature in all code collaboration and ci systems, much like the one in use at wikipedia: https://gerrit.wikimedia.org/ . This tfs article is one long advertisement and really needs some objectivity and qualified contribution, ie. not coming from a ms pr sockpuppet ;) — Preceding unsigned comment added by 80.166.181.62 (talk) 07:22, 9 November 2013 (UTC)[reply]

The section on Architecture contains almost only marketing noise and no real information. The article would be better without it. Mkaama (talk) 03:20, 12 September 2015 (UTC)[reply]

This article is a disgrace to Wikipedia and should be reduced to a stub. It is flooded with marketing terms without giving any accurate information. There is not even a mention of basic version control features like file rename tracking, directory creation history. Mkaama (talk) 04:52, 12 September 2015 (UTC)[reply]

Request for History Section

Would someone please add a section, "History", in similar fashion to page "Microsoft Visual Studio": https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#History

Microsoft Team Foundation Server RTM does not necessarily follow Microsoft Visual Studio RTM. For example, TFS 2015, with a release date of August, 2015, compared with Visual Studio 2015, with a release date of July, 2015. Iokevins (talk) 04:20, 29 April 2016 (UTC)[reply]