> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/help-center-index/faqs/tfs-faqs/auth-types.md).

# Which authentication modes does OpsHub Integration Manager support for Team Foundation Server (TFS)/

### Description

Out of the multiple authentication modes supported by Team Foundation Server (TFS)/Azure DevOps, <code class="expression">space.vars.OIM</code> supports 2 modes.

### Solution

Following are the authentication modes that are supported by <code class="expression">space.vars.OIM</code> for Team Foundation Server (TFS)/Azure DevOps:

* **Basic**
  * For Team Foundation Server (TFS), **Basic** authentication requires UserName prefixed with Domain Name and Password. For NTLM, **Basic** authentication mode is used.
  * For Azure DevOps, **Basic** authentication requires Email Id and **Alternative Credentials**. Refer [*Alternative Credentials*](/v7.237/connectors/azure-devops.md) section to learn how to enable the **Alternative Credentials**.
* **Personal Access Token**
  * For Azure DevOps, **Personal Access Token** authentication requires Email Id and **Personal Access Token**. Refer [*Personal Access Token*](/v7.237/connectors/azure-devops.md#create-personal-access-token) section to learn how to create a new personal access token.


---

# 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://docs.opshub.com/v7.237/help-center-index/faqs/tfs-faqs/auth-types.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.