Home / Microsoft
Azure DevOps Repos + Git LFS
azure.microsoft.com/en-us/pricing/details/devops/azure-devopPaaSstorage/azure-devops-repos-git-lfsJSONcomparereport an errorprovider JSON
- Free allowance
- No LFS storage quota is published and none is enforced in the docs.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported4 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | No LFS storage quota is published and none is enforced in the docs. Microsoft states plainly: 'Azure DevOps Services fully supports Git LFS and offers it for free.' The free tier is 5 Basic users with unlimited private Git repos; only Azure Artifacts carries a numeric cap (2 GiB free). Repo size guidance is 250 GB (soft), 'recommend keeping below 10 GB for optimal performance'. unit GiB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | Unmetered. No bandwidth line item exists anywhere on the Azure DevOps pricing page — the paid units are users, parallel jobs and Artifacts GiB only. |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | rest, ssh, git part of the text of Free tier, above |
|---|
| Tooling | git-lfs 3.x (gitlfs/git-lfs). Works over HTTPS; SSH is NOT supported for repos with LFS-tracked files. PAT auth. Also reachable via the Azure DevOps REST API for repo/ref management. |
|---|
| Composes with | 5 free Basic users per org, and up to 5 orgs per account (Microsoft Q&A, moderator answer) -> 25 orgs' worth of free LFS if each is a separate MSA. Orgs are unlimited in repo count, so total LFS is bounded only by the 250 GB-per-repo soft guidance — 250 GB x N repos. Unlike GitLab/GitHub, LFS bytes are not on the meter at all. |
|---|
| Reliability | The 250 GB repo figure is guidance, not a wall, but the docs warn the internal pack-file limit can trigger 'The Git pack file limit has been reached' and temporarily block writes on very large repos. Over-quota behaviour is undefined because there is no quota. |
|---|
Evidence 4
Unknown values 5
$.binding_note boilerplate$.per_object_cap.notes the field may be stated in a source that was not read$.per_object_cap.stated the field may be stated in a source that was not read$.retention.notes the field may be stated in a source that was not read$.retention.stated the field may be stated in a source that was not read