Every category where a model named Azure Repos for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Source control hosting	Developer platform	0%	7 of 23	0%	13	accepted challenger

Movement

This is the first edition on this tier, so no move can be computed for Azure Repos yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Azure Repos across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Alternative	Mention	Labels
Claude Haiku 4.5	0	0	0
GPT-5.4 mini	0	1	1
Gemini 3.5 Flash	0	0	0
Perplexity Sonar	1	0	1
Grok 4.1 Fast	1	0	1
Mistral Small	1	1	2
DeepSeek V4 Flash	3	0	3
Llama 4 Maverick	1	1	2
Qwen 3.7 Flash	0	0	0
Kimi K2	1	1	2
GLM 4.7 FlashX	0	0	0
MiniMax M2.5	0	1	1

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct2 labelsNone

Paraphrase0 labelsNone

Comparative16 labelsNone

Budget-constrained0 labelsNone

Scale-constrained6 labelsNone

Negative8 labelsNone

First choiceAlternativeMentionNegative32 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“Azure DevOps/Repos — if you're a Microsoft/Azure shop; scales to 10,000+ users; TFVC option.” DeepSeek V4 Flash · Source control · scale prompt · alternative

“Azure DevOps Repos is integrated within Azure DevOps and is ideal for Microsoft-stack teams” Llama 4 Maverick · Source control · comparative prompt · alternative

“best for Microsoft-centric teams ... Watch out: Less relevant if you're cloud-agnostic” DeepSeek V4 Flash · Source control · direct prompt · alternative

“Microsoft-heavy environment, existing Azure usage | Azure DevOps Repos” Kimi K2 · Source control · scale prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as Azure Repos, over the 32 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Azure Repos was named but was not.

ProductSame answerTook the first choice insteadHead to head

GitHub32 of 3222Not in the top three

Bitbucket32 of 320Not in the top three

GitLab31 of 3211Not in the top three

AWS CodeCommit19 of 320Not in the top three

Gitea12 of 321Not in the top three

Perforce Helix Core9 of 320Not in the top three

Gitea/Forgejo6 of 320Not in the top three

Forgejo5 of 321Not in the top three

Azure DevOps5 of 320Not in the top three

Codeberg4 of 320Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Azure Repos. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 27 of the 32 answers that named Azure Repos and are not a share of its labels.

Domains cited

mgsoftware.nl14

guideflow.com12

worldmetrics.org12

viasocket.com10

g2.com9

bmc.com7

gitnux.org7

reddit.com7

rhodecode.com7

aimultiple.com6

Ninety-one of the ninety-one domain citations in answers naming Azure Repos came from somebody else's page.

Pages cited

mgsoftware.nl/en/tools/best-version-control-systems14

guideflow.com/blog/version-control-software12

viasocket.com/discovery/blog/gq33cp/version-control-tools/10-best-version-control-tools-fo10

worldmetrics.org/best/source-code-control-software9

bmc.com/blogs/github-vs-gitlab-vs-bitbucket7

aimultiple.com/version-control-tools6

devopsschool.org/tools/source-code-management6

g2.com/categories/version-control-hosting6

Pages are listed as the models cited them.

Names read as Azure Repos

What the judge wrote, as written, with how often. The vendor table decides that these count as Azure Repos; a claim can dispute any of them.

Azure DevOps Repos 7Azure DevOps / Azure Repos 1Azure DevOps/Repos 1

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Azure Repos's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Azure Repos, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at azure.cn is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.