> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started-1/registration/version-control-repository/tfs.md).

# TFS

Integrating a **Team Foundation Server (TFS)** repository with AutoRABIT (ARM) lets you automate commits, merges, and CI/CD pipelines against code stored in your on-premises or Azure DevOps–hosted TFS project.

The steps below show an Org Admin how to register a TFS repo so ARM can authenticate, index metadata, and launch jobs.

***

## Registering TFS Repository in ARM <a href="#registering-tfs-repository-in-arm" id="registering-tfs-repository-in-arm"></a>

1. Log in to **ARM**.
2. Hover over **`Admin`** and choose **`VC Repos`**.<br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVpRYETXbi6BemW0JjaVW%2FScreenshot%202025-08-16%20at%208.27.09%E2%80%AFPM.png?alt=media&amp;token=fa85a465-3552-4ca1-b33d-373ee34da21e" alt="" width="232"><figcaption></figcaption></figure>
3. Click **Register Repository**.
4. On the **Register Repository** page, select **TFS** as the **Version Control System**.
5. **Repository Label** – enter a friendly name that will appear in ARM.
6. **Repository URL** – paste the full TFS URL (e.g., `https://tfs.mycorp.com/tfs/Collection/Project`).
7. **Credentials** – choose stored credentials or click **+** to add new ones.
8. Click **Test Connection**. A success message confirms ARM can authenticate.<br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FNUwlVSQIT2scwbQzVH37%2Fimage.png?alt=media&amp;token=cd06b872-3073-4ae3-b4b5-2fd910c98dfe" alt="" width="375"><figcaption></figcaption></figure>
9. Click **Save** to finish. The repository now appears in the VC Repos list.

{% hint style="info" %}
**nCino projects**\
Tick **Enable nCino** if the repo contains nCino objects. ARM marks such repositories with the nCino logo so you can spot them quickly.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/getting-started-1/registration/version-control-repository/tfs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.