Finding and exporting your Azure DevOps data

What it holds

Azure Repos stores code revisions, branches and tags. Boards holds work items and planning fields, while pull-request discussions and pipeline records are separate from the repository contents.

Where Azure DevOps shows the size

1. With code-read permission and a token carrying vso.code, call GET https://dev.azure.com/ORG/PROJECT/_apis/git/repositories?api-version=7.1 for each project.
2. Sum the repository size fields, returned in bytes, and convert to GB.
3. For a local comparison, run git count-objects -vH inside a complete clone and inspect size-pack; account for LFS independently.

Plan and admin role. Code read permission is needed in each project. Work-item exports require Project Administrators membership or View project-level information set to Allow, together with access to the relevant items.

Exporting the full history

1. Run git clone --mirror REPOSITORY_URL for each repository and git lfs fetch --all where LFS is used.
2. Open Boards > Queries and build or open a query covering the required work items.
3. Add the desired fields as query columns, then select the actions icon > Export to CSV.

A CSV contains selected query fields, not a complete work-item revision, comment or attachment archive. Mirrors likewise omit service-side collaboration records.

LFS objects are external to ordinary Git storage and need their own download.

The documented repository ceiling is 250 GB, with less than 10 GB recommended; recommended individual file size is at most 100 MB and pushes are limited to 5 GB.

You don't need to run an export to talk to us, and there's no need to clean it first — removing personal data is part of our work.