> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/updating-and-viewing-reports-in-azure-devops/pre-requisites.md).

# Pre-requisites

To authenticate Azure DevOps with Avo Assure, here are the prerequisites: 

1. **Azure DevOps Credentials**: Ensure to have the login credentials such as username and password ready 
2. **API Access Token**: Generate the API token and keep it handy  
3. **Avo Assure Client**: Ensure Avo Assure Clients should be connected with Avo Assure to configure and execute the Execution list. 
4. **Avo Integrator**: Ensure the Avo Integrator extension is downloaded in the browser. This required for Login, Mapping, and Logging a bug from Avo Assure to Azure DevOps. 

{% hint style="info" %}
To learn how to add **Avo Integrator** in Browser, refer this [Avo Integrator Extension](/avo-assure/integrations-in-avo-assure/avo-integrator-extension.md)
{% 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 dynamically by asking a question.

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

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/azure-devops-in-avo-assure/updating-and-viewing-reports-in-azure-devops/pre-requisites.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.