> For the complete documentation index, see [llms.txt](https://docs.ticket-log.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ticket-log.com/documentation/administrators-guide/azure-devops-settings.md).

# Azure DevOps settings

This is the Azure DevOps configuration screen:

<figure><img src="/files/w1oyDu28M49ZmUSDMUXR" alt="" width="563"><figcaption></figcaption></figure>

From this screen you set the **Organization URL** and **Project** name for the Azure DevOps organization and project you want new tickets to be created in. Additional Azure DevOps settings (such as work item types, tags and areas) are located in [Forms & fields](/documentation/administrators-guide/forms-and-fields.md) settings.

Select an **Authentication method** then click **Save & Authorize** to complete the integration. What happens next depends on the authentication method selected:

{% hint style="info" %}
With either method, you should consider using a dedicated user for the purpose of TicketLog integration. This will ensure all interactions (such as comments and updates) are easy to identify in Azure DevOps.
{% endhint %}

{% hint style="info" %}
For details on authorization requirements or help with issues, check out our Troubleshooting guide here:[Authorizing Azure DevOps](/troubleshooting/authorizing-azure-devops.md)
{% endhint %}

* **Microsoft Entra ID:**

  * *Choose this method if your Azure DevOps users are Entra ID organizational users.*
  * Select a currently logged in user or sign in with your preferred user.
  * Accept the integration with TicketLog:

  <figure><img src="/files/FpMmO41SUVHN8B3fU0FV" alt="" width="344"><figcaption></figcaption></figure>
* **Legacy Azure DevOps OAuth:**

  * *Choose this method if your Azure DevOps users are direct Microsoft logins.*
  * *Please note:*
    * Visit our [Quick Setup guide](/guides/how-to-connect-to-azure-devops.md) for detailed instructions on this method.
    * This method does not give an option to select or change user. Authentication will default to the currently logged-in Azure DevOps user. For this reason, we recommend completing this process while *not* logged in to Azure DevOps (consider using a Guest, Private or Incognito browser). This way, you can be sure which Azure DevOps user is attached as the integration user to TicketLog.&#x20;
  * If you are not already logged in to Azure DevOps, you will be prompted to login.
  * You will then be prompted to accept data sharing for integration. Verify the user (1) and organization (2) details are correct, then click Accept.

  <figure><img src="/files/MN9xR5GVZQk0psk1WWUk" alt="" width="563"><figcaption></figcaption></figure>

Once accepted, TicketLog will attempt to validate the connection with Azure DevOps and ensure minimum configuration requirements are correct. Watch the panel at the bottom of the screen and wait for the results to appear. If validation is successful, the service desk will be enabled. If there is an error, the service desk will be disabled.

<figure><img src="/files/ltRC0fdGtLoaYodKmS8W" alt="" width="563"><figcaption></figcaption></figure>

You can validate the connection any time by clicking the **Check Connection** button.

&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ticket-log.com/documentation/administrators-guide/azure-devops-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.