Start integrating with ONEiO for free!

Endpoint Configuration Guide - Azure DevOps

In this document, you can find the description of fields and additional instructions on making the endpoint in ONEiO ready for integration with your Azure DevOps instance. This endpoint is meant as a self-service and currently supports the Bugs, Epics, Issues, and Tasks as entity types. If anything is unclear or you get stuck with something that is not covered please reach out to us at



Status Sets the status of the endpoint. 
Name Name of the endpoint. It is recommended to use short names since this name is used in displays throughout ONEiO.
Base URL The base address of your Azure DevOps instance.



  [Your Azure DevOps] -> ONEiO
ONEiO Receiver QA/ONEiO Receiver PROD The address to insert to Azure DevOps Service Hooks. The targets are different depending on the ONEiO environment. See the Azure DevOps integration guide for more details.
Authentication Token In the edit mode will generate the authentication token to be used in the Service Hook configuration. 
Inbound Whitelist Filter

A comma-separated list of conditions must all match to allow the inbound message to be processed. Each contains an attribute name, operation, and value. Supported operation types are:

  • = (or ==) for EQUALS
  • != for NOT EQUALS
  • IN which evaluates to true if any of the values in the list are equal to the value compared to

The default value

resource.fields.System.ChangedBy!=${config:property.username} <${}>,resource.revision.fields.System.ChangedBy!=${config:property.username} <${}>

serves the purpose of filtering the echoing of integration messaging generated by ONEiO.




  ONEiO -> [Your MS Azure DevOps]
Method  Decides whether ONEiO will use a PAT or an OAuth bearer token to authenticate.
Personal Access Token The value of the PAT.
Client Id Client Id value of the OAuth application registered in Microsoft Entra ID.
Client Secret The corresponding secret of the OAuth application.
Token URL  The OAuth token resource URL in Microsoft Entra ID.
Scope Permission scope to be requested for the token. It should match or be covered by the permission for the whole OAuth application.
Username The username of the user utilized by the integration. This will be required for the echo suppression mechanism defined in the Inbound Whitelist Filter property.
User Email The email associated with the user.


Entity types

To integrate with Azure DevOps, you can use defined entity types. These entity types are valid for Basic and Scrum boards. 

Currently supported entities:

  • Bug
  • Epic
  • Issue
  • Task
  • Pipeline Run
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.