Azure DevOps Repo
This document outlines the integration with the Azure DevOps Repo connector, enabling streamlined metadata management through features such as crawling and data preview. It also ensures secure authentication via Credential Manager.

Overview
Connector Details
Connector Category
File Connectors
Connector Version
Release7.2
Releases Supported (Available from)
Release6.0
Connectivity
[How the connection is established with Azure DevOps Repo]
REST APIs
Connector Features
Crawling
✅
Delta Crawling
❌
Profiling
❌
Query Sheet
NA
Data Preview
✅
Auto Lineage
NA
Manual Lineage
✅
Secure Authentication via Credential Manager
✅
Data Quality
❌
DAM (Data Access Management)
❌
Bridge
✅
Metadata Mapping
The following objects are crawled from the Azure DevOps Repo and mapped to the corresponding UI assets.
Bucket
Bucket
Bucket
Bucket
Bucket
Folder
Folder
Folder
Folder
Folder
File
File
File
File
File
XLSX
File
File
File
XLSX
XLS
File
File
File
XLS
CSV
File
File
File
CSV
TXT
File
File
File
TXT
PARQUET
File
File
File
PARQUET
ORC
File
File
File
ORC
JSON
File
File
File
JSON
YAML
File
File
File
YAML
PIP
File
File
File
PIP
Set up a Connection
Prerequisites
The following are the prerequisites to establish a connection.
Service Account User Permissions
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
Connector Validation
Read-only
Crawling
Read-only
Folder
Read-only
Files
Read-only
Connection Configuration Steps
Users are required to have the Connector Creator role in order to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Azure DevOps Repo, and complete the required parameters.
Connector Type
By default, "Azure DevOps Repo" is displayed as the selected connector type.
Credential Manager*
Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selected option.
Supported Credential Managers:
OE Credential Manager
AWS Secrets Manager
HashiCorp
Azure Key Vault
Connector Environment
Select the environment (Example: PROD, STG) configured for the connector.
Connector Name*
Enter a unique name for the Azure Devops Repo connection
(Example: "AzureDevopsRepodb").
Connector Description
Enter a brief description of the connector.
Organisation*
Enter the organization name from the source system.
Project*
Enter the name of the project for the connection.
Repository*
Enter the repository name within the selected project.
Token*
Enter the access token required for authentication.
Connection String
Configure the connection string for the Azure Devops Repo database:
Automatic mode: The system generates a connection string based on the provided credentials.
Manual mode: Enter a valid connection string manually.
Replace placeholders with actual database details.
{sid} refers to the database name.
Proxy Enabled*
Select Yes to route API calls through a proxy server. Select No to bypass the proxy and connect directly.
Default Governance Roles
Default Governance Roles*
Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings are available for selection.
Admin Roles
Admin Roles*
Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured
in the security settings are available for selection.
No of Archive Objects
No Of Archive Objects*
This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.
Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.
Bridge
Select Bridge*
If applicable, select the bridge from the drop-down list.
The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.
After entering all connection details, the following actions can be performed:
Click Validate to verify the connection.
Click Save to store the connection for future use.
Click Save & Configure to apply additional settings before saving.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl
To perform crawl operations, users must be assigned the Integration Admin role.
Navigate to the Connectors page and click Crawl/Profile.
This action initiates the metadata collection process from the data source and loads the retrieved metadata into the File Manager.
In the File Manager, select the specific folder(s) or file(s), then click Catalog Files/Folders from the Nine Dots menu.
The selected files or folders will be added to the Data Catalog> Databases/Files/File Columns tab.
Other Operations
The Connectors page provides a centralized view of all configured connectors, along with their health status.
Managing connectors includes:
Connectors Health: Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
Viewing: Click the Eye icon next to the connector name to view connector details, including databases, tables, columns, and codes.
Nine Dots Menu Options:
To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.
Edit Connector: Update and revalidate the data source.
Validate Connector: Check the connection's integrity.
Settings: Modify connector settings.
Crawler: Configure data extraction.
Business Glossary Settings: Manage term associations at the connector level.
Others: Configure notification recipients for metadata changes.
Delete Connector: Remove a connector with confirmation.
Connectivity Troubleshooting
If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.
1
Error while validating connection: Exception occured while validating in Azure Repo Connection : A JSONObject text must
begin with '{' at 5 [character 1 line 3]
Description: Invalid response format – expected JSON object (Error parsing at line 3).
Resolution: Enter valid project, repository, organization, and token details in the correct format.
Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA
Last updated
Was this helpful?

