Skip to content
Telegraph Lab

Source code

Find and export
your Azure DevOps data.

Azure DevOps keeps Git repositories and work-tracking records in different services. Their inventories and exports should identify code history, large files and Boards content separately.

Report in
GB
Category
Source code
Last checked

Find your Azure DevOps data size

  1. Use read access across the projects and repositories in scope.
  2. Ask a developer to list repositories through the Azure DevOps Git REST API.
  3. Sum each repository's size field, which Microsoft defines as compressed bytes, and convert to GB.
  4. Check mirror-clone folder sizes and LFS storage when measuring an actual collection.
The repository size field does not establish the volume of Boards, artifacts or all LFS content. Describe those separately.

What to include in your data inventory

Report source-history storage in GB, with repository and project counts. Give work-item quantities and attachment availability alongside it.

Use the oldest retained commits and work-item dates, including imports, and identify contributing staff.

Add the dates covered and the people who use this software. Label estimates and describe how you calculated them.

Export your Azure DevOps history

  1. Create mirror clones for the Git repositories in scope.
  2. Collect required Git LFS objects separately.
  3. In Boards → Queries, define the work items and columns needed, then choose Export to CSV.
  4. Use a supported additional route for required comments, attachments, artifacts or other content outside those files.

Boards CSVs reflect the fields and filters selected in the query. Preserve work-item IDs and repository relationships.

A code mirror and work-item CSV have different scopes. Review the missing resource types before planning a full collection.

Why Azure DevOps data has value for AI training

Work items can connect requirements and reported bugs with the code changes used to address them.

Review and test context can explain how a technical team evaluates its work.

What stays private

Select projects and resources in scope, reviewing code rights and confidential work-item content.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.

Common questions about Azure DevOps data

What unit is the API size field?

Microsoft defines repository size as compressed bytes. Convert and state the basis used.

Does it include Boards data?

Repository size and Boards records are different quantities. Inventory them separately.

Which fields appear in a work-item CSV?

The export uses the fields selected as query columns and the items returned by its filters.

Are LFS objects in the repository figure?

Check large-file storage and collection explicitly rather than assuming complete coverage.

Your data inventory

Add your numbers to the picture.

Enter the quantities and years covered in your data inventory, then share it with your Telegraph Lab contact. We’ll review the material and discuss the next step with you.

Discuss your data