Small business=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 21 → 9 of 20
Azure · 1 category · RankedAzure Repos
41Judge labels
1First choices
3Negative labels
12 / 14Models named it
1Category
October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10.8, every buyer segment counted.
Best standing
2% in Source control for mid-market buyers
Rank 5 of 33 in the mid-market standingaccepted challenger
0 of 14 models made it the first choice on the direct prompt; 0% of its 16 labels there were negative.
What the models named instead of Azure Repos →By buyer segmentRead the same way at every buyer size.
Small business10 of 22
0%5 labels
under the label threshold
Mid-market5 of 33
2%16 labels
accepted challenger
Enterprise10 of 42
0%20 labels
accepted challenger
In source control · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading
Standing by category
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 | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Source control hosting | Developer platform | 2% | 5 of 33 | 0% | 16 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
Movement
Since September 2026, Azure Repos held within the floor in its one category: no change cleared 11 points.
Best category · Source control · by segment
Mid-market=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 7 of 29, unchanged
Enterprise=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 7 → 9 of 36
All categories · Mid-market
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Source control | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 7 → 5 of 33 |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
By model
How each model treated Azure Repos across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.ShowHide
By model
How each model treated Azure Repos across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.
ShowHide| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 1 | 0 | 0 | 1 |
| Grok 4.20 | 0 | 1 | 2 | 0 | 3 |
| Mistral Small | 0 | 2 | 0 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 2 | 0 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 2 | 0 | 2 |
| Muse Glimmer 30B | 1 | 2 | 0 | 0 | 3 |
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
Direct5 labelsNone
Paraphrase8 labelsNone
Comparative17 labelsNone
Budget-constrained2 labels1
Scale-constrained4 labelsNone
Negative5 labelsNone
First choiceAlternativeMentionNegative41 labels in all, every segment counted; 1 of the 1 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.
“Small team wanting zero cost and maximum ecosystem: GitHub or Azure Repos – both give unlimited private repos for free” Muse Glimmer 30B · Source control · budget prompt · first choice
“Choose Azure Repos if: You're heavily invested in Microsoft/Azure ecosystem and need enterprise governance” Kimi K2 · Source control · comparative prompt · alternative
“Free unlimited private Git repositories, especially useful if your company already uses Microsoft tools” Mistral Small · Source control · budget prompt · alternative
“If you're already using Microsoft products, Azure Repos is a solid alternative.” Mistral Small · Source control · paraphrase 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 41 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.ShowHide
Named alongside
The products named in the same answers as Azure Repos, over the 41 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.
ShowHideProductSame answerTook the first choice insteadHead to head
A head-to-head page exists where both products are among a category's top eight. 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, five of the fourteen in this edition, so these counts come from 40 of the 41 answers that named Azure Repos and are not a share of its labels.
Domains cited
g2.com17
about.gitlab.com15
bitbucket.org13
github.com13
gitnux.org13
guideflow.com11
dev.to10
docs.github.com10
guptadeepak.com10
dataintelo.com8
120 of the 120 domain citations in answers naming Azure Repos came from somebody else's page.
Pages cited
Pages are listed as the models cited them.
Search and answers
Where Azure Repos stands in Google search beside where it stands in the models' answers.ShowHide
Search and answers
Where Azure Repos stands in Google search beside where it stands in the models' answers.
ShowHideIn search
Google, US estimates- Searches for its name, Google
- 590 a month (“azure repos”)
- AI search demand for its name, est.
- 42 a month
- Its own site
- It sits on Azure's site (azure.cn), so there are no site figures for it alone
In answers
This editionShare of first choices
2%
rank 5 of 33 in source control
Segment leader
70%
GitHub
- First choices
- 1 across its categories
- Named in
- 41 answers
- Its own site cited
- in 40 of the answers that named it
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
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 Repos / Azure DevOps 3Azure DevOps / Azure Repos 1Azure DevOps Repos 1
Follow Azure Repos
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
The company
Azure is the company behind Azure Repos.ShowHide
The company
Azure is the company behind Azure Repos.
ShowHideOn record
Company records- Also from Azure
- Azure ACR, Azure AD Conditional Access, Azure AD Graph API, Azure AI Document Intelligence, Azure AI Foundry, Azure AI Gateway, Azure AI Search, Azure API Management and 79 more
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.
What a new claim receivesHide what a new claim receives
A new claim receives the current edition's vendor brief for Azure Repos by email, built from the raw record of the edition. It shows:
- where Azure Repos is named, by buyer and by framing, and which cells hold its first choices;
- the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
- its vocabulary against the segment leader's, and the pages the models cited;
- who was chosen in the answers that did not name Azure Repos, and every reason the record gives;
- a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
- one page of published figures cleared to show a buyer.