Azure DevOps connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Azure DevOps from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Azure DevOps ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Azure DevOps access level does the connector require?
The service principal must have the Basic access level or higher. Stakeholder access doesn't include Azure Repos, so the repository, commit, and pull request tables fail without Basic. See Use service principals and managed identities.
Which tables does the connector support?
The connector supports project, repository, work item, build, release, test, and identity tables, such as projects, git_repositories, commits, pull_requests, work_items, builds, releases, users, and groups. For the full list and destination schemas, see Supported source tables.
How far back can the connector ingest data?
For the incremental commits table, the first sync ingests commits from the start_datetime you set, or from the previous 180 days by default. Each later sync ingests commits after the last run. Full-refresh tables reingest all available records on every run.
Which authentication methods does the connector support?
The connector supports OAuth M2M with a Microsoft Entra service principal. OAuth U2M and basic authentication are not supported.